| ??? 02/28/07 01:36 Read: times Msg Score: +1 +1 Informative |
#133903 - Sloppy Responding to: ???'s previous message |
Neil Kurzman said:
move constants to code to save space in RAM Careful... The 8051 knows only address spaces - for the external address spaces, it doesn't know whether you have RAM or ROM mapped into them. int aVariable; // RAM Not necessarily true: depending on the Memory Model, the variable could be in PDATA or XDATA space - and these are not necessarily RAM. code int aVariable; // ROM Although CODE space most commonly contains ROM, this is not necessarily the case... If you over run the stack it over writes the varables. Bad things happen. Worse, if you corrupt the stack, function return addresses get trashed - and really bad things can happen! In particular, note that a NULL Generic Pointer points to IDATA... |
| 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 |