[avrdude-dev] [bug #37441] lockbits in ATxmega + avrdude = problem

[Joerg Wunsch]

Update of bug #37441 (project avrdude):

                  Status:               Need Info => Works For Me           
             Assigned to:                    None => joerg_wunsch           
             Open/Closed:                    Open => Closed                 

    _______________________________________________________

Follow-up Comment #3:

You are using a fairly outdated version of AVRDUDE.

In recent versions (6.x), I don't see a problem with the way it is
now, i.e. using "lock" for the Xmega lock bits:


$ avrdude -c atmelice_pdi -p atxmega16d4 -qq -U lock:r:-:h -U eeprom:r:-:h
0xff
0xff,0xff,0xff,0xff,0xff,[...]
$ avrdude -c atmelice_pdi -p atxmega16d4 -qq -U lock:w:0:m
$ avrdude -c atmelice_pdi -p atxmega16d4 -qq -U lock:r:-:h -U eeprom:r:-:h
0x0
0x0,0x0,0x0,0x0,0x0,0x0,[...]
$ avrdude -c atmelice_pdi -p atxmega16d4 -qq -e -U lock:r:-:h
0xff


There are certain points in the code where m->desc is checked against
just "lock" so "lockbits" would fail to be recognized (i.e., just the
opposite from what this bug report is telling).  In all situations
where this might be applicable, I changed the comparison to only check
for the first four characters being equal to "lock", so both, "lock"
and "lockbits" will do.


    _______________________________________________________

Reply to this item at:

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

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