On 28.09.2015 11:13, Maarten Brock wrote:
>
>> I will try to answer your first question this way: I would like the linker
>> could handle the EEPROM as an additional memory space so that addresses
>> are calculated by the linker automatically (i.e. by defining an alternate
>> descriptor like __eep
Hello Victor,
> Thank you for your response. As I think over about this issue, I wonder
> how did Atmel guys thought this should have been addressed from the
> compiler/linker perspective.
>
> In the AT89C51ID2 chip DATA/IDATA, XDATA and EEPROM are all overlapped
> (i.e. all three begin at address
Hello Victor,
I think the first question should be: do you want the linker to locate the
variables in eeprom or would you like to have control over what ends up
where? The latter is often better if you intend to have firmware upgrades
in the future but with the same eeprom contents (e.g. calibrati
