| Commit message (Collapse) | Author | Files | Lines |
|---|
|
* start/start.c: Modified to support generation of ram_init.
* start/ram_init.ld, BSP/start/ram_init.sed: New files.
These changes enable RTEMS to automatically generate
the ram_init file used by gdb with the BDM patches. The 332 has
on-board chip select lines (for RAM and FLASH) that must be
configured before use of these peripherals. These patches parse
data from start.c where the chip select lines are configured in
the runtime executable and automatically generates the gdb
initialization file using the same settings. A great time saver.
A similar file, ram_init_FW (flash writable), is also generated
that the flash programming tool uses.
* start/Makefile.am: Modified to support above.
* CPU/sim.h: Modified to support above.
* startup/except_vect_332_ROM.S: Moved to start so it would not
be included in libbsp.a. Moving it to start ensures it is
available as a single object file.
* start/except_vect_332_ROM.S: Moved from startup.
* startup/linkcmds, startup/linkcmds_ROM: Fixes to the memory map
shown in the comments.
|
|
|
|
problems that prevented the 19990302 snapshot from running on
the efi332.
I'm happy to report that rtems-19990302 is running on the efi332
board. I have enclosed a few minor patches below to the efi332 bsp. All
patches are within that library but one. make/custom/efi332.cfg has a
patch to select the right CPU_CFLAGS (at one time -m68332 was a
problem... -mcpu32 or -m68332 work fine now).
|
|
> RTEMS is under CVS control and has been since rtems 3.1.16 which was
> around May 1995. So I just to add the $Id$. If you notice other files
> with missing $Id$'s let me know. I try to keep w\up with it.
Now that you have asked -- I'll attach a list of files lacking an RCS-Id to
this mail. This list has been generated by a little sh-script I'll also
enclose.
|
|
|
|
commit them.
|
