Go Down

Topic: bug in optiboot bootloader (Read 3 times) previous topic - next topic

westfw

Huh.  How do you even GET trailing 0xFFs in the .data segment?
I'm always getting .data from the Arduino libraries beyond everything I put in the user area of the sketch.

Libraries?

008001be d _ZL8mystdout
00800200 D trailff_RAM               ;; structure with trailing FFs
00800280 V _ZTV14HardwareSerial      ;; structure from libraries.
00800290 B __bss_start
00800290 D __data_end

pito

#31
Aug 03, 2013, 12:18 pm Last Edit: Aug 03, 2013, 03:05 pm by pito Reason: 1
Quote
the new avrdude only burns and verifies the actual pages with real data in them.
The burn/verify time for optiboot using USBASP is less than 1 second now.

Where we can get that latest avrdude?

Here for example (6.0rc2):

http://www.mikrocontroller.net/topic/296379#3166155

bperrybap


Where we can get that latest avrdude?

You will have to build it yourself.
From the repository:
http://savannah.nongnu.org/svn/?group=avrdude
There are also some tar'ed up source versions available:
http://download.savannah.gnu.org/releases/avrdude/

Just get and build whatever version you want for your OS platform.
note: there are quite a few tools that must be in place to be
able to do native s/w development and for those still using Windows,
it isn't quite as easy to get them in place as those running
linux OS's.

--- bill

g_u_e_s_t


If it is ONLY the block at the very end of the sketch, that's a much less serious problem.  IMO.



this definitely means it will effect fewer people, but also means it will be far more confusing when it does happen.  the partial page trailing FF's seems like an easy fix anyways.  not sure anything can be done on the optiboot side for full pages at the end of a .hex file.

bperrybap



If it is ONLY the block at the very end of the sketch, that's a much less serious problem.  IMO.



this definitely means it will effect fewer people, but also means it will be far more confusing when it does happen.  the partial page trailing FF's seems like an easy fix anyways.  not sure anything can be done on the optiboot side for full pages at the end of a .hex file.


Couldn't you put a dummy section at the end of the linked image to ensure that this never happened?
Yeah, it would require a tweak to the Arduino team controlled code but it's a one time thing.

Go Up