| ??? 05/20/08 09:18 Read: times |
#154951 - Glad you have it working Responding to: ???'s previous message |
Most of the newer chips that include this kind of ram have it mapped into the XDATA space. When you say 4.4K RAM, this is how it would be organized.
4K RAM - 0-FFFh in XDATA space 0.4K (256 bytes) in DATA space If you need to keep the array in RAM, you could force it to XDATA same as you did to put it in CODE. XDATA char ........ Christoph is right. The compiler cannot guess how you plan to use your variables. It is just a dumb translator doing what [i]you[/i] tell it to. NINO or GIGO ie : No input, No output or Garbage in, Garbage out Good luck |
| Topic | Author | Date |
| Array size limitation for Keil ? | 01/01/70 00:00 | |
| if you breakpoint | 01/01/70 00:00 | |
| Time to check the assembler output.... | 01/01/70 00:00 | |
| RE: you can not break on the declaration of a vari | 01/01/70 00:00 | |
you can not break on the declaration of a variable | 01/01/70 00:00 | |
| You seem to be declaring constant | 01/01/70 00:00 | |
| It is fully possible.... | 01/01/70 00:00 | |
| idata as stack | 01/01/70 00:00 | |
| Keil compiler limits | 01/01/70 00:00 | |
| I agree - its not a limit | 01/01/70 00:00 | |
| Well maybe.... | 01/01/70 00:00 | |
| 64 or 128 | 01/01/70 00:00 | |
| It was the stack | 01/01/70 00:00 | |
| The compiler cannot really guess .. | 01/01/70 00:00 | |
| Glad you have it working | 01/01/70 00:00 | |
| Map the variables in correct memory area | 01/01/70 00:00 |