??? 02/27/07 20:26 Read: times |
#133879 - it is, and thus it takes many reads Responding to: ???'s previous message |
i have refferd the keil manual also but i am finding it a bit difficult to follow.
it is, and thus it takes many reads to get used to finding what you need. I recall my first several 'lookings' what a pain in the butt, but after a while I learned how to find things. Anyhow, that you did not know IDATA indicated that you had not bothered work through the 'getting started guide', just reading it is 97% worthless. Erik |
Topic | Author | Date |
using 256 bytes of ram 0f 8052 in keil | 01/01/70 00:00 | |
you can't, the most you can get is 248 (256 - one | 01/01/70 00:00 | |
Keil internal ram | 01/01/70 00:00 | |
resons for extending memory | 01/01/70 00:00 | |
it is, and thus it takes many reads | 01/01/70 00:00 | |
lookup | 01/01/70 00:00 | |
not necessarily correct | 01/01/70 00:00 | |
There is limit | 01/01/70 00:00 | |
Try it if you think its wrong :) | 01/01/70 00:00 | |
wht a bunch of gobbelygook! | 01/01/70 00:00 | |
Qualifers | 01/01/70 00:00 | |
Sloppy | 01/01/70 00:00 | |
Maybe | 01/01/70 00:00 | |
problem solved | 01/01/70 00:00 | |
You Must Read | 01/01/70 00:00 | |
RTFMs![]() | 01/01/70 00:00 | |
What??? | 01/01/70 00:00 | |
The solution could be as simple as: | 01/01/70 00:00 | |
just note about size | 01/01/70 00:00 |