AVR-Chat

OK, I'm confused.  I am starting debug, and then loading the data from 
the .eep file created by the assembler.
To be certain it was loading the EEPROM data, I saved the data back out 
to another file and manually
confirmed that the data in the file represents the data in my EEPROM table.

Here's the problem:   Watching the EEPROM in the "IO" view in the 
debugger, I am never seeing any
data in EEDR.  Likewise, of course, no data is being fed to my program.  
What the (*&*&???????


tom

Additional information:

watching the EEPROM in the IO view, I can see that the address in the 
low byte address register is
incrementing and decrementing as it should, per my code.  The problem is 
that no data is being read
from those locations in the EEPROM, despite there being data THERE,  Am 
I running into yet another
problem with AVRStudio, or am I missing some other subtle point?

tom

At 11:46 AM 3/10/2007, you wrote:

>Am I running into yet another
>problem with AVRStudio, or am I missing some other subtle point?

Have downloaded the data into EEPROM by upload/download memory?

 >> HOW << are you trying to read the eeprom?

Regards

John Samperi

********************************************************
Ampertronics Pty. Ltd.
11 Brokenwood Place Baulkham Hills, NSW 2153 AUSTRALIA
Tel. (02) 9674-6495       Fax (02) 9674-8745
Email: john@ampertronics.com.au
Website  http://www.ampertronics.com.au
*Electronic Design * Custom Products * Contract Assembly
********************************************************

John Samperi wrote:
>
> At 11:46 AM 3/10/2007, you wrote:
>
> >Am I running into yet another
> >problem with AVRStudio, or am I missing some other subtle point?
>
> Have downloaded the data into EEPROM by upload/download memory?
>
> >> HOW << are you trying to read the eeprom?
>









Yes, I have used the up/.download memory feature.

I tested that by downloading it into the simulator, then
saving it to a differently named file, and manually
scanning that file to determine if the correcct data
were present.   They were

   I am reading the EEPROM per the sample code in that data
sheet.  I know this is working correctly because I can watch the
associated registers in the IO view, and see that the address
\register for the EEPROM is taking on correct values, but no data is
appearing in the EEPROM data register (EEDR).

tom

>
>    I am reading the EEPROM per the sample code in that data
> sheet.  I know this is working correctly because I can watch the
> associated registers in the IO view, and see that the address
> \register for the EEPROM is taking on correct values, but no data is
> appearing in the EEPROM data register (EEDR).

What address do you have in the EEAR when you do the read?

At 01:26 PM 3/10/2007, you wrote:
>    I am reading the EEPROM per the sample code in that data
>sheet.

Just remember that the last 2 steps?? need to be performed within
4 cycles IIRC. So if you are dodling with the simulator it may not
work. May be better to run the whole routine and just put a breakpoint
after reading the EEDR.



Regards

John Samperi

********************************************************
Ampertronics Pty. Ltd.
11 Brokenwood Place Baulkham Hills, NSW 2153 AUSTRALIA
Tel. (02) 9674-6495       Fax (02) 9674-8745
Email: john@ampertronics.com.au
Website  http://www.ampertronics.com.au
*Electronic Design * Custom Products * Contract Assembly
********************************************************

David VanHorn wrote:
>
> >
> > I am reading the EEPROM per the sample code in that data
> > sheet. I know this is working correctly because I can watch the
> > associated registers in the IO view, and see that the address
> > \register for the EEPROM is taking on correct values, but no data is
> > appearing in the EEPROM data register (EEDR).
>
> What address do you have in the EEAR when you do the read?
>
> __
>
>  







  The addresses in the EEAR vary from 0x00 to 0x24 (since there are 36 
itrems in the table
stored in the EEPROM this would be correct).

tom

> 
> Yes, I have used the up/.download memory feature.
> 
> I tested that by downloading it into the simulator, then
> saving it to a differently named file, and manually
> scanning that file to determine if the correcct data
> were present.   They were
> 
>    I am reading the EEPROM per the sample code in that data
> sheet.  I know this is working correctly because I can watch the
> associated registers in the IO view, and see that the address
> \register for the EEPROM is taking on correct values, but no data is
> appearing in the EEPROM data register (EEDR).
> 
> tom
> 

How about the EERE bit? It needs to be set to trigger a read...

Bruce

Bruce Parham wrote:
>
>
> >
> > Yes, I have used the up/.download memory feature.
> >
> > I tested that by downloading it into the simulator, then
> > saving it to a differently named file, and manually
> > scanning that file to determine if the correcct data
> > were present. They were
> >
> > I am reading the EEPROM per the sample code in that data
> > sheet. I know this is working correctly because I can watch the
> > associated registers in the IO view, and see that the address
> > \register for the EEPROM is taking on correct values, but no data is
> > appearing in the EEPROM data register (EEDR).
> >
> > tom
> >
>
> How about the EERE bit? It needs to be set to trigger a read...
>

















Yes, I am setting the EERE bit, as per the sample code in the data sheet
I have successfully used EEPROM data in the past, with other programs
and other AVRs.

tom

> ,_._,___