Other Parts Discussed in Thread: LAUNCHXL-F28069M
Hi,
my customer find that sometimes the sections will not occupy flash memory consecutively.
In the picture below, the left side shows that there will be a hole between .cinit(ended at 003dfe52) and .econst(start at 00edfe54).
While the right side doesn't have such problem.
They met this problem by adding "switch case" functions in their code and there are many cases in one function.
For example,
"switch a,
case1, case2, case..., case N." N>10.
And they find that the code could not run correctly if .cinit section and .econst section occupy flash memory not consecutively.
We've no idea why it could happen.