FS-929 Digi International, FS-929 Datasheet
FS-929
Specifications of FS-929
Related parts for FS-929
FS-929 Summary of contents
Page 1
... JTAG-Booster for Intel StrongARM SA11x0 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_SA-11x0b.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 StrongARM SA-1100.......................................9 1.6. First Example with ...
Page 4
General The programs JTAG1100.EXE and JTAG1110.EXE use the JTAG port of the Intel StrongARM SA-11x0 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 ...
Page 5
Ordering Information The following related products are available 929 JTAG-Booster Intel StrongARM SA-11x0, 3.3V, DOS/Win9x/WinNT, delivered with adapter type 285 268 Adapter Keith&Koep, adapts the 8 pin connector of JTAG-Booster to 10 pin connector of Keith&Koep Evaluation Platform “ARNOLD ...
Page 6
Contents of Distribution Disk JTAG1100.EXE Tool for Intel StrongARM SA-1100 JTAG1100.OVL JTAG1100.INI Template configuration file for Intel StrongARM SA- 1100. See chapter 1.9 "Initialization file JTAG11x0.INI" JTAG1110.EXE Tool for Intel StrongARM SA-1110 JTAG1110.OVL JTAG1110.INI Template configuration file for Intel ...
Page 7
... Pin 7 is the target’s TDO pin and is connected to the JTAG-Booster’s TDI pin. The 3.3V version of the JTAG-Booster (FS part number 285) is delivered together with this package. Don’t use the 5V version of the JTAG-Booster (FS number 227) with a 3.3V target. 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
... For the Keith&Koep Evaluation Platform “ARNOLD II” additional there pin connector available to connect the JTAG-Booster (FS part number 268). +3.3V +3.3V GND TRST# TDI TDO Before you start the program, the JTAG-BOOSTER must be plugged to a parallel interface of your PC and to the 8 pin JTAG connector on the target. ...
Page 9
... LPT1 of your PC and target power is on. Typing JTAG1100 /P MYAPP.BIN at the DOS prompt results in the following output: JTAG1100 --- JTAG utility for Intel StrongARM SA-1100 Copyright FS FORTH-SYSTEME GmbH, Breisach Version 4.xx of mm/dd/yyyy (1) Configuration loaded from file JTAG11x0.INI (2) Target: Keith & Koep, ARNOLD II ...
Page 10
The initialization file JTAG1100.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
... In the following simple example it is assumed that the JTAG-Booster is connected to LPT1 of your PC and target power is on. Typing JTAG1110 /P MYAPP.BIN at the DOS prompt results in the following output: JTAG1110 --- JTAG utility for Intel StrongARM SA-1110 Copyright FS FORTH-SYSTEME GmbH, Breisach Version 4.xx of mm/dd/yyyy (1) Configuration loaded from file JTAG1110.INI (2) Target: Generic Target (3) ...
Page 12
The initialization file JTAG1110.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 13
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 14
... 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. Do not specify option /NOCS with any other chip select There is a conflict in the command line ...
Page 15
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 16
... 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 StrongARM SA-11x0 The option /CPUPOS= points to a part not a Intel StrongARM SA-11x0 16 JTAG_SA11x0b ...
Page 17
... The sum of all instruction register bits in the JTAG chain does not fit to the Intel StrongARM SA-11x0. 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 18
... 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 StrongARM SA-11x0. Check the target connection. Check the target CPU type. Check the settings for /IROFFS= and /CPUPOS there are several parts in the JTAG chain. 18 ...
Page 19
Initialization file JTAG11x0.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 StrongARM SA- 11x0. The Target-Entry is used to identify ...
Page 20
Sample File JTAG1100.INI: // Description file for Intel StrongARM SA-1100 Target: Keith & Koep, ARNOLD II // All chip select signals are set to output and inactive. // All signals should be defined. Undefined signals are set to their defaults. ...
Page 21
D31 Out, Group B: All pins in this group must be set to the same direction // For Flash programming, this group must be set to output A0 Out, Out, Out, Out,Lo ...
Page 22
WE# Out, write enable, is switched while accessing Flash // The following pins are complete bidirectional pins. // The direction of each pin can be set independent of the other pins. // Each pin can be used as ...
Page 23
GP26 Inp GP27 Inp TXD_C Inp RXD_C Inp SCLK_C Inp SFRM_C Inp // The following pins are output only pins. // Setting to input (tristate) one of these pins results in an error. POE# Out, PCMCIA output enable ...
Page 24
Sample File JTAG1110.INI: // Description file for Intel StrongARM SA-1110 Target: Generic Target // All chip select signals are set to output and inactive. // All signals should be defined. Undefined signals are set to their defaults. // Pin names ...
Page 25
D31 Out, Group B: All pins in this group must be set to the same direction // For Flash programming, this group must be set to output A0 Out, Out, Out, Out,Lo ...
Page 26
The following pins are complete bidirectional pins. // The direction of each pin can be set independent of the other pins. // Each pin can be used as input. TXD_3 Inp RXD_3 Inp TXD_2 Inp RXD_2 Inp TXD_1 Inp ...
Page 27
GP20 Inp GP21 Inp GP22 Inp GP23 Inp GP24 Inp GP25 Inp GP26 Inp GP27 Inp TXD_C Inp RXD_C Inp SCLK_C Inp SFRM_C Inp // The following pins are output only pins. // Setting to input (tristate) one of these ...
Page 28
The following pins are input only. // Setting to output of one of these pins results in an error. // Declaration of the direction of these pins is optional. BATT_FAULT Inp // VDD_FAULT Inp // SMROM_EN Inp // IOIS16# ...
Page 29
Supported flash devices Type JTAG11x0 /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_SA11x0b.doc 29 ...
Page 30
... When you start JTAG11x0.EXE without any parameters the following help screen with all possible functions and options is displayed: JTAG11x0 --- JTAG utility for Intel StrongARM SA-11x0 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 StrongARM SA-11x0 ...
Page 31
... Supported Options: /CS0 /CS1 /CS5 /CARD /NOWRSETUP /TOP /P /NODUMP /LPT1 /LPT2 /16BIT /8BIT /FILE-OFFSET= /FO= /DEVICE-BASE= /DB= /IROFFS= /CPUPOS= /I2CDAT= /I2CDATI= /OUT= /INI= The following options are valid for most functions: /DRIVER=x with x = 1,2,3,4 A driver for the interface to the JTAG-BOOSTER on the parallel port may be specified ...
Page 32
... This pin must be specified as output in the initialization file. /IROFFS= Specifies the position of the Intel StrongARM SA-11x0 instruction register within the JTAG chain. In most cases this option is not needed. Default: /IROFFS=0 /CPUPOS= Specifies the position of the Intel StrongARM SA-11x0 within the JTAG chain. Default: /CPUPOS=0 32 JTAG_SA11x0b ...
Page 33
Program a Flash Device Usage: JTAG11x0 /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). ...
Page 34
... Abbreviation: /O= /TOP If the option /TOP is used the option /OFFSET= specifies the address where the programming ends (plus one) instead of the starting address. This option is very important for Intel CPU architectures, because target execution always starts at the top of the address space. ...
Page 35
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 36
Examples: JTAG11x0 /P ROMDOS.ROM /L=20000 /TOP 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. JTAG11x0 /P CE.ROM /32BIT /CS1 This example programs the file CE.ROM ...
Page 37
... 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 38
... 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). /CS0 /CS1 /CS2 /CS3 /NOCS /CS0 /CS1 /CS2 /CS3 /CS4 /CS5 /NOCS (Intel StrongARM SA-1110) See function /P (Chapter 2 ...
Page 39
... See function /P (Chapter 2.1) /8BIT /16BIT /32BIT 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_SA11x0b.doc 39 ...
Page 40
See function /P (Chapter 2.1) /NODUMP See function /P (Chapter 2.1) /CS0 /CS1 /CS2 /CS3 /NOCS /CS0 /CS1 /CS2 /CS3 /CS4 /CS5 /NOCS (Intel StrongARM SA-1110) See function /P (Chapter 2.1) /NOWRSETUP See function /P (Chapter 2.1) Please note: ...
Page 41
... 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=0 Abbreviation: /DB= /TOP If the option /TOP is used the option /OFFSET= specifies the address where ...
Page 42
Example: JTAG11x0 /DUMP /BMS This example makes a memory dump of the first 256 bytes of the Boot-EPROM. 42 JTAG_SA11x0b.doc ...
Page 43
... 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_SA11x0b.doc (if option /I2CBIG omitted) (if option /I2CBIG specified) ...
Page 44
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 45
... Options: /I2CBIG This option must be the first option after the filename. See function /PI2C (Chapter 2.5) /DEVICE-BASE=hhhhhh See function /PI2C (Chapter 2.5) /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 46
Example: JTAG11x0 /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 StrongARM SA-11x0. 46 JTAG_SA11x0b.doc ...
Page 47
... This option must be the first option after the filename. See function /PI2C (Chapter 2.5) /DEVICE-BASE=hhhhhh See function /PI2C (Chapter 2.5) /OFFSET=hhhhhh See function /PI2C (Chapter 2.5) /FILE-OFFSET=hhhhhh See function /PI2C (Chapter 2.5) /LENGTH=hhhhhh See function /PI2C (Chapter 2.5) /NODUMP See function /PI2C (Chapter 2.5) /I2CCLK=pin_name See function /PI2C (Chapter 2 ...
Page 48
See function /PI2C (Chapter 2.5) Example: JTAG11x0 /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 StrongARM ...
Page 49
... 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.5) /DEVICE-BASE=hhhhhh See function /PI2C (Chapter 2.5) 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 50
Specifies the CPU pin used for serial data input. Pin_name must specify a input pin otherwise an error message occurs. Example: JTAG11x0 /DUMPI2C /I2CCLK=FLAG0 /I2CDAT=FLAG1 This example makes a memory dump of the first 100h bytes of a serial ...
Page 51
Toggle CPU pins Usage: JTAG11x0 /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 52
Polling CPU pins Usage: JTAG11x0 /PIN? /PIN=pinname [optionlist] This command allows to test the hardware by polling CPU signals. Please Note: Not every pin of the Intel StrongARM SA-11x0 may be specified as an input pin. Options: /PIN=pin_name CPU ...
Page 53
Polling CPU pins while the CPU is running Usage: JTAG11x0 /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 54
Show status of all CPU pins while the CPU is running Usage: JTAG11x0 /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 55
Sample output: This is a sample output for a Intel StrongARM SA-1110 | 0 BATT_FAULT | 0 VDD_FAULT | 1 RXD_C | 1 TXD_C | D10 | ...
Page 56
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 57
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 58
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 59
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 60
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 60 JTAG_SA11x0b.doc ...