AVR Downloader/UploaDEr - Bugs: bug #42267, jtag3isp fails to read lock and...
You are not allowed to post comments on this tracker with your current authentication level.
bug #42267: jtag3isp fails to read lock and fuse bytes directly after changing lock byte
Submitter: | Matthijs Kooijman <matthijs> | ||
Submitted: | Fri 02 May 2014 09:43:30 AM UTC | ||
Category: | None | Severity: | 3 - Normal |
Priority: | 5 - Normal | Item Group: | None |
Status: | Fixed | Privacy: | Public |
Assigned to: | joerg_wunsch | Originator Name: | Matthijs Kooijman |
Open/Closed: | Closed | Release: | None |
Programmer hardware: | Device type: |
Jump to the original submission
Tue 29 Dec 2020 02:30:17 PM UTC, comment #10: |
Matthijs Kooijman <matthijs> |
Tue 28 Oct 2014 10:27:35 AM UTC, comment #9: After a bit more prodding, Atmel writes:
|
Matthijs Kooijman <matthijs> |
Tue 14 Oct 2014 06:14:03 PM UTC, comment #8: Hmm, I just noticed min_write_delay and max_write_delay in avrdude.conf. Aren't these related? I couldn't quite figure out what they're used for exactly, though. |
Matthijs Kooijman <matthijs> |
Tue 14 Oct 2014 05:48:33 PM UTC, comment #7: Just compiled svn trunk and did a quick test, seems that the delay
|
Matthijs Kooijman <matthijs> |
Tue 07 Oct 2014 03:31:38 PM UTC, comment #6: Getting more info sounds sane :-)
ticket for it.
|
Matthijs Kooijman <matthijs> |
Tue 07 Oct 2014 03:22:55 PM UTC, comment #5: I added 10 ms of delay before exiting from stk500isp_write_byte().
|
Joerg Wunsch <joerg_wunsch> |
Tue 07 Oct 2014 03:06:29 PM UTC, comment #4:
|
Joerg Wunsch <joerg_wunsch> |
Tue 07 Oct 2014 02:23:23 PM UTC, comment #3: Hmm, I see. However, even though this might be the firmware's fault, it seems unlikely that this will be fixed on that end (especially for the older hardware, I'd expect). Closing this as invalid and ignoring the problem doesn't seem like a great idea, since then things will still be broken for anyone using avrdude with this hardware. When manually running avrdude, the obvious workaround is of course to not verify the lockbits, but for example running inside the Arduino IDE, I don't think this easy (and probably not possible without also disabling verification of the full binary). Having to disable verification isn't so nice anyway...
|
Matthijs Kooijman <matthijs> |
Tue 07 Oct 2014 02:02:06 PM UTC, comment #2: This appears to be an issue with the JTAGICE3 firmware itself.
|
Joerg Wunsch <joerg_wunsch> |
Tue 06 May 2014 12:40:18 PM UTC, comment #1: I just did some quick testing with avrdude 6.1, which also shows the same problem. |
Matthijs Kooijman <matthijs> |
Fri 02 May 2014 09:43:30 AM UTC, original submission:
I'm having some trouble reading and verifying the lock bits with jtag3isp. jtag3 works as expected. I'm using Avrdude 6.0.1.
|
Matthijs Kooijman <matthijs> |
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 5 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2014-10-07 | joerg_wunsch | Status | Confirmed | Fixed | |
Open/Closed | Open | Closed | |||
2014-10-07 | joerg_wunsch | Status | None | Confirmed | |
Assigned to | None | joerg_wunsch | |||
2014-05-02 | matthijs | Attached File | - | Added log.txt, #31298 |
Powered by Savane 3.13-758e.
Corresponding source code
For future reference, the workaround was added in this commit: http://svn.savannah.gnu.org/viewvc/avrdude/trunk/avrdude/stk500v2.c?r1=1336&r2=1337