aboutsummaryrefslogtreecommitdiff
path: root/bootloaders/stk500v2/Makefile
diff options
context:
space:
mode:
authorWestfW <westfw@gmail.com>2011-06-10 17:47:47 -0700
committerDavid A. Mellis <d.mellis@arduino.cc>2011-10-10 12:11:15 -0400
commitb4952051f6eb9a47c9bd08918a093cd070637704 (patch)
tree645db8512dc70c6b7e93b59693bf6fc9786acb96 /bootloaders/stk500v2/Makefile
parent64cbe56ab5028dfc6d61767f40f060471ab468df (diff)
Add a version number to the optiboot source and binary.
http://code.google.com/p/arduino/issues/detail?id=554 end of flash memory where they can be read (at least in theory) by device programmers, hex-file examination, or application programs. This is done by putting the version number in a separate section (".version"), and using linker/objcopy magic to locate that section as appropriate for the target chip. (See http://lists.gnu.org/archive/html/avr-gcc-list/2011-02/msg00016.html for some discussion on the details.) Start the version at 4.1 (the last "packaged" version of optiboot was called version 3, so the "top of source" would be 4.0, and adding the version number makes 4.1) Refactor LDSECTION in the Makefile to LDSECTIONS so that multiple section start addresses can be defined. Change the _isp makefile definitions to make the bootloader section readable (but not writable) by the application section. (This would need to be done elsewhere as well to handle all bootloader programming techniques. Notably Arduino's boards.txt Note that this change does not change the "code" portion of optiboot at all. The only diffs in the .hex files are the added version word at the end of flash memory. (cherry picked from commit 00706284dec3171646419839bd4a9e3f1c2d7088)
Diffstat (limited to 'bootloaders/stk500v2/Makefile')
0 files changed, 0 insertions, 0 deletions