Several uncommon platforms don't include the .version section

GoogleCodeExporter commented 8 years ago

For the "Arduino-supported" chips (m8, m168, m328), the optiboot version is 
loaded into the last two bytes of program memory via the .version section.
Several other platforms (MEGA, Sanguino, m1284) do not include the definition 
of the .version section...

Original issue reported on code.google.com by wes...@gmail.com on 29 Jan 2012 at 11:43

GoogleCodeExporter commented 8 years ago

Fixed via Makefile changes in 
http://code.google.com/p/optiboot/source/detail?r=cc5e4843feec1476610c5978b71b5e
1023104d8d

Original comment by wes...@gmail.com on 4 Apr 2012 at 2:15

Changed state: Fixed

GoogleCodeExporter commented 8 years ago

It looks like a consequence of not having the .version section start address 
specified is that version number gets loaded at a default flash location of 
0x00000 instead (rather than simply being omitted.)  Under normal 
circumstances, this doesn't cause problems because those locations are erased 
anyway as part of the bootloader burn, and erased again when the bootloader 
loads a sketch.  But if you are doing something like combining .hex files with 
a sketch to create a single burnable .hex, there will be conflicts when both 
the bootloader and the sketch have contents for location 0.

Original comment by wes...@gmail.com on 29 Apr 2012 at 6:58

rgoel / optiboot

Several uncommon platforms don't include the .version section #56