I understand that 0xff is not a useful value, it was just to dramatize
the error. So even if the write failed, the read should pass, but
neither did.
Yes, I will try the svn version, thanks.
On 06/05/2012 03:30 PM, Joerg Wunsch wrote:
As David L. Martin wrote:
0.00savrdude: stk600_xprog_write_byte(): unknown memory "lock"
***failed;
That should be fixed in the SVN version. Give it a try if you can.
Btw., trying to program the lock byte to 0xff is not useful.
Returning lock bits to `1' state can only be reached by means of a
chip erase.
_______________________________________________
avrdude-dev mailing list
avrdude-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/avrdude-dev
