| 1 | # |
|---|
| 2 | # $Id$ |
|---|
| 3 | # |
|---|
| 4 | |
|---|
| 5 | BSP supporting the on-CPU capabilities of the Synova Mongoose-V. |
|---|
| 6 | This BSP assumes that basic HW initialization is performed by |
|---|
| 7 | PMON. |
|---|
| 8 | |
|---|
| 9 | Address Map |
|---|
| 10 | =========== |
|---|
| 11 | This is the generic address map of the Mongoose-V prototyping board |
|---|
| 12 | this BSP was tested on. |
|---|
| 13 | |
|---|
| 14 | 0x8000_0000 - 0x8FFF_FFFF - RAM (KSEG0 cached) |
|---|
| 15 | 0xA000_0000 - 0xAFFF_FFFF - RAM (KSEG1, same memory uncached) |
|---|
| 16 | 0xBFC0_0000 - 0xBFFF_FFFF - EEPROM |
|---|
| 17 | 0xFFFE_xxxx - on-CPU peripherals |
|---|
| 18 | |
|---|
| 19 | This is the hardware address map of the board used as it was |
|---|
| 20 | actually populated. |
|---|
| 21 | |
|---|
| 22 | 0x8000_0000 - 0x83FF_FFFF - 32 MB RAM (KSEG0 cached) |
|---|
| 23 | 0xA000_0000 - 0xA3FF_FFFF - 32 MB RAM (KSEG1, same memory uncached) |
|---|
| 24 | 0xBFC0_0000 - 0xBFDF_FFFF - 2 MB EEPROM |
|---|
| 25 | 0xFFFE_xxxx - on-CPU peripherals |
|---|
| 26 | |
|---|
| 27 | This is the organization of the EEPROM when fully populated. Since |
|---|
| 28 | the board used to develop this BSP only had the first bank of EEPROM |
|---|
| 29 | populated, only the first program image area was used. |
|---|
| 30 | |
|---|
| 31 | 0xBFC0_0000 - 0xBFC3_FFFF - PMON |
|---|
| 32 | 0xBFC4_0000 - 0xBFC4_FFFF - reserved for boot loader |
|---|
| 33 | 0xBFC5_0000 - 0xBFDF_FFFF - reserved for program 1 image |
|---|
| 34 | 0xBFE0_0000 - 0xBFFF_FFFF - reserved for program 2 image |
|---|
| 35 | |
|---|
| 36 | The Mongoose-V on this board is at 12 Mhz. |
|---|
| 37 | |
|---|
| 38 | Downloading |
|---|
| 39 | =========== |
|---|
| 40 | |
|---|
| 41 | At startup, PMON looks for a <space> to be pressed. If it is pressed, |
|---|
| 42 | then a PMON prompt is displayed. Otherwise, PMON automatically jumps |
|---|
| 43 | to the code at 0xBFC4_0000. This code may be a boot manager or |
|---|
| 44 | simply a collection of noop's that fall into the code at |
|---|
| 45 | 0xBFC5_0000. If the code at 0xBFC4_0000 is a boot manager, then it |
|---|
| 46 | can determine which program image to load. This layout allows for the |
|---|
| 47 | possible compression of program images. Given that there is much |
|---|
| 48 | more RAM than EEPROM, compression could be desirable for certain |
|---|
| 49 | applications. |
|---|
| 50 | |
|---|
| 51 | Questions |
|---|
| 52 | ========= |
|---|
| 53 | |
|---|
| 54 | + XXX |
|---|
| 55 | |
|---|
| 56 | Status |
|---|
| 57 | ====== |
|---|
| 58 | |
|---|
| 59 | + untested |
|---|
| 60 | |
|---|
| 61 | + no mkeeprom script |
|---|
| 62 | |
|---|
| 63 | + start code must copy from EEPROM to RAM and then run. |
|---|
| 64 | |
|---|
| 65 | + XXX |
|---|
![[RTEMS Logo]](/images/logo.png){kind=logo}
