Hi,
>> __code unsigned char __at( 0xf00000 )
>> values[] = {
>> 0x00, 0x01,
>> 0x02, 0x03,
>> 0x04, 0x05,
>> };
>>
>> Unfortunately, when I use the EEPROM read commands for index 0, I get
>> 0x00, for index 1, I get 0x02, and index 2, I get 0x04.
Could you check whether/which of the .hex / .o / .lst / .asm files are OK?
If I am not mistaken, there was a problem in gputils with addressing
certain memory spaces.
I might have a look into this myself later, but updating gputils to
whatever is currently out there might be worth a try.
Regards
Raphael
------------------------------------------------------------------------------
Download new Adobe(R) Flash(R) Builder(TM) 4
The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly
Flex(R) Builder(TM)) enable the development of rich applications that run
across multiple browsers and platforms. Download your free trials today!
http://p.sf.net/sfu/adobe-dev2dev
_______________________________________________
Sdcc-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sdcc-user
