diff options
author | Joel Sherrill <joel.sherrill@OARcorp.com> | 2006-06-23 16:04:33 +0000 |
---|---|---|
committer | Joel Sherrill <joel.sherrill@OARcorp.com> | 2006-06-23 16:04:33 +0000 |
commit | 504c5ca0f2079fee64e27d5a08187c0bc9b77feb (patch) | |
tree | ac3b94dad516f8c05ce65bacf3f32ace247948d4 /c/src/lib/libbsp/m68k/gen68302 | |
parent | 2006-06-23 Ralf Corsépius <ralf.corsepius@rtems.org> (diff) | |
download | rtems-504c5ca0f2079fee64e27d5a08187c0bc9b77feb.tar.bz2 |
2006-06-23 Worth Burruss <worth@motioncontrol.org>
* Makefile.am, README, startup/init5235.c, startup/linkcmds,
startup/linkcmdsflash, startup/linkcmdsram: Modify to the mcf5235
eval boards to either load and run from ram using the dBug moniter as
the boot deviced (Board setup as shipped from the factory), or it
allows the user to Boot his code from flash he loads onto the eval
board. The code changes between the two are based on the selected
linker script using a variable in the script. The options to the
linker are used to override the default linker script and select
which options to configure at boot either from flash, or from ram:
-qnolinkcmds -T linkcmdsflash
If no options are given the standard linker sript assumes dBug was
used to set up the board and the user is going to load his program
to RAM.
Diffstat (limited to 'c/src/lib/libbsp/m68k/gen68302')
0 files changed, 0 insertions, 0 deletions