bugAVR Downloader/UploaDEr - Bugs: bug #37441, lockbits in ATxmega + avrdude =...

 
 

You are not allowed to post comments on this tracker with your current authentication level.

bug #37441: lockbits in ATxmega + avrdude = problem

Submitter:  None
Submitted:  Tue 25 Sep 2012 12:48:36 PM UTC
   
 
Category:  None Severity:  3 - Normal
Priority:  5 - Normal Item Group:  None
Status:  Works For Me Privacy:  Public
Assigned to:  joerg_wunsch Originator Name:  mn_post@mail.ru
Originator Email:  -email is unavailable- Open/Closed:  Closed
Release:  None Programmer hardware: 
Device type: 

Wed 15 Oct 2014 08:01:26 PM UTC, 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.

Joerg Wunsch <joerg_wunsch>
Group administrator
Wed 15 Oct 2014 06:34:05 PM UTC, comment #2: 

"lock" in the configuration file is not recognized by avrdude.
If it is renamed to "lockbits" in the configuration file, reading and writing of lock byte works.

Command parameter should remain the same though.
For example "-Ulock:w:0x00:m"

Related to:
avrdude: Version 5.11.1, compiled on Oct 18 2011 at 21:41:15

MCU:
AtXMega256A3BU

nvd <nvd>
Tue 03 Sep 2013 12:10:59 PM UTC, comment #1: 

Well, we traditionally named the lock bits section "lock", not
only for Xmega devices but also for older AVRs.

What's your actual problem with that name?

Joerg Wunsch <joerg_wunsch>
Group administrator
Tue 25 Sep 2012 12:48:36 PM UTC, original submission:  

avrdude.conf consists non-valid memory sections names for MCU's ATxmega family. Memory section name (in avrdude.conf) "lock" - is wrong, "lockbits" - that's right.

Anonymous

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by nvd (Posted a comment)
  • -email is unavailable- added by joerg_wunsch (Posted a comment)
  • -email is unavailable- added by None (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

     

    Follow 4 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2014-10-15 joerg_wunsch StatusNeed Info Works For Me
        Assigned toNone joerg_wunsch
        Open/ClosedOpen Closed
    2013-09-03 joerg_wunsch StatusNone Need Info

    Back to the top

    Powered by Savane 3.13-d3ae.
    Corresponding source code