RedBoot™ User's Guide: Document Version 1.9, February 2003 | ||
---|---|---|
Prev | Chapter 5. Installation and Testing | Next |
RedBoot supports the serial port labelled 'modem inteface' on the board and the ethernet port. The default serial port settings are 38400,8,N,1. RedBoot also supports flash management on the SEB9312. Two basic RedBoot configurations are supported:
RedBoot running from RAM, but contained in the board's flash boot sector (ROMRAM mode).
RedBoot running standalone from RAM.
NOTE: The cache is currently disabled as this feature does not seem to work properly with the beta silicon; it interacts badly with flash management activities and network usage.
A Windows or Linux utility is used to program flash using the 'modem interface' serial port via on-chip programming firmware. See board documentation for details on in situ flash programming.
To update the primary RedBoot images, follow the procedures detailed in the Section called Update the primary RedBoot flash image in Chapter 4, but the actual numbers used with the flags in the sample commands should be:
-f 0x24000000 -b 0x00100000 -l 0x20000 |
Note that since the primary RedBoot image copies itself to RAM and runs from RAM (“ROMRAM” startup), it is not necessary to run a separate RAM-only RedBoot during this update process; you can use the primary RedBoot image to update the primary RedBoot image in situ.
To update the secondary RedBoot images, follow the procedures detailed in the Section called Load and start a different version of RedBoot, running from RAM in Chapter 4, but the actual numbers used with the flags in the sample commands should be:
-f 0x24020000 -b 0x40000 -r 0x40000 -l 0x20000 -e 0x40040 |
No special commands.
One special fconfig option is provided to control the ethernet station address (ESA or 'MAC address').
RedBoot> fco -l .... Local IP address: 10.16.19.10 Default server IP address: 10.16.19.66 Network hardware address [MAC]: 0x00:0x12:0x34:0x56:0x78:0xAB ... RedBoot> fco ep93xx_esa ep93xx_esa: 0x00:0x12:0x34:0x56:0x78:0xAB |
The MMU page tables are located at the end of DRAM.
NOTE: The virtual memory maps in this section use a C and B column to indicate whether or not the region is cached (C) or buffered (B).
Physical Address Range Description ----------------------- ---------------------------------- 0x00000000 - 0x01ffffff DRAM 0x24000000 - 0x247fffff Flash 0x28000000 - 0x280fffff SRAM 0x80000000 - 0x8fffffff I/O registers Virtual Address Range C B Description ----------------------- - - ---------------------------------- 0x00000000 - 0x01ffffff Y Y DRAM 0x24000000 - 0x247fffff Y Y Flash 0x28000000 - 0x2800ffff Y Y On-chip SRAM 0x80000000 - 0x8fffffff N N I/O registers 0xC0000000 - 0xC1ffffff N N Non-cachable access to DRAM The flash based RedBoot image occupies virtual addresses 0x24000000 - 0x2401ffff. |
The ROMRAM startup RedBoot image occupies RAM addresses 0x08000 - 0x3ffff. RAM addresses from 0x40000 to the end of RAM are available for general use such as a temporary scratchpad for downloaded images before they are written to flash.
The RAM based RedBoot image occupies RAM addresses 0x40000 - 0x68000. RAM addresses from 0x68000 to the end of RAM are available for general use.
In either case, memory from 0x0 - 0x07fff is reserved for system vectors and the VM translation tables.
The instructions in Chapter 3 should be followed. The values for ARCH_DIR and PLATFORM_DIR on this platform are “arm” and “arm9/ep93xx” respectively. The value for TARGET is “seb9312”. Note that the configuration export files supplied in the hal/arm/arm9/ep93xx/VERSION/misc directory in the RedBoot source tree should be used. Use only the ROMRAM and RAM type configuration export files.