Go Down

Topic: avrdude content mismatch: Linux, ATMEGA328 (Read 5 times) previous topic - next topic

retrolefty

#5
Jun 26, 2009, 05:12 am Last Edit: Jun 26, 2009, 05:13 am by retrolefty Reason: 1
Quote
If you bought the ATmega328 separately remember the '328 is not the same as the '328P


I've only seen 328P data sheet. Is there such a device as a '328?

Lefty

trialex

Yeah now that I think of it, not sure. I think maybe I was thinking of when you use avrdude from the command line, there is a difference and you need to select the part as '328P.

Still, check that the board you have selected is Arduino with 328, not just Duemilanove

gzip

I was having the same problem and it turned out to be a power issue. A switch from USB power to wall wart solved it. I had a similar problem when I first built my Arduino. I could program Atmega8s but it would fail on Atmeg168. I was using a 9v battery at the time.

CaptainObvious

Very interesting.

I haven't tried the power issue yet, but I have noticed I only get the error when I'm trying to use a (HUGE), well bitmap that was converted into a .h file, it uses PROGMEM.

avrdude: verification error, first mismatch at byte 0x0080
        0xff != 0x05
avrdude: verification error; content mismatch

Once I upload normally to the board.. using a different sketch with the LCD, it works fine.

And actually.. when I uploaded a sketch that included a different .h file, the bootloader locked up on me completely. (I was able to able to lock it up multiple times, just to make sure) I'm guessing it was some kind of memory error? I don't have much experience with PROGMEM, I have read up on the Playground and some random sites but not sure how to get it to work in my position.

I did just try with an external wall-wart, regulated at 11.49 ish volts, can supply 1.5 amps... without any luck, still get the error when I upload the first sketch. (Keep in mind, it does say it's done uploading, and the LCD initializes.. but it doesn't print the picture, which is error in the code I'm positive.


Just curious, did you try different sketches when you were testing? For example using just the Blink example? Just to rule out anything with memory leaks. (I know they say it's not very easy to lock up the Arduino like this.. but I just did, repeatedly lol, inexperience for the win!)

Elbriga

You must set the baud rate for the 328(p) chip with " -b 57600 " on the avrdude line

Go Up