AVR Downloader/UploaDEr - Bugs: bug #9882, faulty flash writes on ATmega32...
You are not allowed to post comments on this tracker with your current authentication level.
bug #9882: faulty flash writes on ATmega32 via avr910
Submitter: | None | ||
Submitted: | Wed 04 Aug 2004 02:44:43 PM UTC | ||
Category: | None | Severity: | 3 - Normal |
Priority: | 5 - Normal | Item Group: | None |
Status: | Fixed | Privacy: | Public |
Assigned to: | bdean | Originator Name: | none given |
Originator Email: | -email is unavailable- | Open/Closed: | Closed |
Release: | None | Programmer hardware: | |
Device type: |
Sun 18 Sep 2005 12:36:58 AM UTC, comment #2: |
Brian Dean <bdean> |
Tue 10 Aug 2004 05:30:37 PM UTC, comment #1: Okay, the problems I experienced on non-interactive downloads were due to failure in avr910_paged_write_flash() to re-set the address correctly after page writes. That function has a several other problems:
|
Anonymous |
Wed 04 Aug 2004 02:44:43 PM UTC, original submission:
I'm getting very bizarre faults on writing flash, looks like either buggy avr910 driver code or timing problems - see the attached file for a detailed description. Hardware works fine with AVRprog.exe, host and target work fine with avrdude and an avrisp programmer, so the bug must be specific to avrdude's avr910 code. |
Anonymous |
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 6 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2005-09-18 | bdean | Status | None | Fixed | |
Assigned to | None | bdean | |||
Originator Name | none given | ||||
Originator Email | none given | ||||
Open/Closed | Open | Closed | |||
2004-08-04 | None | Attached File | - | Added problem.txt, #1563 |
Powered by Savane 3.13-0329.
Corresponding source code
I think this bug is fixed by patch #3277 which was just committed.