[avrdude-dev] [bug #44717] avrdude creates empty flash dump

[Joerg Wunsch]

Update of bug #44717 (project avrdude):

                  Status:                    None => Invalid                
             Assigned to:                    None => joerg_wunsch           

    _______________________________________________________

Follow-up Comment #1:

It's not a bug, it's a feature: your flash is empty (erased), 
thus the resulting file is empty, too.  You have chosen raw 
file output, so you get a file with length 0.  If you had 
chosen e.g. Intel hex output, you'd at least get the terminal 
record in the file – as an indication that everything worked 
well, but there simple are no data to display.

Without that feature, readout of a partially filled flash 
would always get a bunch of 0xFFFF values at the end of the 
file.  The feature is only applied to flash, not to EEPROM, 
that's why your EEPROM readout indeed yields a file full of 
0xFF.  Yes, that's not really quite consistent, but has been 
that way since the early days of AVRDUDE.

    _______________________________________________________

Reply to this item at:

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

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