Skip to content

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

Merged
merged 2 commits into from
Apr 26, 2019

Conversation

deepikabhavnani
Copy link

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:

  1. Fixed size and small sections moved to SRAM2 (32K)
    Vectors
    Crash data
    Stack
    Remaining section - RW / ZI
  2. Large memory space should be used for variable sections
    RW/ZI
    Heap - (Minimum - xxx target based)

Pull request type

[X] Fix
[ ] Refactor
[ ] Target update
[ ] Functionality change
[ ] Docs update
[ ] Test update
[ ] Breaking change

@ciarmcom ciarmcom requested review from screamerbg and a team March 8, 2019 18:00
@ciarmcom
Copy link
Member

ciarmcom commented Mar 8, 2019

@deepikabhavnani, thank you for your changes.
@screamerbg @ARMmbed/mbed-os-maintainers please review.

Copy link
Collaborator

@jeromecoutant jeromecoutant left a 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

@adbridge
Copy link
Contributor

@deepikabhavnani what is the status of this PR? It at least needs a rebase...

@cmonr
Copy link
Contributor

cmonr commented Mar 27, 2019

Closing for now since @deepikabhavnani is out until 2nd week of April.

@cmonr cmonr closed this Mar 27, 2019
@cmonr cmonr removed the needs: work label Mar 27, 2019
@deepikabhavnani
Copy link
Author

@ARMmbed/mbed-os-maintainers - Can we please reopen this?

@cmonr cmonr reopened this Apr 9, 2019
@cmonr
Copy link
Contributor

cmonr commented Apr 9, 2019

@deepikabhavnani Done!

Looks like this needs a rebase.

@deepikabhavnani
Copy link
Author

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
@deepikabhavnani
Copy link
Author

@jeromecoutant - Please review

Copy link
Collaborator

@jeromecoutant jeromecoutant left a 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...

@deepikabhavnani
Copy link
Author

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.

@cmonr
Copy link
Contributor

cmonr commented Apr 12, 2019

CI started

@mbed-ci
Copy link

mbed-ci commented Apr 12, 2019

Test run: FAILED

Summary: 1 of 7 test jobs failed
Build number : 1
Build artifacts

Failed test jobs:

  • jenkins-ci/mbed-os-ci_build-ARM

@0xc0170
Copy link
Contributor

0xc0170 commented Apr 12, 2019

heap and stack overlaps in the build logs - one target failures, please review

@deepikabhavnani
Copy link
Author

heap and stack overlaps in the build logs - one target failures, please review

4b7e163 - shall fix this

@0xc0170
Copy link
Contributor

0xc0170 commented Apr 15, 2019

CI started

@mbed-ci
Copy link

mbed-ci commented Apr 15, 2019

Test run: FAILED

Summary: 1 of 11 test jobs failed
Build number : 2
Build artifacts

Failed test jobs:

  • jenkins-ci/mbed-os-ci_dynamic-memory-usage

@deepikabhavnani
Copy link
Author

Failed test jobs:
jenkins-ci/mbed-os-ci_dynamic-memory-usage

Where can I find log for failing job?

@alekla01
Copy link
Contributor

restarted jenkins-ci/mbed-os-ci_dynamic-memory-usage

@deepikabhavnani
Copy link
Author

continuous-integration/jenkins/pr-head - Looks like same auto-trigger issue

@0xc0170 0xc0170 removed the request for review from screamerbg April 18, 2019 12:35
@0xc0170
Copy link
Contributor

0xc0170 commented Apr 18, 2019

CI restarted

@mbed-ci
Copy link

mbed-ci commented Apr 18, 2019

Test run: SUCCESS

Summary: 11 of 11 test jobs passed
Build number : 5
Build artifacts

@deepikabhavnani
Copy link
Author

@ARMmbed/mbed-os-maintainers : Approved + CI is success

@adbridge
Copy link
Contributor

ci started

@mbed-ci
Copy link

mbed-ci commented Apr 25, 2019

Test run: SUCCESS

Summary: 11 of 11 test jobs passed
Build number : 6
Build artifacts

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants