Consider making optboot boot region read-accessible to sketchs in the non-boot sections.

GoogleCodeExporter commented 8 years ago

What steps will reproduce the problem?
1. normal build and install
2.
3.

What is the expected output? What do you see instead?
It would be nice for troubleshooting purposes if the optiboot version number 
were available to be read by sketches.  Or at least the code area so that it 
could be checksummed and compared against known releases.
This is not possible with the current 0F memory protection fuse setting, but 
would be possible if the memmory protection were set to 2F, which would still 
prevent writing  to the boot section, but WOULD allow reading it.

What version of the product are you using? On what operating system?
Not version specific.
Please provide any additional information below.
How to get the version number into a known place is trickier than I thought it 
would be :-(

Original issue reported on code.google.com by wes...@gmail.com on 25 Feb 2011 at 10:00

GoogleCodeExporter commented 8 years ago

Original comment by wes...@gmail.com on 29 Oct 2011 at 5:27

GoogleCodeExporter commented 8 years ago

Fixed as part of the great optiboot/Arduino sync-up
http://code.google.com/p/optiboot/source/detail?r=8559b64fd093d3976cae58778a1540
256cde5c8e

Original comment by wes...@gmail.com on 30 Oct 2011 at 8:19

Changed state: Fixed

gusarov / optiboot

Consider making optboot boot region read-accessible to sketchs in the non-boot sections. #34