Setup -- Preparing the MX1ADS/A board for eCos Development
Overview
In a typical development environment, the MX1ADS/A board boots from
flash into the RedBoot ROM monitor. eCos applications are configured
for RAM startup and then downloaded and run on the board via the
debugger arm-eabi-gdb. Preparing the board therefore
usually involves programming a suitable RedBoot image into flash
memory.
The following RedBoot configurations are supported:
Configuration
Description
Use
File
SRAM
RedBoot running from RAM, but loaded via the JTAG interface
redboot_SRAM.ecm
redboot_SRAM.bin
RAM
RedBoot running from RAM, usually loaded by another
version of RedBoot
redboot_RAM.ecm
redboot_RAM.bin
ROM
RedBoot running from ROM
redboot_ROM.ecm
redboot_ROM.bin
ROMRAM
RedBoot running from RAM, but contained in the board's flash boot sector
redboot_ROMRAM.ecm
redboot_ROMRAM.bin
For serial communications, all versions run with 8 bits, no parity,
and 1 stop bit at 38400 baud. RedBoot also supports ethernet
communication and flash management.
Initial Installation
Installing RedBoot is a matter of downloading a new binary
image and overwriting the existing Boot monitor ROM image.
There are two possible mechanisms for doing this, both via the JTAG
interface. The first uses the ability of some JTAG debuggers to write
directly to FLASH. The second merely uses the JTAG debugger to load
a version of RedBoot and to then use that to program the FLASH.
Direct FLASH Programming
The following instructions describe how to install RedBoot by
programming the FLASH directly from the JTAG debugger. At present
this has only been tried using an Abatron BDI2000 debugger and these
instruction apply to that device. However, it should be possible to
adapt these instructions to any other device.
The BDI2000 configuration file needs to be set up to initialize the
SDRAM and to tell it what type of FLASH device is present. The
resulting config file is shown below:
The BDI2000 needs to be rebooted to cause it to reload this
configuration file. Once this is done connect to the BDI2000 via its
telnet port and issue a reset command:
Now ensure that the FLASH is erased. The following command uses the
ERASE entries in the configuration file to erase
the first 9 blocks in the FLASH.
Core#0>erase
Erasing flash at 0x10000000
Erasing flash at 0x10004000
Erasing flash at 0x10008000
Erasing flash at 0x1000c000
Erasing flash at 0x10010000
Erasing flash at 0x10014000
Erasing flash at 0x10018000
Erasing flash at 0x1001c000
Erasing flash at 0x10020000
Erasing flash passed
Core#0>
Copy redboot_ROMRAM.bin to the root directory of
the same TFTP server used to fetch the configuration file and execute
the following command:
If this completes successfully then the FLASH has been programmed. You
can start RedBoot by issuing the go command, or by
detaching the BDI2000 and cycling the power switch of the board. You
should see the RedBoot startup screen:
+... waiting for BOOTP information
Ethernet eth0: MAC address 0e:00:00:ea:18:f0
IP: 10.0.0.207/255.255.255.0, Gateway: 10.0.0.3
Default server: 10.0.0.1, DNS server IP: 10.0.0.1
RedBoot(tm) bootstrap and debug environment [ROMRAM]
Non-certified release, version UNKNOWN - built 15:51:18, Jul 19 2004
Platform: Motorola MX1ADS/A (ARM9)
Copyright (C) 2000, 2001, 2002, Free Software Foundation, Inc.
Copyright (C) 2003, 2004, eCosCentric Limited
RAM: 0x00000000-0x02000000, [0x0002f778-0x01fdd000] available
FLASH: 0x10000000 - 0x12000000, 256 blocks of 0x00020000 bytes each.
RedBoot>
Download RedBoot
The following instructions describe how to install RedBoot via the
JTAG interface by downloading a version of RedBoot to program the
FLASH. This is a two stage process, you must first download a
RAM-resident version of RedBoot and then use that to download the ROM
image to be programmed into the flash memory. The following directions
are necessarily somewhat general since the specifics depend on the
exact JTAG device available, and the software used to drive it.
Connect the JTAG device to the JTAG connector on the MX1ADS/A board
and check that the device is functioning correctly. Using 32 bit
memory writes, initialize the static memory controller so that the SDRAM
and flash are accessible. The following assignments should be made:
Now load the SRAM redboot binary image from the file
redboot_SRAM.bin into SDRAM at
0x08040000. Exactly how you do this depends on the JTAG driver
software. Note that it may be easier to load the ELF or SREC files, if
supported, since these contain the correct load addresses.
Connect the serial port of a host machine to UART 1 on the MX1ADS/A
board and start a terminal emulator (for example
HyperTerminal on Windows,
minicom on Linux) set up to communicate at 38400
baud, 8 bits, one stop bit, no parity. Start RedBoot by executing
from location 0x08040000, which should result in RedBoot starting up
and emitting this message on the serial channel:
+... waiting for BOOTP information
Ethernet eth0: MAC address 0e:00:00:ea:18:f0
IP: 10.0.0.207/255.255.255.0, Gateway: 10.0.0.3
Default server: 10.0.0.1, DNS server IP: 10.0.0.1
RedBoot(tm) bootstrap and debug environment [SRAM]
Non-certified release, version UNKNOWN - built 15:50:10, Jul 19 2004
Platform: Motorola MX1ADS/A (ARM9)
Copyright (C) 2000, 2001, 2002, Free Software Foundation, Inc.
Copyright (C) 2003, 2004, eCosCentric Limited
RAM: 0x08000000-0x0c000000, [0x08065ea0-0x0bfdd000] available
FLASH: 0x10000000 - 0x12000000, 256 blocks of 0x00020000 bytes each.
RedBoot>
Now the ROM image can be downloaded using the following RedBoot
command:
RedBoot> load -r -b %{FREEMEMLO} -m ymodem
Use the terminal emulator's Ymodem support to send the file
redboot_ROMRAM.bin. This should result in
something like the following output:
Raw file loaded 0x08066000-0x080b900d, assumed entry at 0x08066000
xyzModem - CRC mode, 2659(SOH)/0(STX)/0(CAN) packets, 5 retries
RedBoot>
Once the file has been uploaded, you can check that it has been
transferred correctly using the cksum command. On
the host (Linux or Cygwin) run the cksum program on
the binary file:
The second number in the output of the host cksum
program is the file size, which should be used as the argument to the
-l option in the RedBoot cksum
command. The first numbers in each instance are the checksums, which
should be equal.
If the program has downloaded successfully, then it can be programmed
into the flash using the following commands:
RedBoot> fis init
About to initialize [format] FLASH image system - continue (y/n)?y
*** Initialize FLASH Image System
... Erase from 0x11fe0000-0x12000000: .
... Program from 0x0bfe0000-0x0c000000 at 0x11fe0000: .
RedBoot> fis create -b %{FREEMEMLO} RedBoot
An image named 'RedBoot' exists - continue (y/n)?y
... Erase from 0x10000000-0x10020000: .
... Program from 0x08066000-0x08086000 at 0x10000000: .
... Erase from 0x11fe0000-0x12000000: .
... Program from 0x0bfe0000-0x0c000000 at 0x11fe0000: .
RedBoot>
The MX1ADS/A board may now be disconnected from the JTAG device and
reset by cycling the power. It should then display the startup screen
for the ROMRAM version of RedBoot:
+... waiting for BOOTP information
Ethernet eth0: MAC address 0e:00:00:ea:18:f0
IP: 10.0.0.207/255.255.255.0, Gateway: 10.0.0.3
Default server: 10.0.0.1, DNS server IP: 10.0.0.1
RedBoot(tm) bootstrap and debug environment [ROMRAM]
Non-certified release, version UNKNOWN - built 15:51:18, Jul 19 2004
Platform: Motorola MX1ADS/A (ARM9)
Copyright (C) 2000, 2001, 2002, Free Software Foundation, Inc.
Copyright (C) 2003, 2004, eCosCentric Limited
RAM: 0x00000000-0x02000000, [0x0002f778-0x01fdd000] available
FLASH: 0x10000000 - 0x12000000, 256 blocks of 0x00020000 bytes each.
RedBoot>
Rebuilding RedBoot
Should it prove necessary to rebuild a RedBoot binary, this is done
most conveniently at the command line. The steps needed to rebuild the
the ROMRAM version of RedBoot for the MX1ADS/A are:
$ mkdir redboot_mx1ads_a_romram
$ cd redboot_mx1ads_a_romram
$ ecosconfig new mx1ads_a redboot
$ ecosconfig import $ECOS_REPOSITORY/hal/arm/arm9/mx1ads_a/VERSION/misc/redboot_ROMRAM.ecm
$ ecosconfig resolve
$ ecosconfig tree
$ make
To rebuild the SRAM version of RedBoot:
$ mkdir redboot_mx1ads_a_sram
$ cd redboot_mx1ads_a_sram
$ ecosconfig new mx1ads_a redboot
$ ecosconfig import $ECOS_REPOSITORY/hal/arm/arm9/mx1ads_a/VERSION/misc/redboot_SRAM.ecm
$ ecosconfig resolve
$ ecosconfig tree
$ make
At the end of the build the install/bin subdirectory should contain
the file redboot.bin. This is the case for both
the above builds, take care not to mix the two files up, since
programming the SRAM RedBoot into the ROM will render the board
unbootable.
