We have run out of memory in our KL03 16K based project. But, interestingly, one of us has managed to squeeze out more memory by re-arranging flash memory allocation in the IAR / NXP KL03 memory configuration files!
Wow! But, how safe is this??
To put it another way, (I can not believe) if this is "ok to do", that IAR / NXP simply hasn't done this for all KL03 projects already?
Here's the before:
"A1": place at 0x00000000 { ro section .intvec }; "P1": place in [from 0x00000400 to 0x0000040f] { section FlashConfig }; "P2": place in [from 0x00000000 to 0x000000ff] | [from 0x00000410 to 0x00003fff] { ro }; "P3": place in [from 0x1ffffe00 to 0x200004ff] { block RW }; "P4": place in [from 0x1ffffe00 to 0x200004ff] { block ZI }; "P6": place in [from 0x20000500 to 0x200005ff] { block CSTACK };
And here's the after:
"A1": place at 0x00000000 { ro section .intvec };
"P1": place in [from 0x00000400 to 0x0000040f] { section FlashConfig };
"P2": place in [from 0x00000000 to 0x000000ff] |
[from 0x00000100 to 0x000003ff] |
[from 0x00000410 to 0x00003fff] { ro };
"P3": place in [from 0x1ffffe00 to 0x200004ff] { block RW };
"P4": place in [from 0x1ffffe00 to 0x200004ff] { block ZI };
"P6": place in [from 0x20000500 to 0x200005ff] { block CSTACK };
...poof! Another 767bytes of memory. The project now compiles and executes on our target. However, we haven't had time to do any extensive testing.
I checked with Kinetis L family product team, customer doesn't need to allocate 0x400 flash memory range for vector table. In fact, the Flash range 0x100 to 0x3ff can be used for customer usage. That kind of application is safe.
Wish it helps.
Have a great day, Ma Hui
----------------------------------------------------------------------------------------------------------------------- Note: If this post answers your question, please click the Correct Answer button. Thank you! -----------------------------------------------------------------------------------------------------------------------
