region "m_text" overflowed ____ bytes

[syed_idris]

Hi,

we are working on Kinetis KL03 processor with KDS 3.1.0 in Processor Expert.

Wen we are printing float value in simple code it is executing properly using Processor Expert,

but some codes are giving errors like,

>> region "m_text" overflowed 1896 bytes

and also some other errors as in screenshot,

Is this related to (flash) memory overflow?

Do we need to change the memory size & how to resolve this error?

[syed_idris]

DavidS​ I followed steps as you gave, but still we are getting error.

[DavidS]

Hi Syed,

Can you post your project?

Regards,

David

[syed_idris]

Hi DavidS​,

Thanks for your help but without director's permission I can't post our project.

We moved some little bit ahead & able to build the project, but its not working.

details are as follows,

previously m_text size was 0x00007BF0 and it was giving the error that m_text overflowed by 6952 bytes,

After incrementing 6952 bytes and making m_text size of 0x00009718 ,it was giving error that overflowed by 0 bytes & some more errors also

After incrementing some random bytes and making m_text size as 0x000097C8, Project built successfully without any error & .elf file is also generated,

but while debugging (Run/F8) the project is not working, giving warning as below

Instead of using Run(F8) if Step in (F5) is used then pointer is only pointing to these two lines only continuously,

project is building successfully but not working:smileyplain:

hope you will guide us.

Syed_Idris

[DavidS]

Hi Syed,

I can only guess at issues when cannot see project.  Hope you understand.

Once in debugger, please remove/delete all breakpoints. Exit and re-start debug session.  Those warnings should be gone now.

Something is trigger an ISR or exception.

Do you have watchdog disabled?  If not this can be a cause of interrupt.

Do you have NMI pin enabled?  If yes and the pin is low, it can cause interrupt.  Solution is to not enable NMI or to add pull-up (4-10Kohm) to the NMI pin.

Hope this helps.

Regards,

David

[syed_idris]

Hi DavidS​,

Sorry for late.

I am sending the basic code to you which is giving errors as I mentioned above, hope you will give some idea,

It will be better if you give me step by step procedure what you are doing to eliminate these errors,

If you make video to let me understand how can I also remove these errors, it will be best for me,

Thanks,

Syed_Idris

[DavidS]

Hi Syed,

After looking at your project I have concluded that the KL03 using KSDK_1.3+PE is not efficient enough for low memory device like KL03 when the code base is also implementing PRINTF with floating point, software is using floats and floating point math, etc...and PE's overhead.

I recommend using an existing none PE example as a starting point and/or use a device with more memory.

Example none PE projects:

C:\Freescale\KSDK_1.3.0\examples\frdmkl03z\demo_apps\adc_hw_trigger\lptmr\kds

C:\Freescale\KSDK_1.3.0\examples\frdmkl03z\demo_apps\rtc_func\kds

Regards,

David

[ZhangJennie]

Hi,

from the error message, the problem is because of  the code size in .text is too big to fit in m_text section.

please check both of your linker of and map file, make sure if there is enough space in m_text for your code?

Have a great day,
Jennie Zhang

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

[syed_idris]

Thanks for your reply,

We are new to kinetis processor so can you please help us to know that how can we check 'linker file' and 'map file' & if there is no space in m_text section for our code then how to manage or increase the m_text size ?

[ZhangJennie]

Hi,

first, please check m_text definition in ld file with user manual memory map, if m_text covers all the valid flash memory..

check map file, map records how the function size relocation address in memory.  if the functions code size is too big to hold in m_text. i am afraid you need move to a bigger size chip.

or , you can post your project here, we can help you confirm it.

Have a great day,
Jennie Zhang

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

[syed_idris]

I didn't understand,

first, please check m_text definition in ld file with user manual memory map,

will you please give step by step procedure where I can check "m_text" size?

[ZhangJennie]

Hi,

you can check m_text in *.ld file:

in above screenshot, m_text is from 0x000410 to 0x01FBF0, which is used for allocating code.

please check your particular chip user manual, if m_text size is big enough.

if you still can't figure it out by yourself, please post your project here/ or at least post your *.ld file here with your target part number. I can check it for you.

Have a great day,
Jennie Zhang

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

[syed_idris]

OK but where is *.ld file located ?

if you give the location of *.ld file then will we be able to increase the m_text size only by just editing in that file ?

or we have to do something else for that ?