??? 02/28/07 19:36 Read: times |
#133962 - The solution could be as simple as: Responding to: ???'s previous message |
After reading this guys posts, and navigating through all of the local conversations amongst those who know, about those who don't know in this thread, it occurred to me we may have missed the most obvious answer here.
Pradheep states he doesn't seem to be able to access the upper 128 bytes of internal RAM in his processor, due to the complier telling him he's out of space at 128, but he thinks his chip has more... Maybe his first line in his startup assembly code reads something like: IDATALEN EQU 80H and maybe it should read something like: IDATALEN EQU 100H or maybe he's declaring his variables (because the default value for SMALL model is DATA) all in the DATA space, and he could easily add a simple qualifier to a few of them like: before: unsigned int myvar = 0x0505; after: unsigned int idata myvar = 0x0505; just thinking... |
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 |