??? 02/20/08 17:46 Read: times |
#151218 - _at_ instead of XBYTE Responding to: ???'s previous message |
Kesav Mahesh Kumar said:
XBYTE instruction can be perfectly used in the context of this rtc. Note that XBYTE is not an instruction - it's just a macro. It effectively gives you access to a pointer as a "magic number" Again, this means that the tools have no idea that the XDATA addresses used by your RTC are not available for general use. If you use XBYTE, you must ensure that you prohibit the tools from using the same addresses for variables! Have you done that? i neither have any idea about "_at_" nor how to use it.
please tell me where i can find information related to it It is, of course, in the compiler Manual - here: http://www.keil.com/support/m...varloc.htm Note that it is specific to Keil. This suggests that you need to spend some time familiarising yourself with the Manual - there may well be other useful features that you are missing...! |
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 |