Setup

Preparing the Abatron BDI2000 JTAG debugger

The BDI2000 must first be configured to allow communication with your local network, and configured with the parameters for interfacing with the target board. The following steps should be followed:

1. Prepare a PC to act as a host PC and start a TFTP server on it.

2. Connect the Abatron BDI2000 JTAG debugger via both serial and ethernet to the host PC and power it on. Use the serial cable supplied with the BDI2000.

3. Install the Abatron BDI2000 bdiGDB support software on the host PC.

4. Confirm that the XScale firmware is resident in the BDI2000. For example, using the bdisetup utility:

   $ bdisetup -v -s BDI Type : BDI2000 Rev.C (SN: xxxxxxxx) Loader : V1.05 Firmware : V1.08 bdiGDB for XScale Logic : V1.03 XScale MAC : 00-0c-01-96-64-92 IP Addr : 192.168.7.220 Subnet : 255.255.255.0 Gateway : 192.168.7.1 Host IP : 192.168.7.9 Config : /ixdp425.cfg

   To upload firmware if needed, follow the procedures in the BDI2000 manual, for example using the bdisetup utility:

   $ bdisetup -u -p/dev/ttyS0 -b57 -aGDB -tXSCALE Connecting to BDI loader Erasing CPLD Programming firmware with ./b20xscgd.108 Erasing firmware flash .... Erasing firmware flash passed Programming firmware flash .... Programming firmware flash passed Programming CPLD with ./xscjed21.103

5. Locate the file ixdp425.cfg within the BDI2000 software installation.

6. Locate the file regIXP425.def within the installation of the BDI2000 bdiGDB support software.

7. Place the ixdp425.cfg file in a location on the PC accessible to the TFTP server. Later you will configure the BDI2000 to load this file via TFTP as its configuration file.

8. Similarly place the file regIXP425.def in a location accessible to the TFTP server.

9. Open ixdp425.cfg in an editor such as emacs or notepad and if necessary adjust the path of the regIXP425.def file in the [REGS] section to match its location relative to the TFTP server root. Also comment out with a ';' the IP line in the [HOST] section, or update it to refer to the development PC.

10. Install and configure the Abatron BDI2000 in line with the bdiGDB instruction manual. Configure the BDI2000 to use the ixdp425.cfg configuration file at the appropriate point of this process. For example, using the bdisetup utility:

    $ bdisetup -c -p/dev/ttyS0 -b57 -i192.168.7.220 -h192.168.7.9 -m255.255.255.0 -g192.168.7.1 -f/ixdp425.cfg Connecting to BDI loader Writing network configuration Configuration passed

    The above command uses the first serial port at 57,600 baud to set the BDI2000's IP address to 192.168.7.220, its default TFTP host to 192.168.7.9, the network mask to 255.255.255.0, the default gateway to 192.168.7.1, and the configuration file to load to /ixdp425.cfg.

Preparing the IXDP425 board for programming

Follow the steps in this section in order to allow communication between the board and the host PC, and between the board and the JTAG device.

1. First you must connect a straight through DB9 serial cable between the high speed serial port labelled UART0 on the board and a serial port on the host computer.

2. Start a suitable terminal emulator on the host computer such as minicom or HyperTerminal. Set the communication parameters to 115200 baud, 8 data bits, no parity bit and 1 stop bit with no flow control.

3. If using a PCI ethernet card, connect the board to your host PC's LAN with an Ethernet cable.

4. If using a PCI ethernet card, you may need to designate the ethernet interface with a new Ethernet MAC address. The RedBoot binary image contains a default address, but each board requires its own unique address. It is advisable to mark each board with its programmed MAC address for future identification.

5. Connect the board to the BDI2000 using a 20-pin ARM/Xscale cable from the JTAG/ICE interface connector (J12) to the Target A port on the BDI2000.

6. Power up the IXDP425 board. You should see the hex display and various LEDs illuminate.

7. Connect to the BDI2000's CLI interface via TCP/IP on the standard telnet port 23. The telnet application is suitable for this. You should see usage information followed by the prompt:

   Core#0>

8. Confirm correct connection with the BDI2000 with the reset halt command as follows:

   Core#0> reset halt - TARGET: processing reset request - TARGET: BDI asserts RESET and TRST - TARGET: BDI removed TRST - TARGET: Bypass check: 0x000000001 => 0x00000001 - TARGET: JTAG exists check passed - Core#0: ID code is 0x19274013 - Core#0: BDI sets hold_rst and halt mode - TARGET: BDI removes RESET - Core#0: BDI sets hold_rst and halt mode again - Core#0: BDI loads debug handler to mini IC - Core#0: BDI clears hold_rst - TARGET: resetting target passed - TARGET: processing target startup .... - TARGET: processing target startup passed Core#0>

9. Locate the redboot_ROM.bin image within the loaders subdirectory of the base of the eCos installation.

10. Copy the redboot_ROM.bin file into a location on the host computer accessible to its TFTP server.

Using the BDI2000 to directly program RedBoot into Flash

As previously mentioned, there are two methods of programming a RedBoot image into the parallel NOR Flash via JTAG, depending on the capabilities of the JTAG device. The BDI2000 supports direct programming of the Flash device and so that is the approach described here.

This is a three stage process. The relevant Flash blocks must first be unlocked, then erased, and finally programmed. This can be accomplished with the following steps:

1. Connect to the BDI2000 telnet port as before.

2. Use the following commands in the BDI2000 telnet session to unlock and then erase the relevant Flash blocks that will contain RedBoot.

   Core#0>unlock 0x50000000 0x20000 4 Unlocking flash at 0x50000000 Unlocking flash at 0x50020000 Unlocking flash at 0x50040000 Unlocking flash at 0x50060000 Unlocking flash passed Core#0>erase 0x50000000 0x20000 4 Erasing flash at 0x50000000 Erasing flash at 0x50020000 Erasing flash at 0x50040000 Erasing flash at 0x50060000 Erasing flash passed

3. Program the RedBoot image into Flash with the following command, replacing /RBPATH with the location of the redboot_ROM.bin file relative to the TFTP server root directory:

   Core#0>prog 0x50000000 /RBPATH/redboot_ROM.bin bin Programming /RBPATH/redboot_ROM.bin , please wait .... Programming flash passed Core#0>

   This operation can take some time.

The RedBoot installation is now complete. This can be tested by powering off the board, disconnecting the JTAG, and then powering on the board again. The RedBoot banner should be visible on the serial port. The message

flash configuration checksum error or invalid key

If it proves necessary to re-install RedBoot, this may be achieved by repeating the above process. Alternatively, a new image may be downloaded and programmed into flash more directly using RedBoot's own commands. See the RedBoot documentation for details.