FS-9017 Digi International, FS-9017 Datasheet
FS-9017
Specifications of FS-9017
Related parts for FS-9017
FS-9017 Summary of contents
Page 1
... JTAG-Booster for IBM PPC405xxx 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 September 10, 2003 Dieter Fögele JTAG_PPC405a.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 IBM PPC405EP ......................................................9 1.6. First Example with ...
Page 4
General The programs JT405EP.EXE and JT405GPr.EXE use the JTAG port of the IBM PPC405xxx mircocontrollers in conjunction with the small JTAG-Booster: to program data into flash memory to verify and read the contents of a flash memory to make ...
Page 5
Ordering Information The following related products are available 9017 JTAG-Booster IBM PPC405xxx, 3.3V, PPC405EP and PPC405GPr DOS/Win9x/WinNT/Win2000/WinXP, delivered with adapter type 285 1.2. System Requirements To successfully run this tool the following requirements must be met: MSDOS, WIN3.x, WIN9x, ...
Page 6
Contents of Distribution Disk JT405EP.EXE Tool for IBM PPC405EP JT405EP.OVL JT405EP.INI Template configuration file for IBM PPC405EP. See chapter 1.9 "Initialization file JT405xxx.INI" JT405GPr.EXE Tool for IBM PPC405GPr JT405GPr.OVL JT405GPr.INI Template configuration file for IBM PPC405GPr. See chapter 1.9 ...
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 part 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
The utility is started with the general command line format: JTAGxxx JT405xxx /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 JT405xxx, ...
Page 9
... 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 JT405EP /P MYAPP.BIN at the DOS prompt results in the following output: JT405EP --- JTAG utility for IBM PPC405EP Copyright FS FORTH-SYSTEME GmbH, Breisach Version 4.xx of mm/dd/yyyy (1) Configuration loaded from file JT405EP.INI (2) Target: Generic Target (3) ...
Page 10
... The position of the JTAG instruction register of the IBM PPC405EP is assumed to be zero, if not specified in the command line (see option /IROFFS=). (9) The real length of the boundary scan register is displayed here and compared with the boundary scan register length of a IBM PPC405EP. ...
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 JT405GPr /P MYAPP.BIN at the DOS prompt results in the following output: JT405GPr --- JTAG utility for IBM PPC405GPr Copyright FS FORTH-SYSTEME GmbH, Breisach Version 4.xx of mm/dd/yyyy (1) Configuration loaded from file JT405GPr.INI (2) Target: Generic Target (3) ...
Page 12
... The position of the JTAG instruction register of the IBM PPC405GPris assumed to be zero, if not specified in the command line (see option /IROFFS=). (9) The real length of the boundary scan register is displayed here and compared with the boundary scan register length of a IBM PPC405GPr. ...
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. Disk full Writing a output file was aborted as a result of missing disk space. ...
Page 15
Error: Pin-Name is an output only pin The specified pin cannot be sampled. Check the command line. Check the initialization file. Error: Pin-Name is an input only pin The specified pin cannot be activated. Check the command line. Check the ...
Page 16
Please check the syntax in your configuration file. (See chapter 1.9 “Initialization file JT405xxx.INI”). LPTx not installed The LPT port specified with /LPTx cannot be found. Please check the LPT port or specify a installed LPT ...
Page 17
... The sum of all instruction register bits in the JTAG chain does not fit to the IBM PPC405xxx. 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 IBM PPC405xxx. 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 JTAG_PPC405a.doc ...
Page 19
Initialization file JT405xxx.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 IBM PPC405xxx. The Target-Entry is used to identify your design ...
Page 20
Sample File JT405EP.INI: // Description file for IBM PPC405EP Target: Generic Target, 2003/08/26 // Adapt this file carefully to your design!! // All chip select signals are set to output and inactive. // All signals should be defined. Undefined signals ...
Page 21
The following pins are output only pins. // Setting to input (tristate) one of these pins results in an error. // These are used for Flash programming PER_ADDR6 Out,Lo // PER_ADDR7 Out,Lo // PER_ADDR8 Out,Lo // PER_ADDR9 Out,Lo // ...
Page 22
Group 278: All pins in this group must be set to the same direction // These pins are bidirectional MEM_DATA8 Inp // MEM_DATA9 Inp // MEM_DATA10 Inp // MEM_DATA11 Inp // MEM_DATA12 Inp // MEM_DATA12 Inp // MEM_DATA14 Inp ...
Page 23
Group 125: All pins in this group must be set to the same direction // These pins are bidirectional PCI_AD0 Inp // PCI_AD1 Inp // PCI_AD2 Inp // PCI_AD3 Inp // // Group 132: All pins in this group ...
Page 24
Group 184: All pins in this group must be set to the same direction // These pins are bidirectional PCI_AD24 Inp // PCI_AD25 Inp // PCI_AD26 Inp // PCI_AD27 Inp // // Group 190: All pins in this group ...
Page 25
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 an input. IIC_SDA Inp // IIC_SCL Inp // UART0_DCD# Inp // ...
Page 26
The following pins are output only pins. // Setting to input (tristate) one of these pins results in an error. DQM0 Out,Lo // DQM1 Out,Lo // DQM2 Out,Lo // DQM3 Out,Lo // EMC0_TX0EN Out,Lo // EMC0_TX0ERR Out,Lo // EMC0_TX0D0 ...
Page 27
MEM_RAS# Out,Lo // MEM_CAS# Out,Lo // MEM_WE# Out,Lo // MEM_CLKOUT0 Out,Lo // MEM_CLKOUT1 Out,Lo // MEM_CLKEN0 Out,Lo // MEM_CLKEN1 Out,Lo // BANKSEL0# Out,Lo // BANKSEL1# Out, The following pins are input only. // Setting to output of one ...
Page 28
Sample File JT405GPr.INI: In preparation 28 JTAG_PPC405a.doc ...
Page 29
Supported flash devices Type JT405xxx /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_PPC405a.doc 29 ...
Page 30
... When you start JT405xxx.EXE without any parameters the following help screen with all possible functions and options is displayed: JT405xxx --- JTAG utility for IBM PPC405xxx Copyright © FS FORTH-SYSTEME GmbH, Breisach Version 4.xx of mm/dd/yyyy Programming of Flash-EPROMs and hardware tests on targets with the IBM PPC405xxx. ...
Page 31
... Note: The initialization file is not loaded for the functions /SAMPLE (chapter 2.11) and /SNAP (chapter 2.12). Default: /INI=JT405xxx.INI JTAG_PPC405a.doc /CS2 /CS3 /NOWRSETUP /TOP /P /NODUMP /LPT1 /LPT2 /8BIT /NOMAN /FO= /OFFSET= /DRIVER= /PIN= /I2CCLK= I2CBIG /WATCH= /CS4 /BYTE-MODE /NOERASE /LPT3 /LENGTH= /O= /IROFFS= /I2CDAT= /OUT= 31 ...
Page 32
... This pin may be the trigger of a watchdog. This pin must be specified as output in the initialization file. /IROFFS= Specifies the position of the IBM PPC405xxx instruction register within the JTAG chain. In most cases this option is not needed. Default: /IROFFS=0 32 JTAG_PPC405a.doc ...
Page 33
Specifies the position of the IBM PPC405xxx within the JTAG chain. Default: /CPUPOS=0 JTAG_PPC405a.doc 33 ...
Page 34
Program a Flash Device Usage: JT405xxx /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 35
... 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 36
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 37
Examples: JT405xxx /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. JT405xxx /P CE.ROM /32BIT /CS1 This example programs the file CE.ROM ...
Page 38
... 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 39
... 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 /CS4 See function /P (Chapter 2 ...
Page 40
... 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) 40 JTAG_PPC405a.doc ...
Page 41
See function /P (Chapter 2.1) /NODUMP See function /P (Chapter 2.1) /CS0 /CS1 /CS2 /CS3 /CS4 See function /P (Chapter 2.1) /NOWRSETUP See function /P (Chapter 2.1) Please note: In the function /V write cycles are needed to detect ...
Page 42
... 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 43
Example: JT405xxx /DUMP This example makes a memory dump of the first 256 bytes of the Boot-EPROM. JTAG_PPC405a.doc 43 ...
Page 44
... 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= 44 (if option /I2CBIG omitted) (if option /I2CBIG specified) ...
Page 45
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 46
... 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 47
Example: JT405xxx /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 IBM PPC405xxx. JTAG_PPC405a.doc 47 ...
Page 48
... 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 49
See function /PI2C (Chapter 2.5) Example: JT405xxx /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 IBM PPC405xxx. ...
Page 50
... 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 51
Specifies the CPU pin used for serial data input. Pin_name must specify a input pin otherwise an error message occurs. Example: JT405xxx /DUMPI2C /I2CCLK=FLAG0 /I2CDAT=FLAG1 This example makes a memory dump of the first 100h bytes of a serial ...
Page 52
Toggle CPU pins Usage: JT405xxx /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 53
Polling CPU pins Usage: JT405xxx /PIN? /PIN=pinname [optionlist] This command allows to test the hardware by polling CPU signals. Please Note: Not every pin of the IBM PPC405xxx may be specified as an input pin. Options: /PIN=pin_name CPU pin ...
Page 54
Polling CPU pins while the CPU is running Usage: JT405xxx /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 55
Show status of all CPU pins while the CPU is running Usage: JT405xxx /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 56
Sample output: This is a sample output for a IBM PPC405EP | 0 DQM2 | 1 MEM_DATA21 | 1 MEM_DATA23 | 0 MEM_DATA24 | 1 MEM_DATA25 | 1 MEM_DATA26 | 1 DQM3 | 1 UART0_CTS UART0_RX | 1 ...
Page 57
IRQ5 | 1 IRQ4 | 1 GPIO7 | 1 GPIO6 | 1 IRQ2 | 0 IRQ1 | 0 GPIO3 | 1 GPIO2 | 1 PHY0_RX0D1 | 1 GPIO1 | 0 MEM_ADDR11 | 1 SYS_RESET MEM_ADDR7 | ...
Page 58
Implementation Information This chapter summarizes some information about the implementation of the JTAG-Booster and describes some restrictions. The JTAG-Booster currently uses Boundary Scan to perform Flash programming. The Debug Interface of the PPC405 is not used. The software assumes ...
Page 59
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 60
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 61
Support for Windows NT, Windows 2000 and Windows XP A configured run time version of the "Kithara DOS Enabler, Version 6.x" is used to give support for some of our DOS based tools (like the JTAG-Booster) for Windows NT, ...
Page 62
... Now you can install the Kithara 6.x as described above. 5.4. De-Installation version 5.x/6.x: For deinstallation of the runtime version of the "Kithara DOS-Enabler Version 5.x/6.x": use: Settings - Control-Panel - Add/Remove Programs and remove the “FS FORTH-SYSTEME WinNT Support” and/or “WinNT Support for JTAG-Booster and FLASH166” Reboot your PC 62 JTAG_PPC405a.doc ...