Remove assert from linker files imx7ulp

[Hadatko]

Signed-off-by: Cervenka Dusan cervenka@acrios.com

Prerequisites

• [X] I have checked latest main branch and the issue still exists.
• [X] I did not see it is stated as known-issue in release notes.
• [X] No similar GitHub issue is related to this change.
• [X] My code follows the commit guidelines of this project.
• [X] I have performed a self-review of my own code.
• [X] My changes generate no new warnings.
• [X] I have added tests that prove my fix is effective or that my feature works.

Describe the pull request

It looks like linker files (maybe also for different targets) contains ASSERT which was copied and paste without checking and evaluating its reason. As data section compared with assert are from different memory sections and between them exists another sections which are not checked and it is throwing error even memory sections are not completely used i think this assert should be removed.

Please check also other linker files if you agree with me

Type of change

• [X] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] This change requires a documentation update

Tests

• Test configuration (please complete the following information):
  • Hardware setting: imx7ulp
  • Toolchain: gcc 11.3 (and gcc10.3)
  • Test Tool preparation:
  • Any other dependencies:
• Test executed Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce.
  • [X] Build Test
  • [X] Run Test

[Hadatko]

Here is picture from compiling code with assert:

[Hadatko]

For example assert for heap and stack make sense to keep as they are located in same memory space (m_data)

[Hadatko]

Matchies:

[mcuxsusan]

Thank you for the notification and appreciate for your patience, already forwarded the issue to internal team for check.

[nxp-wayne]

Hi Hadatko, The assert here is to ensure the built binary can be accommodated into the flash. Otherwise the application cannot boot from flash. Rationale: Both code and data need to be put into flash (region defined by m_text). If the code + data size exceeds the flash size, the assertion will be triggered and it's an expected behavior.

[Hadatko]

Hi @nxp-wayne, i understand your point. But shouldn't linker itself throw error if m_text would overflow?

[Hadatko]

Hi @nxp-wayne just thinking: If we will do bellow change, we will get linker error. So the result is same without assert. Am i right?

[Hadatko]

I will close this PR as it showed up ASSERT is really needed. Thank you.