??? 03/21/05 14:06 Read: times |
#90110 - Oleg, why I do similar Responding to: ???'s previous message |
By the way, could you, share us with some examples where you need to control things yourself and where Keil cannot help you, please? Especially I ask for:
I often optimize code for speed/size based on absolute position of variables/arrays, relative position of variables to each other I can not answer that for (I)DATA, but when working with C I very often use an assembler module to define all XDATA variables. Why? Tho locate most frequently addressed XDATA variables in the "internal external" RAM which is accessible at full speed where the "external external" RAM need a strech cycle to meet the timing requirements. When the above made me make the locator module, I later got the idea to locate buffers and such in a way that made them start on nice even addresses easy to remember when debugging. Erik |
Topic | Author | Date |
initializing SP to 7FH | 01/01/70 00:00 | |
why? | 01/01/70 00:00 | |
To Oleg & Russell | 01/01/70 00:00 | |
To Mehdi | 01/01/70 00:00 | |
To Mehdi | 01/01/70 00:00 | |
why not | 01/01/70 00:00 | |
for example, please | 01/01/70 00:00 | |
Oleg, why I do similar | 01/01/70 00:00 | |
here they are | 01/01/70 00:00 | |
well | 01/01/70 00:00 | |
well well | 01/01/70 00:00 | |
well, well - done | 01/01/70 00:00 | |
tight SRAM - use C | 01/01/70 00:00 | |
- or assembler![]() | 01/01/70 00:00 | |
Stack pointer | 01/01/70 00:00 | |
external stack | 01/01/70 00:00 | |
why not? | 01/01/70 00:00 | |
SDCC | 01/01/70 00:00 | |
Re:initializing SP to 7FH | 01/01/70 00:00 | |
very old assemblers only | 01/01/70 00:00 | |
Let the assembler do the work! | 01/01/70 00:00 |