Skip to content
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

stk500v2 bootloader corrupts data when reading EEPROM #23

Closed
mlasevich opened this issue Jul 27, 2018 · 5 comments · May be fixed by #24
Closed

stk500v2 bootloader corrupts data when reading EEPROM #23

mlasevich opened this issue Jul 27, 2018 · 5 comments · May be fixed by #24
Assignees

Comments

@mlasevich
Copy link

READ_EEPROM command treats each address as 16bit instead of 8bit, as a result, the output of read EEPROM is corrupt, giving every other byte.

@mlasevich mlasevich changed the title stkv500v2 bootloader corrupts data when reading EEPROM stk500v2 bootloader corrupts data when reading EEPROM Jul 27, 2018
@mcuee
Copy link

mcuee commented Jun 3, 2022

This may be related. It does not seem to be an avrdude issue but rather the issue of the bootloader.

@mcuee
Copy link

mcuee commented Jun 12, 2022

I can confirm that #24 fixed this issue.

@mcuee
Copy link

mcuee commented Jun 9, 2023

For those who want to use an Arduino Core with the fix, you can use this one.
https://github.com/MCUdude/MegaCore

It has incorported #24 fix here.
MCUdude/MegaCore@eba4f4a

@mcuee
Copy link

mcuee commented Jun 10, 2023

The zip file here contains this EEPROM fix and a few other fixes.

@per1234 per1234 linked a pull request Jun 11, 2023 that will close this issue
@per1234 per1234 self-assigned this Jun 11, 2023
@per1234 per1234 added the bug label Jun 11, 2023
@per1234
Copy link
Contributor

per1234 commented Jun 11, 2023

If I understand correctly, #129 is a duplicate of this issue. Since #129 has a bit more information, I'll close this one in favor of the other.

@per1234 per1234 closed this as not planned Won't fix, can't repro, duplicate, stale Jun 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants