-
Notifications
You must be signed in to change notification settings - Fork 3k
STM: Update linker script for using SRAM1 and SRAM2 in ARM #10018
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
Conversation
@deepikabhavnani, thank you for your changes. |
897a7d2
to
ace2397
Compare
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.
Few questions.
But as a general question, not easy to approve a specific PR for 2 targets and 1 toolchain only
@LMESTM
targets/TARGET_STM/TARGET_STM32L4/TARGET_STM32L443xC/device/TOOLCHAIN_ARM_STD/stm32l443xx.sct
Show resolved
Hide resolved
@deepikabhavnani what is the status of this PR? It at least needs a rebase... |
Closing for now since @deepikabhavnani is out until 2nd week of April. |
@ARMmbed/mbed-os-maintainers - Can we please reopen this? |
@deepikabhavnani Done! Looks like this needs a rebase. |
ace2397
to
d5c3fc5
Compare
Rebased to resolve conflicts |
To have the flexibilty in application; to use any of the section (data/bss/heap) without updating linker script in every use case, following decisions are made: 1. Fixed size and small sections moved to SRAM2 (32K) Vectors Crash data Remaining section - RW / ZI 2. Large memory space should be used for variable sections RW/ZI Heap - (Minimum - 0x12000) Stack - At bottom
d5c3fc5
to
feba293
Compare
@jeromecoutant - Please review |
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.
I could approve, but who takes the action to align all scatter files of all targets...
Aligning all scatter files for devices supporting multiple RAM bank is the query I suppose? Existing linker scripts work and are aligned to Mbed OS memory map but both RAM banks were not utilized. Linker scripts for Pelion platform/applications in need of more RAM were requested hence updating the ones in need now. Rest shall be updated as part of Pelion porting, or can also add issue in Mbed OS to keep track. |
CI started |
Test run: FAILEDSummary: 1 of 7 test jobs failed Failed test jobs:
|
heap and stack overlaps in the build logs - one target failures, please review |
4b7e163 - shall fix this |
CI started |
Test run: FAILEDSummary: 1 of 11 test jobs failed Failed test jobs:
|
Where can I find log for failing job? |
restarted jenkins-ci/mbed-os-ci_dynamic-memory-usage |
|
CI restarted |
Test run: SUCCESSSummary: 11 of 11 test jobs passed |
@ARMmbed/mbed-os-maintainers : Approved + CI is success |
ci started |
Test run: SUCCESSSummary: 11 of 11 test jobs passed |
Description
To have the flexibilty in application; to use any of the section (data/bss/heap) without updating linker script in every use case, following decisions are made:
Vectors
Crash data
Stack
Remaining section - RW / ZI
RW/ZI
Heap - (Minimum - xxx target based)
Pull request type