It's a bit more complicated. avrdude switches values between fuses when
reporting them (bug?) and when you see 0x07 where you expect to see 0xFF at
the extended fuse that's okay (at least for atmega 328p). You only need to
change lfuse into 0xE2 to disable downscaling to 1MHz and leave the rest at
Jan,
For the Arduino Uno we have been using the following command string
successfully:
avrdude -p m328p -c avrispmkII -P usb -U efuse:w:0xFF:m -U hfuse:w:0xD9:m -U
lfuse:w:0xFF:m -U flash:w:uno.hex:i -U eeprom:w:uno.eep.hex:i
Thus argument for efuse is set to FF instead of 05.
The short
Default values I use are: lfuse = 0x62, hfuse = 0xDF, efuse = 0x01.
Highspeed mode: lfuse = 0xE2.
On Tue, Oct 16, 2018 at 10:01 PM John Verne wrote:
> Oh, wait. My last response is just going to add to the confusion. Sorry
> about that.
>
> Are you sure you have the fuse settings right in your
Oh, wait. My last response is just going to add to the confusion. Sorry
about that.
Are you sure you have the fuse settings right in your command line? Have
you swapped efuse and lfuse by accident in that command line?
I would expect efuse to be 0xFF, which is the default. 0x05 doesn't really
It is warning you that you are changing the low fuse settings. This is
because changing fuses can permanently damage the chip.
In this case it looks like the existing fuse settings are CKSEL1 only, but
your AVRDude command wants to set 0x05, which enables a bunch of fuses.
You should be ok
When loading AmForth into my Arduino Uno I get an error on the end.
My question is what to do in that case?
Are my settings of the fuse one?
Cheers,
Jan
avrdude: verifying ...
avrdude: verification error, first mismatch at byte 0x
0xfd != 0x05
avrdude: verification error; content
