[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Unexpected message : "avrdude: bad response to write memory command: 0xa
From: |
Doom |
Subject: |
Unexpected message : "avrdude: bad response to write memory command: 0xa0" |
Date: |
Mon, 6 Dec 2021 12:21:07 +0100 |
Hello,
When I write lock bits I have this message :
"avrdude: bad response to write memory command: 0xa0"
It seems to work, but I want to know if it is normal or if I should search
something wrong somewhere ?
mcu is avr128db64
and programmer is atmelice_updi
Thanks for your answer.
Doom.
doom@doom: avrdude -c atmelice_updi -p avr128db64 -e -F -U
lock:w:0x5c,0xc5,0xc5,0x5c:m
avrdude: AVR device initialized and ready to accept instructions
Reading | | 0%
0.00savrdude: Device is locked! Chip erase required to unlock.
avr_read(): error reading address 0x0000
read operation failed for memory "signature"
avrdude: error reading signature data for part "AVR128DB64", rc=-68
avrdude: Received FamilyID: "AVR "
avrdude: Expected FamilyID: ""
avrdude: erasing chip
Reading | ################################################## | 100% 0.00s
avrdude: Device signature = 0x1e970b (probably avr128db64)
avrdude: reading input file "0x5c,0xc5,0xc5,0x5c"
avrdude: writing lock (4 bytes):
Writing | | 0%
0.00savrdude: bad response to write memory command: 0xa0
Writing | ################################################## | 100% 0.06s
avrdude: 4 bytes of lock written
avrdude: verifying lock memory against 0x5c,0xc5,0xc5,0x5c:
avrdude: load data lock data from input file 0x5c,0xc5,0xc5,0x5c:
avrdude: input file 0x5c contains 4 bytes
avrdude: reading on-chip lock data:
Reading | ################################################## | 100% 0.01s
avrdude: verifying ...
avrdude: 4 bytes of lock verified
avrdude: safemode: Fuses OK (E:FF, H:FF, L:FF)
avrdude done. Thank you.
doom@doom: avrdude -c atmelice_updi -p avr128db64 -U lock:r:-:h
avrdude: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.01s
avrdude: Device signature = 0x1e970b (probably avr128db64)
avrdude: reading lock memory:
Reading | ################################################## | 100% 0.01s
avrdude: writing output file "<stdout>"
0x5c,0xc5,0xc5,0x5c
avrdude: safemode: Fuses OK (E:FF, H:FF, L:FF)
avrdude done. Thank you.
doom@doom: avrdude -c atmelice_updi -p avr128db64 -U
lock:w:0xd4,0x4d,0x4d,0xd4:m
avrdude: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.01s
avrdude: Device signature = 0x1e970b (probably avr128db64)
avrdude: reading input file "0xd4,0x4d,0x4d,0xd4"
avrdude: writing lock (4 bytes):
Writing | | 0%
0.00savrdude: bad response to write memory command: 0xa0
Writing | ################################################## | 100% 0.06s
avrdude: 4 bytes of lock written
avrdude: verifying lock memory against 0xd4,0x4d,0x4d,0xd4:
avrdude: load data lock data from input file 0xd4,0x4d,0x4d,0xd4:
avrdude: input file 0xd4 contains 4 bytes
avrdude: reading on-chip lock data:
Reading | ################################################## | 100% 0.01s
avrdude: verifying ...
avrdude: 4 bytes of lock verified
avrdude: safemode: Fuses OK (E:FF, H:FF, L:FF)
avrdude done. Thank you.
doom@doom: avrdude -c atmelice_updi -p avr128db64 -U lock:r:-:h
avrdude: AVR device initialized and ready to accept instructions
Reading | | 0%
0.00savrdude: Device is locked! Chip erase required to unlock.
avr_read(): error reading address 0x0000
read operation failed for memory "signature"
avrdude: error reading signature data for part "AVR128DB64", rc=-68
avrdude: Received FamilyID: "AVR "
avrdude: Expected FamilyID: ""
Double check chip, or use -F to override this check.
avrdude done. Thank you.
ᐧ
- Unexpected message : "avrdude: bad response to write memory command: 0xa0",
Doom <=