FS-977 Digi International, FS-977 Datasheet
FS-977
Specifications of FS-977
Related parts for FS-977
FS-977 Summary of contents
Page 1
... JTAG-Booster for Intel 386EX P.O: Box 1103 Kueferstrasse 8 Tel. +49 (7667) 908-0 sales@fsforth.de • D-79200 Breisach, Germany • D-79206 Breisach, Germany • Fax +49 (7667) 908-200 • http://www.fsforth.de ...
Page 2
... FS FORTH-SYSTEME GmbH Postfach 1103, D-79200 Breisach, Germany Release of Document: Author: Filename: Program Version: All rights reserved. No part of this document may be copied or reproduced in any form or by any means without the prior written consent of FS FORTH-SYSTEME GmbH. 2 May 15, 2002 Dieter Fögele JTAG_386EXa.doc 4.xx ...
Page 3
Table of Contents 1. General ..........................................................................................................4 1.1. Ordering Information ............................................................................5 1.2. System Requirements ..........................................................................5 1.3. Contents of Distribution Disk ................................................................6 1.4. Connecting your PC to the target system .............................................7 1.5. First Example with Intel 386EX .............................................................9 1.6. Trouble Shooting ................................................................................ ...
Page 4
General The program JTAG386.EXE uses the JTAG port of the Intel 386EX embedded microprocessor in conjunction with the small JTAG-Booster: to program data into flash memory to verify and read the contents of a flash memory to load data ...
Page 5
Ordering Information The following related products are available 925 JTAG-Booster Intel 386EX, 5V, DOS/Win9x/WinNT, delivered with adapter type 227 977 JTAG-Booster Intel 386EX, 3.3V, DOS/Win9x/WinNT, delivered with adapter type 285 1.2. System Requirements To successfully run this tool the ...
Page 6
Contents of Distribution Disk JTAG386.EXE Tool for Intel 386EX JTAG386.OVL JTAG386.INI Template configuration file for Intel 386EX. See chapter 1.8 "Initialization file JTAG386.INI" HEX2BIN.EXE Converter program to convert Intel HEX and Motorola S-Record files to binary. See chapter 4 ...
Page 7
... Pin 7 is the target’s TDO pin and is connected to the JTAG-Booster’s TDI pin. There are two versions of the JTAG-Booster available version (FS part number 227) and a 3.3V version (FS part number 285). Don’t apply 5V to the 3.3V version of the JTAG-Booster! Your target must be able to power the JTAG-Booster, it draws about 100mA. ...
Page 8
The utility is started with the general command line format: JTAG386 /function [filename] [/option_1] ... [/option_n]. Note that the function must be the first argument followed (if needed) by the filename. If you want to cancel execution of JTAG386, press ...
Page 9
... JTAG386 --- JTAG utility for Intel 386EX Copyright FS FORTH-SYSTEME GmbH, Breisach Version 4.xx of mm/dd/yyyy (1) Configuration loaded from file JTAG386.INI (2) Target: Module 386EX, FS FORTH-SYSTEME GmbH (3) Using LPT at I/O-address 0378h (4) JTAG Adapter detected (5) 1 Device detected in JTAG chain Device 0: IDCODE=28270013 Intel 386EXTC (C-Step, 5V) ...
Page 10
The initialization file JTAG386.INI was found in the current directory. (2) The target identification line of the initialization file is printed here. (3) The resulting I/O-address of the parallel port is printed here. (4) A JTAG-Booster is found on ...
Page 11
Trouble Shooting Avoid long distances between your Host-PC and the target. If you are using standard parallel extension cable, the JTAG-BOOSTER may not work. Don't use Dongles between the parallel port and the JTAG-BOOSTER. Switch off all special modes ...
Page 12
... Configuration file XYZ not found. The file specified with the option /INI= wasn't found. Device offset out of range The value specified with the option /OFFSET= is greater than the size of the detected flash device. Disk full Writing a output file was aborted as a result of missing disk space. ...
Page 13
Error: Pin-Name is an input only pin The specified pin cannot be activated. Check the command line. Check the initialization file. Error: Pin-Name may not be read back The specified pin can be switched to tristate, but cannot be read ...
Page 14
... Option /CPUPOS= out of range The number specified with the option /CPUPOS= must be less or equal to the number of parts minus 1. Option /IROFFS= out of range Please specify a smaller value Part at specified position is not a Intel 386EX The option /CPUPOS= points to a part not a Intel 386EX 14 JTAG_386EXa ...
Page 15
... The sum of all instruction register bits in the JTAG chain does not fit to the Intel 386EX. Check the target connection. Check the target CPU type. Check the settings for /IROFFS= and /CPUPOS there are several parts in the JTAG chain. Target no longer connected There is a cyclic check of the JTAG chain ...
Page 16
... The length of the boundary scan register of the selected part (if there are more than one in the chain) does not fit to the Intel 386EX. Check the target connection. Check the target CPU type. Check the settings for /IROFFS= and /CPUPOS there are several parts in the JTAG chain. ...
Page 17
Initialization file JTAG386.INI This file is used to define the default direction and level of all CPU signals. This file must be carefully adapted to your design with the Intel 386EX. The Target- Entry is used to identify your ...
Page 18
... Sample File JTAG386.INI: // Description file for Intel 386EX Target: Module 386EX, FS FORTH-SYSTEME GmbH // All chip select signals are set to output and inactive. // All signals should be defined. Undefined signals are set to their defaults. // Pin names are defined in upper case. // Low active signals are signed with a trailing #. ...
Page 19
A21 Out,Hi A22 Out,Hi A23 Out,Hi A24 Out,Hi A25 Out,Hi SMI# Inp P3.0 Inp // = TMROUT0 P3.1 Inp // = TMROUT1 SRXCLK Inp // = DTR1# SSIORX Inp // = RI1# SSIOTX Inp // = RTS1# P3.2 Inp // ...
Page 20
SMIACT# Inp P2.0 Out, CS0# P2.1 Out, CS1# P2.2 Out, CS2# P2.3 Out, CS3# P2.4 Out, CS4# DACK0# Out, CS5# P2.5 Inp // = RxD0 P2.6 Inp // ...
Page 21
Supported flash devices Type JTAG386 /LIST [optionlist] to get a online list of all flash types which could be used with the /DEVICE= option. See separate file JTAG_V4xx_FLASHES.pdf to get a complete list of supported flash types. JTAG_386EXa.doc 21 ...
Page 22
... When you start JTAG386.EXE without any parameters the following help screen with all possible functions and options is displayed: JTAG386 --- JTAG utility for Intel 386EX Copyright © FS FORTH-SYSTEME GmbH, Breisach Version 4.xx of mm/dd/yyyy Programming of Flash-EPROMs and hardware tests on targets with the Intel 386EX. ...
Page 23
... With the option /LATTICE you can simulate the speed achievable with the simple ispLSI-Adapter. /LPT1 /LPT2 /LPT3 A printer port may be specified where the JTAG-Booster resides. Default: /LPT1 JTAG_386EXa.doc /CS1 /CS2 /CS6 /NOCS /PAUSE /LATTICE /ERASEALL /LPT-BASE= /16BIT L= /FILE-OFFSET= /DELAY= /DEVICE-BASE= /DB= /IROFFS= /I2CCLK= /I2CDAT= /WATCH= /OUT= /CS3 /NOWRSETUP /P /LPT1 /8BIT /FO= /CPUPOS= /I2CDATI= /INI= 23 ...
Page 24
... This pin must be specified as output in the initialization file. /IROFFS= Specifies the position of the Intel 386EX instruction register within the JTAG chain. In most cases this option is not needed. Default: /IROFFS=0 /CPUPOS= Specifies the position of the Intel 386EX within the JTAG chain. Default: /CPUPOS=0 24 JTAG_386EXa ...
Page 25
Program a Flash Device Usage: JTAG386 /P filename [optionlist] The specified file is programmed into the flash memory. The flash status is polled after programming of each cell (cell bit, depending on current data bus width). In ...
Page 26
... By default a device start address of 3000000h (=48MByte) is used for accesses to the flash device, because there is SRAM selected with a PLD logic on the FS FORTH-SYSTEM module 386EX. Default: ...
Page 27
The number of programmed bytes may be limited to LENGTH LENGTH is specified the whole file is programmed. Default: /LENGTH=4000000 (64 MByte) Abbreviation: /L= /NODUMP In case of a verify error the contents of the flash memory ...
Page 28
This example programs up to 128 Kbytes of the file ROMDOS.ROM (with i.e. 512 Kbytes) to the top of the boot flash memory. JTAG386 /P CE.ROM /CS1 This example programs the file CE.ROM to the 32 Bit Flash-EPROM connected to ...
Page 29
... See function /P (Chapter 2.1) 2 /DEVICE-BASE=hhhhhh See function /P (Chapter 2.1) /OFFSET=hhhhhh Reading of the flash memory starts at an offset of hhhhhh relative to the start address of the flash device. If the offset is negative, the offset specifies a address relative to the end of the flash device. See also option /TOP. Default: ...
Page 30
... If the option /TOP is used the option /OFFSET= specifies the address where reading ends (plus one) instead of the starting address. /LENGTH=hhhhhh The number of read bytes may be limited to LENGTH LENGTH is specified the whole flash device is read (if no offset is specified). /UCS /CS0 /CS1 /CS2 /CS3 /CS4 /CS5 /CS6 /NOCS See function /P (Chapter 2 ...
Page 31
... See function /P (Chapter 2.1) /8BIT /16BIT See function /P (Chapter 2.1) /BYTE-MODE See function /P (Chapter 2.1) /NOMAN See function /P (Chapter 2.1) /DEVICE-BASE=hhhhhh See function /P (Chapter 2.1) /OFFSET=hhhhhh See function /P (Chapter 2.1) /TOP See function /P (Chapter 2.1) /FILE-OFFSET=hhhhhh See function /P (Chapter 2.1) JTAG_386EXa.doc 31 ...
Page 32
See function /P (Chapter 2.1) /NODUMP See function /P (Chapter 2.1) /UCS /CS0 /CS1 /CS2 /CS3 /CS4 /CS5 /CS6 /NOCS See function /P (Chapter 2.1) /NOWRSETUP See function /P (Chapter 2.1) Please note: In the function /V write cycles ...
Page 33
... The number of downloaded bytes may be limited to LENGTH LENGTH is specified the whole file is downloaded. Default: /LENGTH=4000000 (64 MByte) Abbreviation: /L= /FILE-OFFSET=hhhhhh If FILE-OFFSET is specified, the first hhhhhh bytes of the file are skipped and not loaded into target memory. Default: /FILE-OFFSET=0 Abbreviation: /FO= /NODUMP In case of a verify error the contents of the target memory is written to a file with the extension ...
Page 34
... This increases the download speed by 50%. Examples: JTAG386 /D HELLO /O=30000 This example writes the file HELLO to the target memory. JTAG386 /D CAN.REF /CS3 /8BIT This example loads the file CAN.REF into the CAN controller on the FS FORTH- SYSTEME module 80386EX-CAN. 34 JTAG_386EXa.doc ...
Page 35
... Target data is written to the specified file. For uploads from a flash device the function /R should be used. Options: /8BIT /16BIT Default: /16BIT /OFFSET=hhhhhh See function /D (Chapter Fehler! Verweisquelle konnte nicht gefunden werden.) /TOP See function /D (Chapter Fehler! Verweisquelle konnte nicht gefunden werden.) /LENGTH=hhhhhh The number of uploaded bytes must be specified ...
Page 36
... Test target memory (SRAM) Usage: JTAG386 /SRAM [optionlist] Makes a memory test. Options: /8BIT /16BIT Default: /16BIT /OFFSET=hhhhhh Memory test starts at OFFSET Default: /OFFSET=0 Abbreviation: /O= /LENGTH=hhhhhh The number of tested bytes must be specified LENGTH is specified an error message occurs. Abbreviation: /L= /UCS /CS0 /CS1 /CS2 /CS3 /CS4 /CS5 /CS6 /NOCS ...
Page 37
... Default: /OFFSET=0 Abbreviation: /O= 3 /DEVICE-BASE=hhhhhh The device start address is used as an additional offset. This gives the function /DUMP the same behavior as function /P /V and /R. Default: /DEVICE-BASE=3000000 Abbreviation: /DB= /TOP If the option /TOP is used the option /OFFSET= specifies the address where ...
Page 38
Example: JTAG386 /DUMP /UCS /8BIT This example makes a memory dump of the first 256 bytes of the Boot-EPROM. 38 JTAG_386EXa.doc ...
Page 39
... The programming starts at an offset of hhhhhh relative to the start address of the I²C-Device. Default: /OFFSET=0 Abbreviation: /O= /FILE-OFFSET=hhhhhh If FILE-OFFSET is specified, the first hhhhhh bytes of the file are skipped and not programmed to target. Default: /FILE-OFFSET=0 Abbreviation: /FO= JTAG_386EXa.doc (if option /I2CBIG omitted) (if option /I2CBIG specified) ...
Page 40
The number of programmed bytes may be limited to LENGTH LENGTH is specified the whole file is programmed. Abbreviation: /L= /NODUMP In case of a verify error the contents of the I²C-Device is written to a file ...
Page 41
... Options: /I2CBIG This option must be the first option after the filename. See function /PI2C (Chapter 2.8) /DEVICE-BASE=hhhhhh See function /PI2C (Chapter 2.8) /OFFSET=hhhhhh Reading of the I²C-Device starts at an offset of hhhhhh relative to the start address of the I²C-Device. Default: /OFFSET=0 Abbreviation: /O= /LENGTH=hhhhhh The number of read bytes must be specified otherwise an error message occurs. ...
Page 42
Example: JTAG386 /RI2C EEPROM.CFG /I2CCLK=GP26 /I2CDAT=GP27 /L=100 This example reads 256 bytes from a serial EEPROM to the file EEPROM.CFG. The serial EEPROM is connected to the pins CP26 and GP27 of the Intel 386EX. 42 JTAG_386EXa.doc ...
Page 43
... This option must be the first option after the filename. See function /PI2C (Chapter 2.8) /DEVICE-BASE=hhhhhh See function /PI2C (Chapter 2.8) /OFFSET=hhhhhh See function /PI2C (Chapter 2.8) /FILE-OFFSET=hhhhhh See function /PI2C (Chapter 2.8) /LENGTH=hhhhhh See function /PI2C (Chapter 2.8) /NODUMP See function /PI2C (Chapter 2.8) /I2CCLK=pin_name See function /PI2C (Chapter 2 ...
Page 44
See function /PI2C (Chapter 2.8) Example: JTAG386 /VI2C EEPROM.CFG /I2CCLK=GP26 /I2CDAT=GP27 This example verifies 256 bytes from a serial EEPROM with the file EEPROM.CFG. The serial EEPROM is connected to the pins CP26 and GP27 of the Intel 386EX. ...
Page 45
... A Hex-Dump of an I²C-Device is printed on the screen, if not redirected to file or device. Options: /I2CBIG This option must be the first option. See function /PI2C (Chapter 2.8) /DEVICE-BASE=hhhhhh See function /PI2C (Chapter 2.8) 4 /OFFSET=hhhhhh The memory dump starts at an offset of hhhhhh. Default: /OFFSET=0 Abbreviation: /O= /LENGTH=hhhhhh Default: /LENGTH=100 Abbreviation: /L= /I2CCLK=pin_name Specifies the CPU pin used for serial clock output ...
Page 46
Specifies the CPU pin used for serial data input. Pin_name must specify a input pin otherwise an error message occurs. Example: JTAG386 /DUMPI2C /I2CCLK=FLAG0 /I2CDAT=FLAG1 This example makes a memory dump of the first 100h bytes of a serial ...
Page 47
Toggle CPU pins Usage: JTAG386 /BLINK /PIN=pinname [optionlist] This command allows to test the hardware by blinking with LEDs or toggling CPU signals. Faster signals can be generated by setting the delay option to zero. This can be a ...
Page 48
Polling CPU pins Usage: JTAG386 /PIN? /PIN=pinname [optionlist] This command allows to test the hardware by polling CPU signals. Please Note: Not every pin of the Intel 386EX may be specified as an input pin. Options: /PIN=pin_name CPU pin ...
Page 49
Polling CPU pins while the CPU is running Usage: JTAG386 /SAMPLE /PIN=pinname [optionlist] This command is similar to the function /PIN?. But with this function any pin can be observed, independent of the pin direction. Furthermore the CPU remains ...
Page 50
Show status of all CPU pins while the CPU is running Usage: JTAG386 /SNAP [optionlist] This function is similar to the function /SAMPLE, but displays the status of all CPU pins on the screen. The CPU remains in normal ...
Page 51
Sample output: This is a sample output for a Intel 386EX | 0 D15 | 0 D14 | 0 D11 | 0 D10 | LBA ...
Page 52
Implementation Information This chapter summarizes some information about the implementation of the JTAG-Booster and describes some restrictions. The JTAG-Booster uses the EXTEST function of the JTAG-Interface to perform Flash programming. Refer to the following table for connecting Flash-EPROMs to ...
Page 53
Converter Program HEX2BIN.EXE Since the JTAG-Booster software is not able to handle Intel-HEX or Motorola S- Record files, an separate converter tool is delivered with this product package. Five types of HEX formats can be converted to BIN file: ...
Page 54
Please Note: "CODE segment start address" is interpreted as a Intel x86 architecture segment address: You have to specify a start address of 10000 to start the conversion at 1 MByte. This converter is a relatively old DOS tool and ...
Page 55
Support for Windows NT and Windows 2000 A configured run time version of the "Kithara DOS Enabler, Version 5.1" is used to give support for some of our DOS based tools (like the JTAG-Booster) for Windows NT and Windows ...
Page 56
De-Installation version 5.xx: For deinstallation of the runtime version of the "Kithara DOS-Enabler Version 5.x": use: Settings - Control-Panel - Add/Remove Programs and remove the "WinNT support for JTAG-Booster and FLASH166" Reboot your PC 56 JTAG_386EXa.doc ...