I've been working with AVR microcontrollers (specifically with ATmega328p's) for a bit and I got an ATmega32u4 that I wanted to program it to be used as a USB peripheral. However there is one problem: when I tried to flash a basic LED blink script to the AVR, AVRDUDE started sending back this weird error message:
avrdude.exe: verifying ... avrdude.exe: verifying ... avrdude.exe: verification error, first mismatch at byte 0x0000 0x00 != 0x0c avrdude.exe: verification error; content mismatch Note: before AVRDUDE gets to this point it reads the device signature and writes the hex files that I sent to it. Like normal.
After it does this, it tells me that the lock bit values have changed and I should either leave them alone or restore them to default. (The lock bits are never really the same and not all of them have to be changed.)
I don't know if this is an AVRDUDE issue or a programmer issue. I hope it's not the latter, as it's a new USBasp.
-U lfuse:r:CON:bandhfuse, or whichever locations are applicable to the device. You'll have to look up the bit positions in the manual. Usually Atmel Studio integrates this in the programming dialog (I haven't used it in forever). \$\endgroup\$