Verification error when flashing Arduino

Started by robogrobo on in grblShield Support. 4 replies, last activity May 5, 2011. Closed.

#1607

Hi there

I have a problem when i'm using your patched hex file to flash my Arduino (328).

I always get:

avrdude -p m328p -c usbtiny -P /dev/tty.usbserial-A7006SAQ -b9600 -D -Uflash:w:grbl.hex

avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.01s

avrdude: Device signature = 0x1e950f

avrdude: reading input file "grbl.hex"

avrdude: input file grbl.hex auto detected as Intel Hex

avrdude: writing flash (17418 bytes):

Writing | ################################################## | 100% 28.33s

avrdude: 17418 bytes of flash written

avrdude: verifying flash memory against grbl.hex:

avrdude: load data flash data from input file grbl.hex:

avrdude: input file grbl.hex auto detected as Intel Hex

avrdude: input file grbl.hex contains 17418 bytes

avrdude: reading on-chip flash data:

Reading | ################################################## | 100% 16.86s

avrdude: verifying ...

avrdude: verification error, first mismatch at byte 0x0002

0xcb != 0x41

avrdude: verification error; content mismatch

avrdude: safemode: Fuses OK

avrdude done. Thank you.

Same, when i'm using the compiled hex file from the master branch on the github page from DANK.

No problem if i'm compiling the hex file on my machine, flashing works!

What are your fixes with the patch? Can you put the source files with the patch on your github page?

Thank you for your help.

Synthetos #1608

You said you got an Arduino UNO in a email. Does it toss up the SAME error code when you try it?

Try this avr-dude line:

avrdude -p m328p -c usbtiny -P /dev/tty.usbserial-A7006SAQ -b9600 -D -U flash:w:default/grbl.hex

ril3y

#1609

Thanks to Riley it works now. My ISP Programmer (usbtiny from adafruit) didn't like the parameter "-b 9600". So after removing it, every worked well when flashing my Arduino.

Synthetos #1610

AHA! Very cool... I got home from work today and tried it out on my Macbook. Of course I still used my avrispmkII vs. your TinyISP. However it worked with avrdude today:

ril3ys-MacBook-Pro:~$ avrdude -c avrispmkII -P usb -p atmega328p -U flash:w:Downloads/grbl_0_6b_atmega328p_16mhz_9600_with_grblshield_patch.hex

avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.00s

avrdude: Device signature = 0x1e950f

avrdude: NOTE: FLASH memory has been specified, an erase cycle will be performed

To disable this feature, specify the -D option.

avrdude: erasing chip

avrdude: reading input file "Downloads/grbl_0_6b_atmega328p_16mhz_9600_with_grblshield_patch.hex"

avrdude: input file Downloads/grbl_0_6b_atmega328p_16mhz_9600_with_grblshield_patch.hex auto detected as Intel Hex

avrdude: writing flash (17418 bytes):

Writing | ################################################## | 100% 5.41s

avrdude: 17418 bytes of flash written

avrdude: verifying flash memory against Downloads/grbl_0_6b_atmega328p_16mhz_9600_with_grblshield_patch.hex:

avrdude: load data flash data from input file Downloads/grbl_0_6b_atmega328p_16mhz_9600_with_grblshield_patch.hex:

avrdude: input file Downloads/grbl_0_6b_atmega328p_16mhz_9600_with_grblshield_patch.hex auto detected as Intel Hex

avrdude: input file Downloads/grbl_0_6b_atmega328p_16mhz_9600_with_grblshield_patch.hex contains 17418 bytes

avrdude: reading on-chip flash data:

Reading | ################################################## | 100% 4.99s

avrdude: verifying ...

avrdude: 17418 bytes of flash verified

avrdude: safemode: Fuses OK

avrdude done. Thank you.

ril3ys-MacBook-Pro:~$

If you are on OSX the AVR Mac Pack is a beautiful thing! Its a complete compiled toolchain for AVR. I installed that updated my path and I was good to go. I say this just an FYI for others.

Riley

#1611

Just one more data point, I had to set my baud rate for flashing at 57600 to get it to play nice.

Back to grblShield Support or the forum archive.