[avrdude-dev] [bug #37801] AVRDUDE incorrectly programs sparse images >64KB

[Joerg Wunsch]

Update of bug #37801 (project avrdude):

                  Status:                    None => Works For Me           
             Assigned to:                    None => joerg_wunsch           

    _______________________________________________________

Follow-up Comment #3:

Thanks for supplying the files.

I tried all combinations of the following:

. version 5.11.1 (latest release), with your hex file
. SVN version (r1125), with your hex file
. SVN version (r1125), with your ELF file (SVN version can
  program ELF files directly, including sparse files)

with

. STK600
. STK500 (using V2 firmware)
. AVRISPmkII

All work as intended, i. e. the sparse files are being programmed
correctly.  Consequently, the bug must be in the Arduino programmer/
bootloader, somehow.  Presumably, it confuses the way the "load
address" command is implemented, in particular the use of bit 31 as an
indication to use extended (24-bit) addressing.

However, the log file you submitted does not match the ELF/hex files
you uploaded later.  The load address commands in your log are:

[06] . [80] . [00] . [00] . [00]
[06] . [80] . [00] . [80] . [00]
[06] . [80] . [00] . [f6] . [80]

If I flash your hex file, I get:

[06] . [80] . [00] . [00] . [00]
[06] . [80] . [00] . [80] . [00]
[06] . [80] . [01] . [00] . [00]
[06] . [80] . [01] H [48] . [00]

Note that the addresses in the "load address" command are 16-bit word
addresses (when operating on flash), so the respective byte address
blocks are 0, 0x10000, 0x1ed00 for your log file, and 0, 0x10000,
0x20000, 0x29000 for your hex file.


    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?37801>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/