??? 06/28/08 04:45 Read: times Msg Score: +1 +1 Good Answer/Helpful |
#156281 - OVERLAYABLE Responding to: ???'s previous message |
Should be the RAM used by the compiler will be reused.
Function A calls Function B Function B returns then A calls Function C. The local variables in Function B and Function C can use the same RAM. This simulates the way a stack based compiler works. Assuming your Absolute addresses are properly handled by the linker. Start with pointers and strings next. You may have a buffer over-run, or are write with an improperly set pointer. In the end you have a code issue and need to debug it. |
Topic | Author | Date |
Strange problem with Keil Compiler | 01/01/70 00:00 | |
Try volatile | 01/01/70 00:00 | |
Probably not the volatile | 01/01/70 00:00 | |
Who can know what is in the mind of the compiler | 01/01/70 00:00 | |
cut out the optimizer (set to 2) and see | 01/01/70 00:00 | |
Assembler Dump | 01/01/70 00:00 | |
well | 01/01/70 00:00 | |
XRAM is enabled | 01/01/70 00:00 | |
the most likel7y reason is that | 01/01/70 00:00 | |
You may want to let the linker know | 01/01/70 00:00 | |
he is using a '124 | 01/01/70 00:00 | |
I know | 01/01/70 00:00 | |
Linker output | 01/01/70 00:00 | |
OVERLAYABLE | 01/01/70 00:00 | |
OVERLAYABLE ?![]() | 01/01/70 00:00 | |
Eh, no debugger for silabs chip? | 01/01/70 00:00 | |
I am using CA51 which dont have debugging | 01/01/70 00:00 | |
it will | 01/01/70 00:00 |