Re: [avrdude-dev] [bug #31699] ihex : unhandled ext. linear address records and unoptimized empty (0xff) space

[David A. Lyons]

Within the last day, I had a similar experience to yours.  I'm using avrdude 
5.8.  I haven't filed a bug report yet.

I was unable to write past the first 64K bytes (of an AT90USB1287) when using 
an IHEX file.  However, switching to an SREC file made it work (though it took 
much longer than necessary, as you say).

--Dave


On Nov 18, 2010, at 10:14 AM, Georg Garrecht wrote:

> 
> URL:
> <http://savannah.nongnu.org/bugs/?31699>
> 
>                Summary: ihex : unhandled ext. linear address records and
> unoptimized empty (0xff) space
>                Project: AVR Downloader/UploaDEr
>           Submitted by: gg2410
>           Submitted on: Thu 18 Nov 2010 06:14:42 PM GMT
>               Category: None
>               Severity: 3 - Normal
>               Priority: 5 - Normal
>             Item Group: None
>                 Status: None
>                Privacy: Public
>            Assigned to: None
>        Originator Name: gg2410
>       Originator Email: 
>            Open/Closed: Open
>        Discussion Lock: Any
> 
>   _______________________________________________________
> 
> Details:
> 
> I found a very strange problem, which makes it nearly impossible to write
> e.g. a bootloader into an ATMEGA in a seriously short time.
> 
> For specialists, this should be easy to fix.
> 
> 
> Version : 5.10
> 
> Following commandline:
> 
> avrdude -p m128 -c ponyser -P com1: -e -U flash:w:test55.hex
> 
> 
> used with following sole hexfile content:
> 
> :20F0000011241FBECFEFD0E1DEBFCDBF11E0A0E0B1E0E6E3F6EF01E00BBF02C007900D92F3
> :00000001FF
> 
> 
> Problem #1:
> ===========
> Although the flash memory is cleared, the software always tries to write full
> 61472 bytes into the Atmega. Most of this writing is unnecessary as the bytes
> are all 0xFF after a flash erase.
> This way, it takes minutes instead of 2-3 seconds to write a small portion of
> code into the upper part of the flash.
> 
> It seems that it doesn't skip writing blocks of 0xFF starting at beginning of
> the Flash memory up to the address where it is needed to write the first byte
> != 0.
> 
> even worse: Problem #2
> ======================
> adding
> :020000040001F9  
> as the first line of the hex file should relocate the writing process to
> Flash address 0x1F000.
> 
> Instead, the software still tries to write only 61472 bytes.
> The dump which I get when using cmd-line option "-n" shows this clearly.
> This way, it is impossible to write a bootloader into the upper few KB's of
> the 128K Flash. 
> 
> Is the AVRDUDE Software perhaps not able to write more than 64KB ?
> 
> Please look into this, as it is clearly not only of importance for me.
> 
> Many thanxxxxxxxxxx
> 
> Georg
> 
> 
> 
> 
> 
> 
>   _______________________________________________________
> 
> Reply to this item at:
> 
> <http://savannah.nongnu.org/bugs/?31699>
> 
> _______________________________________________
> Message sent via/by Savannah
> http://savannah.nongnu.org/
> 
> 
> _______________________________________________
> avrdude-dev mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/avrdude-dev