[avr-chat] Avrdude 6.01 does not like zero-length eeprom hex files

[Bob von Knobloch]

Hi,

I use a bash script to program my avrs. It simply gets parameters 
(fuses, bitclock etc.) by 'awk'ing some #defines in my source. This 
allows me to keep this stuff with the source code.

Since updating to avrdude 6.01, I get errors.

Tracking this down it seems that avrdude dores not like it if I try to 
program an eeprom intel hex file with zero information in it (generated 
from a source where no eeprom data is defined).

The old version used to do this OK.

Command line (beware of email mangling CRLFs):
avrdude -p atmega1284p -c stk500v2 -P /dev/ttyS4 -B 1  -U 
eeprom:w:main_eeprom.hex

Contents of main_eeprom.hex:
:00000001FF

Returns:
avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.01s

avrdude: Device signature = 0x1e9705
avrdude: reading input file "main_eeprom.hex"
avrdude: input file main_eeprom.hex auto detected as Intel Hex
avrdude: writing eeprom (0 bytes):

Writing | ################################################## | 100% 0.00s

avrdude: 0 bytes of eeprom written
avrdude: verifying eeprom memory against main_eeprom.hex:
avrdude: load data eeprom data from input file main_eeprom.hex:
avrdude: input file main_eeprom.hex auto detected as Intel Hex
avrdude: input file main_eeprom.hex contains 0 bytes
avrdude: reading on-chip eeprom data:

Reading |                                                    | 0% 
0.00sFloating point exception

It seems to be the reading of the eeprom that fails.
If an eeprom file with data in it is used, the problem disappears.

Cheers,

Bob von Knobloch
--
The Sun is out, the sky is blue, it's time to drive the MR2.