source: rtems/c/src/lib/libbsp/mips/genmongoosev/README @ 7de58239

4.104.114.84.95
Last change on this file since 7de58239 was 7de58239, checked in by Joel Sherrill <joel.sherrill@…>, on 02/01/02 at 16:45:18

2001-02-01 Greg Menke <gregory.menke@…>

  • Update of BSP to address problems restarting, provide more information during boot, and better handle ROM vs RAM images.
  • README, include/bsp.h, start/regs.S, start/start.S, startup/bspstart.c, startup/linkcmds, timer/timer.c: Updated
  • Property mode set to 100644
File size: 3.1 KB
Line 
1#
2#  $Id$
3#
4
5BSP supporting the on-CPU capabilities of the Synova Mongoose-V.
6This BSP assumes that basic HW initialization is performed by
7PMON.
8
9Address Map
10===========
11This is the generic address map of the Mongoose-V prototyping board
12this BSP was tested on.
13
140x8000_0000 - 0x8FFF_FFFF   - RAM (KSEG0 cached)
150xA000_0000 - 0xAFFF_FFFF   - RAM (KSEG1, same memory uncached)
160xBFC0_0000 - 0xBFFF_FFFF   - EEPROM
170xFFFE_xxxx                 - on-CPU peripherals
18
19This is the hardware address map of the board used as it was
20actually populated.
21
220x8000_0000 - 0x83FF_FFFF   - 32 MB RAM (KSEG0 cached)
230xA000_0000 - 0xA3FF_FFFF   - 32 MB RAM (KSEG1, same memory uncached)
240xBFC0_0000 - 0xBFDF_FFFF   - 2 MB EEPROM
250xFFFE_xxxx                 - on-CPU peripherals
26
27This is the organization of the EEPROM when fully populated.  Since
28the board used to develop this BSP only had the first bank of EEPROM
29populated, only the first program image area was used.
30
310xBFC0_0000 - 0xBFC3_FFFF   - PMON
320xBFC4_0000 - 0xBFC4_FFFF   - reserved for boot loader
330xBFC5_0000 - 0xBFDF_FFFF   - reserved for program 1 image
340xBFE0_0000 - 0xBFFF_FFFF   - reserved for program 2 image
35
36The Mongoose-V on this board is at 12 Mhz.
37
38Downloading
39===========
40
41On the breadboard, a locally hacked PMON waits for a space to be pressed
42while the board is reset/powered up.  If found, the PMON console is
43entered, else PMON jumps to the EEPROM address above, presuming a user
44program is located there.
45
46The default output of an RTEMS link is an image linked to run from
4780020000, but has had its LMA shifted up to BFC40000.  It is suitable
48for copying to S3 records or can be burned to ROMs in whatever manner
49the user desires.
50
51Operation
52=========
53
54A small relocator is supplied in the bsp startup code which copies the
55image down to RAM for execution before doing any other initialization.
56This locator code is location independent, and will do nothing if the
57image is already located at its run location.  The LMA and VMA are both
58controlled via the bsp's link script.  The above behavior is produced by
59using the default script.  If this is not desirable, something like the
60following may be added to the user's RTEMS link statement to override
61the default linkcmds with a user-supplied version;
62
63-qnolinkcmds -Wl,-T -Wl,mips-rtems-linkcmds-eprom
64
65this causes the file ./mips-rtems-linkcmds-eprom to override the default
66linkcmds.
67
68Before relocating the RTEMS image, the bsp startup routine attempts to
69configure the processor into a rational state.  During this process,
70status characters are emitted at 19200N81 baud on UART port 0.
71
72
73Questions
74=========
75
76Why can I send characters slowly to a Mongoose V, but get framing errors
77when sending them fast?
78
79- The MongooseV chip seems to <require> that all incoming data have 2
80  stop bits.  When typing on a serial terminal, this is not an issue
81  because the idle state of an RS232 line looks just like a stop bit-
82  but when streaming in data, such pacing is required.  The manual does
83  not indicate anything along these lines, instead, we suspect a
84  somewhat faulty UART design.
85
86
87Status
88======
89
Note: See TracBrowser for help on using the repository browser.