??? 02/20/08 09:06 Read: times |
#151195 - Comments Responding to: ???'s previous message |
Rather than use XBYTE, use _at_ to place properly-named variables at the required XDATA locations.
Otherwise, the tools don't know that those locations are in use - and will assume that they are available for general use as XDATA memory... |
Topic | Author | Date |
Real Time Clock and other | 01/01/70 00:00 | |
How to post source code | 01/01/70 00:00 | |
post- source code | 01/01/70 00:00 | |
internal XRAM? | 01/01/70 00:00 | |
its not logical but | 01/01/70 00:00 | |
modified code using UIF | 01/01/70 00:00 | |
re | 01/01/70 00:00 | |
UIP | 01/01/70 00:00 | |
Will get stuck | 01/01/70 00:00 | |
If you used _at_ instead of XBYTE .... | 01/01/70 00:00 | |
Comments | 01/01/70 00:00 | |
reply to coments | 01/01/70 00:00 | |
_at_ instead of XBYTE | 01/01/70 00:00 | |
pin assignments | 01/01/70 00:00 | |
You still haven't answered the questions! | 01/01/70 00:00 | |
xdata i/o | 01/01/70 00:00 | |
just do it | 01/01/70 00:00 | |
Default | 01/01/70 00:00 | |
sorry i can't reply due to my ill health | 01/01/70 00:00 | |
address | 01/01/70 00:00 | |
perfect!! | 01/01/70 00:00 | |
try to understand | 01/01/70 00:00 | |
yes i finally got the point![]() | 01/01/70 00:00 | |
Aside: Not a macro | 01/01/70 00:00 | |
Delay? | 01/01/70 00:00 | |
agree | 01/01/70 00:00 | |
Keil know | 01/01/70 00:00 |