-
Notifications
You must be signed in to change notification settings - Fork 134
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix proposal for #1832 #1834
Fix proposal for #1832 #1834
Conversation
Perfect, I also checked with the 64du28. Works, too. Create random multi-memory file for AVR64DU28
Write that file to, and verify it against, a real AVR16DU28 using serialupdi (incl bootrow)
Terminal also works
|
Yeah, there is still the issue with repeated operation - if you perform bootrow write operation twice in a row without erasing the chip between the two, second write will be unsuccessful. Maybe I need to perform page erase first? Bottom line: if possible, wait with the merge, I might need to add more changes to the PR. |
There is now alternative PR for this issue and if accepted, I would suggest to merge the other one and reject this. |
This fix should enable correct operation of bootrow memory on compatible devices using serialupdi programming protocol.
Before the fix:
After the fix: