Wed 15 Oct 2014 11:30:10 AM UTC, original submission:
Hi,
I would like to report a little bug with avrdude 6.1.
when I write lock byte:
avrdude -p c128 -c usbasp -U lock:w:0xCC
it works fine
but when I read it or verify it, I get:
avrdude -p c128 -c usbasp -U lock:w:0xCC:m
avrdude: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.03s
avrdude: Device signature = 0x1e9781
avrdude: reading input file "0xCC"
avrdude: writing lock (1 bytes):
Writing | | 0% 0.00s ***failed;
Writing | ################################################## | 100% 0.06s
avrdude: 1 bytes of lock written
avrdude: verifying lock memory against 0xCC:
avrdude: load data lock data from input file 0xCC:
avrdude: input file 0xCC contains 1 bytes
avrdude: reading on-chip lock data:
Reading | ################################################## | 100% 0.01s
avrdude: verifying ...
avrdude: verification error, first mismatch at byte 0x0000
0x0c != 0xcc
avrdude: verification error; content mismatch
avrdude: safemode: Fuses OK (E:FF, H:D2, L:FF)
avrdude done. Thank you.
So lock fuse is correclty written but avrdude can read lock fuse correctly for part: c128
Best regards,
|