You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Mike Brandon
Tue 18 Jul 2017 03:07:29 PM UTC
Programmer hardware: linuxgpio
Device type: m2560, m12834
Using linuxgpio and tested on m2560 and m1284 chips:
When a line in the hex file has less than 0x10 data bytes, avrdude does not write the high byte at the specified memory location as 0xFF. This in turn results in a verification error.
Attached is a sample hex file that was used to produce this result as well as logic captures when using avrdude and Atmel Studio 7.
Avrdude results in a verification error while Atmel Studio does not. It appears that the difference is that Atmel Studio will write 0xFF to the high byte while avrdude moves on to the next memory location and does not write a high byte.
mcuee
added
bug
Something isn't working
duplicate
This issue or pull request already exists
and removed
unconfirmed
Maybe a bug, needs to be reproduced by someone else
labels
Jul 10, 2022
Mike Brandon
Tue 18 Jul 2017 03:07:29 PM UTC
Programmer hardware: linuxgpio
Device type: m2560, m12834
Using linuxgpio and tested on m2560 and m1284 chips:
When a line in the hex file has less than 0x10 data bytes, avrdude does not write the high byte at the specified memory location as 0xFF. This in turn results in a verification error.
Attached is a sample hex file that was used to produce this result as well as logic captures when using avrdude and Atmel Studio 7.
Avrdude results in a verification error while Atmel Studio does not. It appears that the difference is that Atmel Studio will write 0xFF to the high byte while avrdude moves on to the next memory location and does not write a high byte.
file #41233: blink-mod-bitbang-read.PNG
file #41232: blink-2560-mod.hex
file #41231: blink-2560-mod-logic-avrisp-write.PNG
file #41230: blink-2560-mod-logic-avrdude-gpio-write.PNG
This issue was migrated from https://savannah.nongnu.org/bugs/?51497
The text was updated successfully, but these errors were encountered: