| ??? 05/20/08 06:13 Modified: 05/20/08 06:17 Read: times |
#154942 - I agree - its not a limit Responding to: ???'s previous message |
Andy, I agree with you - there is no limit to the array size - certainly not imposed by the compiler. Maybe I didnt convey what I meant clearly.
If you see, I presume, he is using the small memory model for compilation and all variables go to the data space. He is able to load the first array into data space. The second array, if greater than 2 bytes long, tends to destroy his PC(He said - it loops on array 1 declaration). Perhaps this is a signal that the array is disturbing the stack ??? So, I stand by my suggestion for him to be explicit and declare the arrays in code space. This will solve his problem. Edit : Michael-Your statement too is totally true. I saw you message after posting this. Initialization of RAM based variables is taken care of by the compiler. But... see above. What about the RAM space needed. He is trying to declare 2 arrays worth 128 bytes which dont work. Only 64 bytes in all seem to work for him. |
| 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 |