[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [avr-gcc-list] External EEPROM verses internal EEPROM data handling
From: |
David Kelly |
Subject: |
Re: [avr-gcc-list] External EEPROM verses internal EEPROM data handling |
Date: |
Mon, 4 May 2009 13:33:49 -0500 |
User-agent: |
Mutt/1.4.2.3i |
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.
[85 lines deleted under top-post]
--
David Kelly N4HHE, address@hidden
========================================================================
Whom computers would destroy, they must first drive mad.
Re: [avr-gcc-list] External EEPROM verses internal EEPROM data handling, Steven Michalske, 2009/05/04