Go Down

Topic: Need help, FAST (please) (Read 2335 times) previous topic - next topic

nkcelectronics

Quote
I also ordered the "Arduino Diecimila compatible USB board complete KIT with pre-soldered FT232BL" from eBay..
I hope I don't have this problem while I'm messing with it :o

do you think i should order some spare ATMEGA168 chips just in case?  :-/ seeing as I am a total noob at Arduino, microcontrollers, and programming  :D

not that i don't understand what its about :)

The Arduino/Freeduino are prototyping boards, and it means that a lot of bad things can happen to them while developing new electronics applications.  It is always a good practice to have a couple of spare atmega168's, maybe you want to keep one with a sketch programmed, or you want to deploy it using some barebone Arduino boards, etc.  I received only a couple of problem reports with the kits.  I burned an USB chip on a freeduino board just by placing the board on top of some wires by mistake, while it was connected... so a lot of things can happen to these boards while you are prototyping projects with them.

The_Bongmaster

Quote
Quote
I also ordered the "Arduino Diecimila compatible USB board complete KIT with pre-soldered FT232BL" from eBay..
I hope I don't have this problem while I'm messing with it :o

do you think i should order some spare ATMEGA168 chips just in case?  :-/ seeing as I am a total noob at Arduino, microcontrollers, and programming  :D

not that i don't understand what its about :)

The Arduino/Freeduino are prototyping boards, and it means that a lot of bad things can happen to them while developing new electronics applications.  It is always a good practice to have a couple of spare atmega168's, maybe you want to keep one with a sketch programmed, or you want to deploy it using some barebone Arduino boards, etc.  I received only a couple of problem reports with the kits.  I burned an USB chip on a freeduino board just by placing the board on top of some wires by mistake, while it was connected... so a lot of things can happen to these boards while you are prototyping projects with them.


I'll bare that in mind. i'll have to make an anti-static surface to work on and keep my wires away from the underside :D
i'll prolly get more chips soon too just to make sure i have some spare for projects and emergencys :)
B-dui in creation.

Beardy241

Same has happened to me.  The sketch on the board continues to function correctly but I cannot upload new sketches.

Thankfully I picked up a spare chip when I ordered my board. - phew!

Guess I gotta pull in a Bare-Bones jobby for the old chip and retire it into permanent application.  (It's running an automatic PIR sensor driven night lite)

[m]

gijs

i have some new chips now also and it works!
i am happy the FTDI is not broken!
So it probably was the boot loader that got messed up..


yanque

#19
Dec 26, 2007, 06:20 pm Last Edit: Dec 27, 2007, 01:03 am by yanque Reason: 1
Hello,

I've had the same problem with two Arduino Mini. Without any reason (same software, same USB interface, same PC, almost same moment,...), suddenly, I can not upload the program. (I got the same "avrdude: verification error, first mismatch at byte 0x00xx" and that staff)

I've programmed the Arduino before hundred of times, so I think it's not my fault. I've tried to use avrdude to solve the problem, but no way; I am able to read the flash content, but I am not able to read the state of the lock bits or upload any skecth to the flash (well, I´m not an expert with avrdude, and perhaps there is something I'm missing, but I don´t think so).

I only find two possible explanations for this:

- First one; Perhaps I've programed the flash too many times (Atmel guarantees 10000 cycles). Well, I´ve tried to figure out how may times I´ve programmed the arduino, probably 1000-3000 times, but I´m sure I´ve not reached even 5000 cycles. Could be a defective part, but it happened to me with two parts.

- Second; for any strange reason, the flash has been locked, and I'm not able to reprogram it. As I said, I can not read the lock bits with avrdude (any clue to do it?). I can not even read the flash or the eeprom in terminal mode (I always read 0's), but I can dump their contents to a file in command line mode (I don't know this is the normal behaviour or not)

Any idea or help? Due to this problem, I had to unmount a really complex piece of hardware with the Arduino Mini deeply embedded inside, and change it by a new Arduino (and, of course, the day before the demo... a nightmare, you know). I´m really worried about this, because now I don´t feel like using a platform that it is not reliable, unless I can understand what was the reason for this failure.

Thanks

astolfo14

I got to Vienna a couple hours ago, unpacked the sculpture, plugged in to modify the program, and of course it isn't working.  I'm using the same laptop, the same arduino, nothing was added, nothing was taken away.  My code verifies ok, and the arduino runs the sketch I last loaded into it just fine.

The message I am getting is

avrdude: verification error, first mismatch at byte 0x0000
            0x39 != 0x00

avrdude: verification error; content mismatch

I'm not finding anything of much use checking AVR Dude forums.

Any help?  The opening is in a couple hours!!!  Many thanks in advance


Trabajando normalmente, de un momento a otro se me presentó el mismo error. En un Diecimila con un atmega8. La solución fue sustituir  el chip por atmega8 con el bootloader.

kleverd

#21
Aug 09, 2010, 09:27 pm Last Edit: Aug 10, 2010, 08:02 pm by kleverd Reason: 1
I'v had same problem few days ago. The main reason was key -D in command line for AVRDUDE. Arduino ide generates command line automaticaly, and i've found no way to change in usual way. Key -D prevents erasing chip before flashing (makes uploading faster). Thats a bug of arduino.
There is only one way to solve the problem - make a patch for avrdudeuploader.class in pde.jar - flush all -D's with spaces (20h).

Go Up