Skip to content

Add and fix size restrictions to targets #121

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 1 commit into from
Mar 26, 2020
Merged

Conversation

esajaa
Copy link
Contributor

@esajaa esajaa commented Mar 20, 2020

Summary of changes

Added size restrictions to several boards, and also fixed some previous ones that were too large or too small.

Used target.restrict_size calculation method:
For 1MB bank: Hex 0x100000 (=Dec 1024 * Dec 1024) - target.app_offset = target.restrict_size
For 512KB bank: Hex 0x080000 (=Dec 512 * Dec 1024) - target.app_offset = target.restrict_size

[x] I confirm this contribution is my own and I agree to license it with Apache 2.0.

[x] I confirm the moderators may change the PR before merging it in.

For new board enablements only:

[] I confirm the board is Mbed Enabled and passes the Mbed Enabled test set.

[] I confirm the contribution has been tested properly and the tests results for TESTS are attached.

[] I confirm mbed-os.lib and mbed-cloud-client.lib hashes or the content in folders mbed-os and mbed-cloud-client were not modified in order to pass the tests.

  • Maintainers of this repository update the Mbed OS and Client hashes.
  • Please report any issues through issues in relevant repositories.

@iot-pdmc
Copy link
Collaborator

Thanks for your changes.
@ARMmbed/pdmc-integrators please review.

@esajaa esajaa requested a review from teetak01 March 20, 2020 09:11
@teetak01
Copy link
Contributor

run-ci

Copy link
Contributor

@teetak01 teetak01 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Look good.

@MarceloSalazar could you get some more reviewers for this?

@MarceloSalazar
Copy link

Thanks - looks good
I've added @maclobdell @toyowata to be aware of this.
I assume the compile test would be sufficient to verify that there are no regressions.

@teetak01
Copy link
Contributor

yes, this is purely compile-time check to verify that the application does not overflow to bank2.

@teetak01
Copy link
Contributor

@esajaa rebase & merge.

Used following target.restrict_size calculation method:
For 1MB bank: Hex 0x100000 (=Dec 1024 * Dec 1024) - target.app_offset = target.restrict_size
For 512KB bank: Hex 0x080000 (=Dec 512 * Dec 1024) - target.app_offset = target.restrict_size
@esajaa esajaa force-pushed the restrict_app_sizes branch from 4675b26 to 2311744 Compare March 26, 2020 09:42
@teetak01
Copy link
Contributor

build-only

@iot-pdmc
Copy link
Collaborator

@teetak01 teetak01 merged commit a8506d2 into master Mar 26, 2020
@teetak01 teetak01 deleted the restrict_app_sizes branch March 26, 2020 12:48
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.

5 participants