[avrdude-dev] [bug #46759] avrdude 6.1 -> 6.2 regression: lock byte verification error

[Milan Kupcevic]

Follow-up Comment #1, bug #46759 (project avrdude):

This bug is a result of commit r1336
<http://svn.savannah.nongnu.org/viewvc?view=rev&root=avrdude&revision=1336>,
which is a move in the right direction as far as fixing of inconsistent
behavior described in bug#21954 <https://savannah.nongnu.org/bugs/?21954>
goes. 

But now we should make the behavior of all other programmers consistent. 

Per Atmel recommendation unused bits should be set to 1. They are supposed to
read back out of hardware as 1. Therefore the user writing the lock bits
should just follow the recommendation and get the correct outcome.

*Currently*:

@$> avrdude -patmega328p -cstk500v2 -Pusb -e -Ulock:w:0xff:m 

*yields*:

 avrdude: verifying ...
 avrdude: 1 bytes of lock verified


*But*:

@$> avrdude -patmega328p -cusbtiny -Pusb -e -Ulock:w:0xff:m

*yields*:

 avrdude: verifying ...
 avrdude: verification error, first mismatch at byte 0x0000
          0x3f != 0xff
 avrdude: verification error; content mismatch

 avrdude: safemode: Fuses OK (E:FD, H:DE, L:FF)

 avrdude done. Thank you. 


Therefore the lock definition in avrdude.conf should no longer mask reading of
unused lock bits the same way as it has already been done for efuse bits with
commit r1335
<http://svn.savannah.nongnu.org/viewvc?view=rev&root=avrdude&revision=1335>
per discussion of bug#22248 <https://savannah.nongnu.org/bugs/?22248>.


    _______________________________________________________

Reply to this item at:

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

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