AVR Downloader/UploaDEr - Patches: patch #9507, Fix UPDI chip erase
You are not allowed to post comments on this tracker with your current authentication level.
patch #9507: Fix UPDI chip erase
Submitter: | Jan Egil Ruud <je_ruud> | ||
Submitted: | Thu 30 Nov 2017 05:32:48 PM UTC | ||
Category: | None | Priority: | 6 |
Status: | Done | Privacy: | Public |
Assigned to: | joerg_wunsch | Open/Closed: | Closed |
Jump to the original submission
Tue 16 Jan 2018 09:18:24 PM UTC, comment #10: |
Joerg Wunsch <joerg_wunsch> |
Tue 16 Jan 2018 07:18:32 AM UTC, comment #9: So, after sorting some stupid mistakes related to debug HW and misunderstanding of code I myself had made, I finally got it working again.
|
Jan Egil Ruud <je_ruud> |
Wed 10 Jan 2018 07:09:03 AM UTC, comment #8: This is just confusing. My XPlainedPro is also failing now, but with reason 0x1a, which we've never seen before... And it doesn't help to revert back to earlier commits either, still same failure.
|
Jan Egil Ruud <je_ruud> |
Tue 09 Jan 2018 11:33:02 PM UTC, comment #7: Thanks, looks good. Commited in r1405.
|
Joerg Wunsch <joerg_wunsch> |
Fri 05 Jan 2018 12:53:26 PM UTC, comment #6: Here's another attempt on the unlocking, and it should be according to your suggested strategy.
|
Jan Egil Ruud <je_ruud> |
Tue 02 Jan 2018 09:32:02 PM UTC, comment #5: Thanks for the explanation.
|
Joerg Wunsch <joerg_wunsch> |
Tue 02 Jan 2018 11:03:32 AM UTC, comment #4: With the new UPDI AVR's the locking concept has changed. Previously, on old AVR's, when you locked a device you just made the flash unreadable. With the new UPDI AVR's you lock down the whole chip, including the ability to read the signature. There are datasheets that state otherwise, but that is wrong and will be corrected (as soon as possible...).
|
Jan Egil Ruud <je_ruud> |
Mon 01 Jan 2018 12:40:21 PM UTC, comment #3: The "enter prog mode" to read signature failed on a locked device, which meant that you were unable to issue a chip erase to unlock it.
|
Jan Egil Ruud <je_ruud> |
Sat 30 Dec 2017 12:06:35 AM UTC, comment #2: Committed in r1403, except for the changes in main.c (by now,
|
Joerg Wunsch <joerg_wunsch> |
Fri 29 Dec 2017 11:51:18 PM UTC, comment #1: Why did you put the UPDI chip erase that early in the main()
|
Joerg Wunsch <joerg_wunsch> |
Thu 30 Nov 2017 05:32:48 PM UTC, original submission:
Chip erase on devices with UPDI is done by setting a special parameter before entering prog mode. This patch fixes that. |
Jan Egil Ruud <je_ruud> |
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 8 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2021-11-23 | joerg_wunsch | Status | In Progress | Done | |
Open/Closed | Open | Closed | |||
2018-01-16 | je_ruud | Attached File | - | Added unlock_avr8x_fix.patch, #42921 | |
2018-01-05 | je_ruud | Attached File | - | Added unlock_avr8x.patch, #42847 | |
Attached File | - | Added unlock_test_output.txt, #42848 | |||
2017-12-29 | joerg_wunsch | Status | None | In Progress | |
Assigned to | None | joerg_wunsch | |||
2017-11-30 | je_ruud | Attached File | - | Added fix-updi-chiperase.patch, #42535 |
Powered by Savane 3.13-cf05.
Corresponding source code
Applied in r1417 (with minor modifications).
Flash byte read is used in terminal mode (avrdude -t), and I
can confirm it appears to be broken now.
Unlocking my unresponsive XplainedPro board worked without
trouble.