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 default.
Here's a useful page: http://www.engbedded.com/fusecalc Example, choose Atmega328p from the pull down menu, uncheck "divide clock by 8" and you get the right fuse values including the story about the 0x07/0xFF. rgds On Tue, Oct 16, 2018 at 10:01 PM John Verne <john.ve...@gmail.com> 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 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 > make sense, but does set a brown-out detector level -- which is true for > 0xFD as well. > > The hfuse at 0xD9 is the default, and can be the most dangerous to change. > Consider this an expert setting. > > lfuse is the one we usually want to change (unless tweaking brownout > detection or debugging). This is the one where we set clock speed and > oscillator source and so on, and is the one I usually customize. This > should not be 0xFF unless you want to run at 1MHz instead of 8MHz. This is > the one that is usually at 0x05 or 0x62. > > Double check your Makefile or the command you are typing in, and make sure > you have't swapped the efuse and lfuse values. > > On Tue, 16 Oct 2018 at 14:56, Jan Kromhout <krom1...@hotmail.com> wrote: > > > 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 0x0000 > > 0xfd != 0x05 > > avrdude: verification error; content mismatch > > > > avrdude: safemode: efuse changed! Was 5, and is now fd > > Would you like this fuse to be changed back? [y/n] n > > avrdude: safemode: Fuses OK (E:05, H:DE, L:FF) > > > > My question is what to do in that situation? > > > > > > > > > > > > MacBook-Pro-van-Jan-5:avrdude jankromhout$ avrdude -P > > /dev/tty.usbmodem00230362 -c avrispv2 -b 19200 -p m328p -e -U > > flash:w:uno.hex:i -U eeprom:w:uno.eep.hex:i -U efuse:w:0x05:m -U > > hfuse:w:0xD9:m -U lfuse:w:0xFF:m > > > > avrdude: AVR device initialized and ready to accept instructions > > > > Reading | ################################################## | 100% 0.00s > > > > avrdude: Device signature = 0x1e950f (probably m328p) > > avrdude: erasing chip > > avrdude: reading input file "uno.hex" > > avrdude: writing flash (32638 bytes): > > > > Writing | ################################################## | 100% 2.06s > > > > avrdude: 32638 bytes of flash written > > avrdude: verifying flash memory against uno.hex: > > avrdude: load data flash data from input file uno.hex: > > avrdude: input file uno.hex contains 32638 bytes > > avrdude: reading on-chip flash data: > > > > Reading | ################################################## | 100% 1.86s > > > > avrdude: verifying ... > > avrdude: 32638 bytes of flash verified > > avrdude: reading input file "uno.eep.hex" > > avrdude: writing eeprom (144 bytes): > > > > Writing | ################################################## | 100% 0.06s > > > > avrdude: 144 bytes of eeprom written > > avrdude: verifying eeprom memory against uno.eep.hex: > > avrdude: load data eeprom data from input file uno.eep.hex: > > avrdude: input file uno.eep.hex contains 144 bytes > > avrdude: reading on-chip eeprom data: > > > > Reading | ################################################## | 100% 0.02s > > > > avrdude: verifying ... > > avrdude: 144 bytes of eeprom verified > > avrdude: reading input file "0x05" > > avrdude: writing efuse (1 bytes): > > > > Writing | ################################################## | 100% 0.01s > > > > avrdude: 1 bytes of efuse written > > avrdude: verifying efuse memory against 0x05: > > avrdude: load data efuse data from input file 0x05: > > avrdude: input file 0x05 contains 1 bytes > > avrdude: reading on-chip efuse data: > > > > Reading | ################################################## | 100% 0.00s > > > > avrdude: verifying ... > > avrdude: verification error, first mismatch at byte 0x0000 > > 0xfd != 0x05 > > avrdude: verification error; content mismatch > > > > avrdude: safemode: efuse changed! Was 5, and is now fd > > Would you like this fuse to be changed back? [y/n] n > > avrdude: safemode: Fuses OK (E:05, H:DE, L:FF) > > > > avrdude done. Thank you. > > > > MacBook-Pro-van-Jan-5:avrdude jankromhout$ > > > > _______________________________________________ > > Amforth-devel mailing list for http://amforth.sf.net/ > > Amforth-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/amforth-devel > > > > > -- > > > [image: --] > > John Verne > [image: https://]about.me/jverne > <https://about.me/jverne?promo=email_sig> > > _______________________________________________ > Amforth-devel mailing list for http://amforth.sf.net/ > Amforth-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/amforth-devel > _______________________________________________ Amforth-devel mailing list for http://amforth.sf.net/ Amforth-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amforth-devel
