Cannot program EEPROM through Dragon and sometimes through Xplained

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

I have been writing a program for the 324PB, and when I try to program the EEPROM I get this error: "Verifying EEPROM...Failed! address=0x0002 expected=0x25 actual=0x05"

Interestingly, the details of this message change from time to time, like yesterday it failed on address 0x0000.

I have some 324PBs on custom PCBs that I am programming using JTAG and the AVR Dragon. I also have a few 324PB Xplained Pro boards, using the EDBG interface. The Xplained boards also fail, but they work sometimes, unexpectedly. The Xplain failed today with "Verifying EEPROM...Failed! address=0x0001 expected=0x05 actual=0x00".

 

Does anyone know why this would be happening across interfaces and chips? I surely haven't blown out ALL of the EEPROMs I have.

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

"Preserve EEPROM" fuse set?

You can put lipstick on a pig, but it is still a pig.

I've never met a pig I didn't like, as long as you have some salt and pepper.

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

Yes, it has a check mark next to it in the Fuses section of the Atmel Studio Programming dialog. I can also see my device signature and program and debug it from Atmel Studio.

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

dtreth@gmail.com wrote:
Yes, it has a check mark next to it in the Fuses section of the Atmel Studio Programming dialog.

Well, if you are "preserving EEPROM", and then you try to send new EEPROM values, of course they will not verify because the previous values are kept.

You can put lipstick on a pig, but it is still a pig.

I've never met a pig I didn't like, as long as you have some salt and pepper.

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

I am programming using JTAG and the AVR Dragon.

You mean ISP as the 328 does not have JTAG.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

js wrote:

I am programming using JTAG and the AVR Dragon.

You mean ISP as the 328 does not have JTAG.

Ummm--when you reach a certain age, some things start to fail...

 

dtreth@gmail.com wrote:
I have been writing a program for the 324PB,

You can put lipstick on a pig, but it is still a pig.

I've never met a pig I didn't like, as long as you have some salt and pepper.

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

ds

 

dreth has some clutter in his question.

 

I don't know what a Xplained board ON a custom pcb is.

 

Does he have a bare 324 Xplained to test?

 

Happy Holidays!
 

Imagination rules the world-Napoleon

Last Edited: Wed. Dec 21, 2016 - 09:48 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hey now... Seems to be working. OK, so now I have two follow-up questions.

 

1) I presumed the meaning of the EESAVE fuse was to allow you the device to keep its EEPROM values upon restarting, I.E. what you'd want EEPROM to do. What is the actual meaning of this fuse, then? And should I set it again after programming the .eep file?

 

2) I had been using this deployment strategy for a week without problems, but this started happening yesterday. I did not change any fuse settings. I just read the value out when asked on the forum .

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

The EESAVE (when checked) prevents the EEPROM from being erased when the chip is erased for programming (for when you want to preserve what may be in the EEPROM).

David

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

dtreth@gmail.com wrote:

Hey now... Seems to be working. OK, so now I have two follow-up questions.

 

1) I presumed the meaning of the EESAVE fuse was to allow you the device to keep its EEPROM values upon restarting, I.E. what you'd want EEPROM to do. What is the actual meaning of this fuse, then? And should I set it again after programming the .eep file?

 

2) I had been using this deployment strategy for a week without problems, but this started happening yesterday. I did not change any fuse settings. I just read the value out when asked on the forum .

Re 1) deja vu from another current thread...what does the datasheet say?

Re 2), one guess is that your app didn't change EEPROM values until recently.  So if you don't change anything it could indeed verify.

You can put lipstick on a pig, but it is still a pig.

I've never met a pig I didn't like, as long as you have some salt and pepper.