AVR Downloader/UploaDEr - Bugs: bug #22883, Chip Erase performed even with...
You are not allowed to post comments on this tracker with your current authentication level.
bug #22883: Chip Erase performed even with no-write flag (-n)
Submitter: | None | ||
Submitted: | Wed 09 Apr 2008 05:31:37 PM UTC | ||
Category: | None | Severity: | 3 - Normal |
Priority: | 5 - Normal | Item Group: | None |
Status: | Fixed | Privacy: | Public |
Assigned to: | joerg_wunsch | Originator Name: | Thomas Holland |
Originator Email: | -email is unavailable- | Open/Closed: | Closed |
Release: | None | Programmer hardware: | |
Device type: |
Tue 04 Nov 2008 12:13:38 PM UTC, comment #5: |
Joerg Wunsch <joerg_wunsch> |
Wed 09 Apr 2008 11:07:14 PM UTC, comment #4: OK, give me a few days to finish the avrdude support in my Eclipse plugin and then I will take care of the avrdude simulation mode. |
Thomas Holland <innot> |
Wed 09 Apr 2008 09:02:42 PM UTC, comment #3: Well, sure, it's possible that the fuse values do change even
|
Joerg Wunsch <joerg_wunsch> |
Wed 09 Apr 2008 08:44:25 PM UTC, comment #2: I am not sure.
|
Thomas Holland <innot> |
Wed 09 Apr 2008 07:03:25 PM UTC, comment #1: I guess -n should also diable safemode, as safemode would
|
Joerg Wunsch <joerg_wunsch> |
Wed 09 Apr 2008 05:31:37 PM UTC, original submission:
While the -n flag prevents avrdude from writing anything to the flash memory, it will nevertheless happily do a chip erase.
|
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 3 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2008-11-04 | joerg_wunsch | Status | None | Fixed | |
Assigned to | None | joerg_wunsch | |||
Open/Closed | Open | Closed |
Powered by Savane 3.13-02a9.
Corresponding source code
I decided to ignore the safemode issue, and applied a fix
similar to the originally submitted one, except it also
prints a message that the chip is not being erased.