??? 05/20/08 06:22 Read: times |
#154944 - Well maybe.... Responding to: ???'s previous message |
Moving the string constants to CODE space will solve his problem if he can utilize them direct from their storage there. However depending upon the total application there may still need to be an in RAM buffer of the string array. If there is the same 64 byte array it will likely still crash the program when some strcpy() or sprintf() fills the array in to the stack space again.
Michael Karas |
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 |