-
Notifications
You must be signed in to change notification settings - Fork 136
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
Make default EEPROM readback values 0xff for STK500 v1 programmer #1753
Conversation
I will carry out some tests with this PR. The plan is to test with ATmega328P, ATmega8A and ATmega256. |
Firstly this PR is good for ATmega328P. Tested under macOS 14.4.1 (Mac Mini M1 2020).
|
git main has issues with ATmega2560 as well. This PR is good to fix the issue again.
|
For ATmega128A, both git main and this PR are okay.
|
I think this PR is now good to be merged. |
One more sanity check, it does not cause regression with "Arduino as ISP" as well.
BTW, git main is okay with "Arduino as ISP".
|
Same for ATmega8A. This PR is good.
git main is also good.
|
For ATmega168P, situation is the same as ATmega328P. git main is bad but this PR is good.
|
Fixes #1713
That bug probably affects all classic parts. Rather than changing the config
readback
values to0xff 0xff
, this PRreadback
values as specified in the .atdf (0x00 0x00
)0x00 0x00
values to0xff 0xff
Please check a few other parts than m328p (basically any classic part) whether they exhibit the EEPROM writing problem without this PR and whether this PR would introduce a regression.