This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

About keyword xdata

target options in dallas 390: 0x31000:0x20000(size) RAM

#include <absacc.h>
...
unsigned char xdata text[0x100] _at_ 0x2000;//text is located in 0x32000;
...
XBYTE[0x2000] = 0x00;			//memory unit 0x2000,not 0x32000,is set zero;
...
Why doesn't the compiler deal with these two xdata statements in the same way?