-
Notifications
You must be signed in to change notification settings - Fork 3k
uARM - Move heap region after IRAM1 #10019
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. |
@MarceloSalazar @screamerbg @maclobdell Please review. |
Closing for now since @deepikabhavnani is out until 2nd week of April. |
@ARMmbed/mbed-os-maintainers - Can we please reopen this? |
@deepikabhavnani Done! |
@mmahadevan108 @jeromecoutant @maclobdell - Please review |
ARM_LIB_HEAP start is aligned to IRAM1 end, hence should be placed next to RW_IRAM1 i.e. no other region in between.
b4780a3
to
36c7b2d
Compare
Rebased to re-trigger CI, and pick up latest fixes. |
CI started |
Test run: FAILEDSummary: 6 of 7 test jobs failed Failed test jobs:
|
Restarted jenkins-ci |
Test run: SUCCESSSummary: 11 of 11 test jobs passed |
@ARMmbed/team-nxp Please review |
We would like to proceed with this PR |
Was CI triggered accidentally on this PR again? Not sure why |
@deepikabhavnani Something like that. I think @ARMmbed/mbed-os-test-team are working on CI auto-triggering. The current config doesn't have a way to indicate that a job was aborted. |
Test run: FAILEDSummary: 1 of 7 test jobs failed Failed test jobs:
|
CI restarted |
Test run: SUCCESSSummary: 11 of 11 test jobs passed |
Description
ARM_LIB_HEAP start is aligned to IRAM1 end, hence should be placed next to RW_IRAM1 i.e. no other region in between.
Pull request type