[avrdude-dev] Wrong Signature? No problem

[Tom Jones]

I recently made a mistake and asked avrdude to program the wrong target 
device. That was no problem for avrdude, it went right about its 
business. My target was a AT90S8515 but the program was written for a 
AT90S2313. The 2313 has a signature of 1e9101. Avrdude reported the 
8515’s signature of 1e9301 and kept on working.

That seems like a bug to me. But, since I don’t know everything perhaps 
it’s a feature that I just don’t appreciate.

Please enlighten me if you can, and thanks,

Tom Jones

> "make.exe" program
avrdude -p at90s2313 -P com1 -c stk500v2 -U flash:w:AutoLights.hex

avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.02s

avrdude: Device signature = 0x1e9301
avrdude: NOTE: FLASH memory has been specified, an erase cycle will be 
performed
To disable this feature, specify the -D option.
avrdude: erasing chip
avrdude: reading input file "AutoLights.hex"
avrdude: input file AutoLights.hex auto detected as Intel Hex
avrdude: writing flash (358 bytes):

Writing | ################################################## | 100% 1.00s

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

Reading | ################################################## | 100% 0.13s

avrdude: verifying ...
avrdude: 358 bytes of flash verified

avrdude done. Thank you.


> Process Exit Code: 0
> Time Taken: 00:02