Mpide avrdude error on MacOS X

Created Wed, 15 Jun 2011 01:02:13 +0000 by cfaulkingham

cfaulkingham

Wed, 15 Jun 2011 01:02:13 +0000

I am getting the following avrdude error when trying to upload a sketch.

avrdude: verification error, first mismatch at byte 0x0180
         0x00 != 0xff
avrdude: verification error; content mismatch

I dropped Mpide into my App folder and installed the FTDI driver that came with it. Anything else I am supposed to do?

I am using a UNO32.

BTW, I tried using Arduinio 022 with my UNO8 and it worked fine.

Trev

Wed, 15 Jun 2011 10:27:43 +0000

You did select the Uno32 from the board list, right? (I didn't and also had strange errors. Duh!)

cfaulkingham

Wed, 15 Jun 2011 10:58:38 +0000

You did select the Uno32 from the board list, right? (I didn't and also had strange errors. Duh!)

Yep, I selected Uno32.

cfaulkingham

Wed, 15 Jun 2011 13:00:14 +0000

I also tried my Arduino UNO and it did the same thing with Mpide.

jumpin_jack

Wed, 15 Jun 2011 16:56:50 +0000

I'm not having any problems on my Mac, but I had the FTDI drivers installed from the FTDI website rather than the ones packaged with mpide. http://www.ftdichip.com/Drivers/VCP.htm I forget the exact version number.

cfaulkingham

Wed, 15 Jun 2011 23:24:36 +0000

I'm not having any problems on my Mac, but I had the FTDI drivers installed from the FTDI website rather than the ones packaged with mpide. ... I forget the exact version number.

They seem to be the same ones. However I manually removed the driver from /System/Library/Extensions/ and re-installed from the FTDI web site. I also re-installed Mpide and I am still geting the same error.

I guess I will try to re-install avrdude that I had it originally installed it from the CrossPack toolkit.

cfaulkingham

Wed, 15 Jun 2011 23:29:45 +0000

I guess I will try to re-install avrdude that I had it originally installed it from the CrossPack toolkit.

Ok that didn't work either.

WestfW

Thu, 16 Jun 2011 02:40:00 +0000

There's a "known bug" in avrdude where it will assume that flash is in the erased state, and "skip" programming a page full of 0xFF bytes for the sake of efficiency. Since bootloader-based programming does NOT start with a chip erase, it ends leaving the old flash content in those pages...

http://code.google.com/p/arduino/issues/detail?id=273

Could this be your problem?

cfaulkingham

Wed, 29 Jun 2011 01:58:33 +0000

Well I am getting the same error on Windows7. It's starting to look like I have a bad board.

http://twitpic.com/5icutf