AVR 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: |
Joerg Wunsch <joerg_wunsch> |
Wed 15 Oct 2014 06:34:05 PM UTC, comment #2: "lock" in the configuration file is not recognized by avrdude.
|
nvd <nvd> |
Tue 03 Sep 2013 12:10:59 PM UTC, comment #1: Well, we traditionally named the lock bits section "lock", not
|
Joerg Wunsch <joerg_wunsch> |
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 |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
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 | Status | Need Info | Works For Me | |
Assigned to | None | joerg_wunsch | |||
Open/Closed | Open | Closed | |||
2013-09-03 | joerg_wunsch | Status | None | Need Info |
Powered by Savane 3.13-d3ae.
Corresponding source code
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:
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.