Re: [avr-gcc-list] External EEPROM verses internal EEPROM data handling

[Sean D'Epagnier]

Yes, I thought about adding another section for this.

I found a lot of external eeproms annoying because they didn't want to
write a byte at a time.

What about using internal flash?  You can jump to the bootloader
section execute spm and then return, and in this way on a 64kb chip or
so, write your events to flash.  This is going to be slower, and has
some limitations, but it's a possible option.

Sean

On 5/4/09, Steven Michalske <address@hidden> wrote:
> On May 4, 2009, at 11:33 AM, David Kelly wrote:
>
>> On Mon, May 04, 2009 at 11:06:06AM -0700, Steven Michalske wrote:
>>> so your external EEPROM will be accessed by functions you write.  The
>>> compiler does not know how to interface to the external EEPROM.
>>
>> IIRC the compiler doesn't know internal AVR EEPROM either. AVR
>> EEPROM is
>> not mapped in CPU address space but it faked into the load map for
>> debugging and device programming.
>>
>
> Good catch Dave,  avr libc  has macros for accessing the AVR eeprom.
>
> Look at http://www.nongnu.org/avr-libc/user-manual/group__avr__eeprom.html
>    for insperation on writing your own macros.
>
> You can add another section to your linker script for the external
> eeprom if you wanted to as well.
>
> Steve
>
>> [85 lines deleted under top-post]
>>
>> --
>> David Kelly N4HHE, address@hidden
>> =
>> =
>> ======================================================================
>> Whom computers would destroy, they must first drive mad.
>
>
>
> _______________________________________________
> AVR-GCC-list mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/avr-gcc-list
>