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, dke...@hiwaay.net
=
=
======================================================================
Whom computers would destroy, they must first drive mad.
_______________________________________________
AVR-GCC-list mailing list
AVR-GCC-list@nongnu.org
http://lists.nongnu.org/mailman/listinfo/avr-gcc-list
