Preparing to program the board

If the board is to be programmed, whether via JTAG or RedBoot, some hardware settings need to be changed:

• Jumper across ST18 on the board to allow write access to the boot PROM.

• Set DIP switch S1-3 to OFF to allow RedBoot to write to the system flash.

• Set the switch S5 (on the front of the board) to boot from whichever flash is not being programmed. Note that the RedBoot image cannot access the flash from which it is currently executing (it can only access the other flash).

The RedBoot binary image files should also be copied to the TFTP pickup area on the host providing TFTP services if that is how RedBoot should pick up the images it is going to program into the flash. Alternatively, the images can be passed by YMODEM over the serial link.

Preparing to use the JTAG debugger

The JTAG debugger will also need setting up:

1. Install the JTAG debugger software (WICE103E) on a PC running Windows (WinNT is probably the best choice for this) in “C:/PanaX”.

2. Install the Matsushita provided “project” into the “C:/Panax/wice103e/prj” directory.

3. Install the RedBoot image files into the “C:/Panax/wice103e/prj” directory under the names redboot.ram and redboot.prom.

4. Make sure the PC's BIOS has the parallel port set to full bidirectional mode.

5. Connect the JTAG debugger to the PC's parallel port.

6. Connect the JTAG debugger to the board.

7. Set the switch on the front of the board to boot from “boot PROM”.

8. Power up the JTAG debugger and then power up the board.

9. Connect the board's Debug Serial port to a computer by a null modem cable.

10. Start minicom or some other serial communication software and set for 115200 baud, 1-N-8 with hardware (RTS/CTS) flow control.

Loading the RAM-based RedBoot via JTAG

To perform the first half of the operation, the following steps should be followed:

1. Start the JTAG debugger software.

2. Run the following commands at the JTAG debugger's prompt to set up the MMU registers on the CPU.

   ed 0xc0002000, 0x12000580 ed 0xd8c00100, 0x8000fe01 ed 0xd8c00200, 0x21111000 ed 0xd8c00204, 0x00100200 ed 0xd8c00208, 0x00000004 ed 0xd8c00110, 0x8400fe01 ed 0xd8c00210, 0x21111000 ed 0xd8c00214, 0x00100200 ed 0xd8c00218, 0x00000004 ed 0xd8c00120, 0x8600ff81 ed 0xd8c00220, 0x21111000 ed 0xd8c00224, 0x00100200 ed 0xd8c00228, 0x00000004 ed 0xd8c00130, 0x8680ff81 ed 0xd8c00230, 0x21111000 ed 0xd8c00234, 0x00100200 ed 0xd8c00238, 0x00000004 ed 0xd8c00140, 0x9800f801 ed 0xd8c00240, 0x00140000 ed 0xd8c00244, 0x11011100 ed 0xd8c00248, 0x01000001 ed 0xda000000, 0x55561645 ed 0xda000004, 0x000003c0 ed 0xda000008, 0x9000fe01 ed 0xda00000c, 0x9200fe01 ed 0xda000000, 0xa89b0654

3. Run the following commands at the JTAG debugger's prompt to tell it what regions of the CPU's address space it can access:

   ex 0x80000000,0x81ffffff,/mexram ex 0x84000000,0x85ffffff,/mexram ex 0x86000000,0x867fffff,/mexram ex 0x86800000,0x87ffffff,/mexram ex 0x8c000000,0x8cffffff,/mexram ex 0x90000000,0x93ffffff,/mexram

4. Instruct the debugger to load the RAM RedBoot image into RAM:

   _pc=90000000 u_pc rd redboot.ram,90000000

5. Load the boot PROM RedBoot into RAM:

   rd redboot.prom,91020000

6. Start RedBoot in RAM:

   g

   Note that RedBoot may take some time to start up, as it will attempt to query a BOOTP or DHCP server to try and automatically get an IP address for the board. Note, however, that it should send a plus over the serial port immediately, and the 7-segment LEDs should display “rh 8”.

Loading the boot PROM-based RedBoot via the RAM mode RedBoot

Once the RAM mode RedBoot is up and running, it can be communicated with by way of the serial port. Commands can now be entered directly to RedBoot for flashing the boot PROM.

1. Instruct RedBoot to initialise the boot PROM:

   RedBoot> fi init

2. Write the previously loaded redboot.prom image into the boot PROM:

   RedBoot> fi write -f 0x80000000 -b 0x91020000 -l 0x00020000

3. Check that RedBoot has written the image:

   RedBoot> dump -b 0x91020000 RedBoot> dump -b 0x80000000

   Barring the difference in address, the two dumps should be the same.

4. Close the JTAG software and power-cycle the board. The RedBoot banners should be displayed again over the serial port, followed by the RedBoot prompt. The boot PROM-based RedBoot will now be running.

5. Power off the board and unjumper ST18 to write-protect the contents of the boot PROM. Then power the board back up.

6. Run the following command to initialise the system flash:

   RedBoot> fi init

   Then program the system flash based RedBoot into the system flash:

   RedBoot> load -r -b %{FREEMEMLO} redboot_FLASH.bin RedBoot> fi write -f 0x84000000 -b %{FREEMEMLO} -l 0x00020000

   NOTE: RedBoot arranges the flashes on booting such that they always appear at the same addresses, no matter which one was booted from.

7. A similar sequence of commands can be used to program the boot PROM when RedBoot has been booted from an image stored in the system flash.

   RedBoot> load -r -b %{FREEMEMLO} /tftpboot/redboot_ROM.bin RedBoot> fi write -f 0x80000000 -b %{FREEMEMLO} -l 0x00020000

   See the Section called Persistent State Flash-based Configuration and Control in Chapter 2 for details on configuring the RedBoot in general, and also the Section called Flash Image System (FIS) in Chapter 2 for more details on programming the system flash.