Chapter 5. Installation and Testing

Table of Contents
AM3x/MN103E010 Matsushita MN103E010 (AM33/2.0) ASB2305 Board
ARM/ARM7 ARM Evaluator7T
ARM/ARM7+ARM9 ARM Integrator
ARM/ARM7+ARM9 ARM PID Board and EPI Dev7+Dev9
ARM/ARM7 Atmel AT91 Evaluation Boards (EBXX)
ARM/ARM7 Atmel JTST Evaluation Board (AT572D740-DK1)
ARM/ARM7 Cirrus Logic EP7xxx (EDB7211, EDB7212, EDB7312)
ARM/ARM9 Agilent AAED2000
ARM/ARM9 Altera Excalibur
ARM/StrongARM(SA110) Intel EBSA 285
ARM/StrongARM(SA1100) Intel Brutus
ARM/StrongARM(SA1100) Intel SA1100 Multimedia Board
ARM/StrongARM(SA1110) Intel SA1110 (Assabet)
ARM/StrongARM(SA11X0) Bright Star Engineering commEngine and nanoEngine
ARM/StrongARM(SA11X0) Compaq iPAQ PocketPC
ARM/StrongARM(SA11X0) Intrinsyc CerfCube
ARM/XScale Cyclone IQ80310
ARM/XScale Intel IQ80321
ARM/Intel XScale IXDP425 Network Processor Evaluation Board
ARM/Intel XScale Generic Residential Gateway
Motorola PrPMC1100 CPU card
CalmRISC/CalmRISC16 Samsung CalmRISC16 Core Evaluation Board
CalmRISC/CalmRISC32 Samsung CalmRISC32 Core Evaluation Board
FRV/FRV400 Fujitsu FR-V 400 (MB-93091)
Fujitsu FR-V Design Kit (MB93091-CBxx)
Fujitsu FR-V Portable Demonstration Kit (MB93093-PD00)
IA32/x86 x86-Based PC
MIPS/MIPS32(CoreLV 4Kc)+MIPS64(CoreLV 5Kc) Atlas Board
MIPS/MIPS32(CoreLV 4Kc)+MIPS64(CoreLV 5Kc) Malta Board
MIPS/RM7000 PMC-Sierra Ocelot
PowerPC/MPC860T Analogue & Micro PowerPC 860T
PowerPC/MPC8XX Motorola MBX
SuperH/SH3(SH7708) Hitachi EDK7708
SuperH/SH3(SH7709) Hitachi Solution Engine 7709
SuperH/SH3(SH7729) Hitachi HS7729PCI
SuperH/SH3(SH77X9) Hitachi Solution Engine 77X9
SuperH/SH4(SH7751) Hitachi Solution Engine 7751

AM3x/MN103E010 Matsushita MN103E010 (AM33/2.0) ASB2305 Board


RedBoot supports the debug serial port and the built in ethernet port for communication and downloads. The default serial port settings are 115200,8,N,1 with RTS/CTS flow control. RedBoot can run from either flash, and can support flash management for either the boot PROM or the system flash regions.

The following RedBoot configurations are supported:

PROM[ROM]RedBoot running from the boot PROM and able to access the system flash.redboot_ROM.ecm
FLASH[ROM]RedBoot running from the system flash and able to access the boot PROM.redboot_FLASH.ecm
RAM[RAM]RedBoot running from RAM and able to access the boot PROM.redboot_RAM.ecm

Initial Installation

Unless a pre-programmed system flash module is available to be plugged into a new board, RedBoot must be installed with the aid of a JTAG interface unit. To achieve this, the RAM mode RedBoot must be loaded directly into RAM by JTAG and started, and then that must be used to store the ROM mode RedBoot into the boot PROM.

These instructions assume that you have binary images of the RAM-based and boot PROM-based RedBoot images available.

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:

    rd redboot.ram,90000000
  5. Load the boot PROM RedBoot into RAM:

    rd redboot.prom,91020000
  6. Start RedBoot in RAM:


    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.

Additional Commands

The exec command which allows the loading and execution of Linux kernels, is supported for this architecture (see the Section called Executing Programs from RedBoot in Chapter 2). The exec parameters used for ASB2305 board are:

-w <time>

Wait time in seconds before starting kernel

-c "params"

Parameters passed to kernel


Kernel entry point, defaulting to the entry point of the last image loaded

The parameter string is stored in the on-chip memory at location 0x8C001000, and is prefixed by “cmdline:” if it was supplied.

Memory Maps

RedBoot sets up the following memory map on the ASB2305 board.

NOTE: The regions mapped between 0x80000000-0x9FFFFFFF are cached by the CPU. However, all those regions can be accessed uncached by adding 0x20000000 to the address.

Physical Address Range   Description
-----------------------  -----------
0x80000000 - 0x9FFFFFFF  Cached Region
0x80000000 - 0x81FFFFFF  Boot PROM
0x84000000 - 0x85FFFFFF  System Flash
0x86000000 - 0x86007FFF  64Kbit Sys Config EEPROM
0x86F90000 - 0x86F90003  4x 7-segment LEDs
0x86FA0000 - 0x86FA0003  Software DIP Switches
0x86FB0000 - 0x86FB001F  PC16550 Debug Serial Port
0x8C000000 - 0x8FFFFFFF  On-Chip Memory (repeated 16Kb SRAM)
0x90000000 - 0x93FFFFFF  SDRAM
0x98000000 - 0x9BFFFFFF  Paged PCI Memory Space (64Mb)
0x9C000000 - 0x9DFFFFFF  PCI Local SRAM (32Mb)
0x9E000000 - 0x9E03FFFF  PCI I/O Space
0x9E040000 - 0x9E0400FF  AM33-PCI Bridge Registers
0x9FFFFFF4 - 0x9FFFFFF7  PCI Memory Page Register
0x9FFFFFF8 - 0x9FFFFFFF  PCI Config Registers
0xA0000000 - 0xBFFFFFFF  Uncached Mirror Region
0xC0000000 - 0xDFFFFFFF  CPU Control Registers

The ASB2305 HAL makes use of the on-chip memory in the following way:

0x8C000000 - 0x8C0000FF  hal_vsr_table
0x8C000100 - 0x8C0001FF  hal_virtual_vector_table
0x8C001000 -             Linux command line (RedBoot exec command)
           - 0x8C003FFF  Emergency DoubleFault Exception Stack

Currently the CPU's interrupt table lies at the beginning of the RedBoot image, which must therefore be aligned to a 0xFF000000 mask.

Rebuilding RedBoot

These shell variables provide the platform-specific information needed for building RedBoot according to the procedure described in Chapter 3:

export TARGET=asb2305
export ARCH_DIR=mn10300
export PLATFORM_DIR=asb2305

The names of configuration files are listed above with the description of the associated modes.