-
Notifications
You must be signed in to change notification settings - Fork 2.2k
[Silabs] 917SoC Linker file fix #39807
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Silabs] 917SoC Linker file fix #39807
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request updates the linker script for the Silabs 917 SoC, likely to align with a new SDK version. The changes involve memory region adjustments, modifications to section placements, and an updated data initialization approach. My review found a critical typo in the .eh_frame
section name which could lead to runtime failures. I have provided a suggestion to correct it.
In the PR description, |
PR #39807: Size comparison from 9151e79 to e7d0627 Increases above 0.2%:
Full report (71 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, cyw30739, efr32, esp32, linux, nrfconnect, nxp, psoc6, qpg, stm32, telink, tizen)
|
Provide more details on what was tested/how it was tested |
Ohh okay, updated the testing part. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rubber stamping as I don't have context on the specific SoC.
Next time please add a better description explaining the "why" of the changes (moved memory regions because...?
PR #39807: Size comparison from dda2252 to 6cbb740 Increases above 0.2%:
Full report (71 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, cyw30739, efr32, esp32, linux, nrfconnect, nxp, psoc6, qpg, stm32, telink, tizen)
|
Summary
917 SoC linker file was reverted in the PR #39562
Fixed the linker file with the latest sdk
The issue was the file excluded and included were in incorrect format
*filename.o which is used in the extension
*filename.c.o used in the ninja build system
Testing
Tested locally with 917 SoC Commissioning and commands.
Reverted the PR, just to confirm it fails with v3.5.0, it fails with the same error.