1 | 2000-10-12 John S Gwynne <jgwynne@mrcday.com> |
---|
2 | |
---|
3 | * start/start.c: Modified to support generation of ram_init. |
---|
4 | * start/ram_init.ld, BSP/start/ram_init.sed: New files. |
---|
5 | These changes enable RTEMS to automatically generate |
---|
6 | the ram_init file used by gdb with the BDM patches. The 332 has |
---|
7 | on-board chip select lines (for RAM and FLASH) that must be |
---|
8 | configured before use of these peripherals. These patches parse |
---|
9 | data from start.c where the chip select lines are configured in |
---|
10 | the runtime executable and automatically generates the gdb |
---|
11 | initialization file using the same settings. A great time saver. |
---|
12 | A similar file, ram_init_FW (flash writable), is also generated |
---|
13 | that the flash programming tool uses. |
---|
14 | * start/Makefile.am: Modified to support above. |
---|
15 | * CPU/sim.h: Modified to support above. |
---|
16 | * startup/except_vect_332_ROM.S: Moved to start so it would not |
---|
17 | be included in libbsp.a. Moving it to start ensures it is |
---|
18 | available as a single object file. |
---|
19 | * start/except_vect_332_ROM.S: Moved from startup. |
---|
20 | * startup/linkcmds, startup/linkcmds_ROM: Fixes to the memory map |
---|
21 | shown in the comments. |
---|
22 | |
---|
23 | 2000-09-29 Charles-Antoine Gauthier <charles.gauthier@nrc.ca> |
---|
24 | |
---|
25 | * startup/linkcmds: Added lines so DWARF debug information |
---|
26 | would be available. Otherwise gdb complains that the offsets |
---|
27 | for the debug info are incorrect and doesn't load the files. |
---|
28 | |
---|
29 | 2000-09-04 Ralf Corsepius <corsepiu@faw.uni-ulm.de> |
---|
30 | |
---|
31 | * clock/Makefile.am, console/Makefile.am, spurious/Makefile.am, |
---|
32 | start/Makefile.am, startup/Makefile.am, timer/Makefile.am, |
---|
33 | wrapup/Makefile.am: Include compile.am |
---|
34 | |
---|
35 | 2000-08-10 Joel Sherrill <joel@OARcorp.com> |
---|
36 | |
---|
37 | * ChangeLog: New file. |
---|