verify fail

Go To Last Post
9 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I got a problem in programming the ATMEGA32 using avrdude. It always report fail in verifying the chip. I try a couple of brand new chip and got the same result. The programmer can program other broads with ATMEGA32 with no problem. Thanks for any help and advices.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Correct AVR model selected in the programming dialogue?
Can you read the device signature bytes with success repeatedly?

As of January 15, 2018, Site fix-up work has begun! Now do your part and report any bugs or deficiencies here

No guarantees, but if we don't report problems they won't get much of  a chance to be fixed! Details/discussions at link given just above.

 

"Some questions have no answers."[C Baird] "There comes a point where the spoon-feeding has to stop and the independent thinking has to start." [C Lawson] "There are always ways to disagree, without being disagreeable."[E Weddington] "Words represent concepts. Use the wrong words, communicate the wrong concept." [J Morin] "Persistence only goes so far if you set yourself up for failure." [Kartman]

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Yes, the model is selected correctly. Otherwise, the error message is not verify failed.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Use the -v option on avrdude to get more verbose detail of what's going on. Keep adding v's (-vv, -vvv, -vvvv) to get more and more detail. Hopefully that will give you a clue as to what's going on - if not post the verbose output here.

But one of he key things that Johan alluded to is whether the ISP programmer can read the signature in the first place. Every time avrdude runs it starts by checking that the signature is OK - are you seeing that. If it fails at the hurdle all other bets are off.

Cliff

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Yes, it reads the signature correctly and proceed to program the flash and then reading out the flash for verification. But it always report failed in verification at address 0.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Are the device lock bits set? Are you doing a full chip erase before programming? (which would clear the lock bits)

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Yes, I did full chip erase before programming everytime.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

OK so what do you get after a failed programming cycle if you just give avrdude a command to read the chip contents into a different .hex file - how does it then differ from what you tried to program into it?

(you may want to hex2bin both files then use a binary comparison like the DOS command "fc /b file1.bin file2.bin")

Cliff

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

It sounds very much like a known "feature" of parallel port homebrew programmers.

Read the Tutorial on parallel port programmers. And make sure that you have no ringing on your SCK line.

David.