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
A bit of research lead me to this. The SYSCFG0 fuse byte is supposed to be 0xC9 (according to the datasheet), not 0xCD like the fuses_4809.bin file specifies.
But why bother with a binary file in the first place? Each fuse byte is accessable by passing fuse0..fuse8 to avrdude ("-Ufuse5:w:{bootloader.SYSCFG0}:m" for instance), and it makes everything more transparent to the users and developers. I actually had to find myself a binary file editor in order to track this down.
The text was updated successfully, but these errors were encountered:
MCUdude
changed the title
Wrong SYSCFG0 fuse byte value inside fuses.bin
Wrong SYSCFG0 fuse byte value inside fuses_4809.bin
Feb 19, 2019
A bit of research lead me to this. The SYSCFG0 fuse byte is supposed to be 0xC9 (according to the datasheet), not 0xCD like the fuses_4809.bin file specifies.
I can see you've done an attempt in the boards.txt file, but this line is not picked up by avrdude.
But why bother with a binary file in the first place? Each fuse byte is accessable by passing fuse0..fuse8 to avrdude (
"-Ufuse5:w:{bootloader.SYSCFG0}:m"
for instance), and it makes everything more transparent to the users and developers. I actually had to find myself a binary file editor in order to track this down.The text was updated successfully, but these errors were encountered: