[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [avr-gcc-list] xmega support
From: |
Colin D Bennett |
Subject: |
Re: [avr-gcc-list] xmega support |
Date: |
Wed, 14 Jan 2009 15:43:47 -0800 |
On Wed, 14 Jan 2009 16:32:04 -0700
"larry barello" <address@hidden> wrote:
> Read the data sheet.
> http://www.atmel.com/dyn/resources/prod_documents/doc8077.pdf
OK, thanks. Since the data sheet says that both load and store
instructions can be used with EEPROM mapped into the RAM space, it
sounds like writing is possible without any extra effort. Nice!
To quote the data sheet, for the convenience of other readers:
4.7.1 Data Memory Mapped EEPROM Access
The EEPROM address space can optionally be mapped into the Data Memory
space to allow highly efficient EEPROM reading and EEPROM buffer
loading. When doing this EEPROM is accessible using load and store
instructions. Memory mapped EEPROM will always start at hexadecimal
address location 0x1000.
Regards,
Colin
> -----Original Message-----
> From: address@hidden
> [mailto:address@hidden On Behalf Of
> Colin D Bennett
> Sent: Wednesday, January 14, 2009 9:48 AM
> To: address@hidden
> Subject: Re: [avr-gcc-list] xmega support
>
> On Tue, 6 Jan 2009 22:37:15 -0800
> "larry barello" <address@hidden> wrote:
>
> > Thanks for the response. I dug a bit further into the manual and I
> > see that EEPROM can be mapped to SRAM space eliminating the need for
> > library EEPROM support in GCC.
>
> Does this EEPROM->SRAM mapping support writing, though?
>
> Regards,
> Colin
>
>
> _______________________________________________
> AVR-GCC-list mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/avr-gcc-list
>
>
Regards,
Colin
signature.asc
Description: PGP signature