-
Notifications
You must be signed in to change notification settings - Fork 3k
Add a platform config to disable the MPU #9040
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
@c1728p9, thank you for your changes. |
CI started (in case it's decided to bring in as-is for RC3) |
platform/mbed_lib.json
Outdated
@@ -128,6 +128,10 @@ | |||
"fatal-error-auto-reboot-enabled": { | |||
"help": "Setting this to true enables auto-reboot on a fatal error.", | |||
"value": false | |||
}, | |||
"disable-mpu": { |
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.
Config options should be positive unless there's a good reason. This could be enable-mpu
, or maybe use-mpu
is more to the point.
This shall be rebased and some comments addressed above, marking it as "needs: work". @kjbracey-arm Do you want to push an update for positive config value? This PR looks minimal and might be considered for rc3? |
Going to rework a little more - as this is a platform option, it should only be affecting platform code. It shouldn't actually be creating dummy HAL calls (and hence requiring custom MPU HALs to follow the config option). |
Add the platform config DISABLE_MPU to allow the MPU to be disabled from an application.
Make the option positively named, and as it is a platform config option make sure it only affects platform code. HAL functions still remain available even if platform is told not to use them.
753c8a2
to
770baa2
Compare
Reworked, and rebased to make the PR clearer. Naming the option "use-mpu" made it clearer how it should be implemented. (ie don't touch the HAL, just don't use it). |
Test run: FAILEDSummary: 1 of 11 test jobs failed Failed test jobs:
|
CI was aborted (timeout anyway) - for older commits, will restart now for the latest update |
CI started |
Test run: FAILEDSummary: 1 of 1 test jobs failed Failed test jobs:
|
Looks like device out of space error! |
CI should be fixed (other fixes ongoing) |
Other fixes ? |
CI team is checking what caused the space to run out (it was now cleaned) CI restarted |
platform/mbed_mpu_mgmt.h
Outdated
@@ -35,6 +35,8 @@ extern "C" { | |||
|
|||
#define mbed_mpu_manager_init() mbed_mpu_init() | |||
|
|||
#define #define mbed_mpu_manager_deinit() mbed_mpu_free() |
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.
Uh-oh.
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.
At least is isn't #undefined behavior. Just kidding, I pushed a fix.
dcf8ce9
to
3e20e7e
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.
Russ's last commit looks good to me.
Test run: SUCCESSSummary: 11 of 11 test jobs passed |
3e20e7e
to
770baa2
Compare
Test run: FAILEDSummary: 6 of 7 test jobs failed Failed test jobs:
|
Ignore #9040 (comment) I accidentally re-enqueued the PR a while back, and forgot to remove it (and force aborted the job above). |
@cmonr - I see Commits after the CI run was triggered, last force push 15 mins ago. |
@deepikabhavnani Correct. There was a third commit in this PR, but CI was started and passed when there were only two commits. We opted to remove the third commit to make this PR green to increase the chance of having RC3 generated before COB UK time. |
Description
Add the platform config DISABLE_MPU to allow the MPU to be disabled from an application.
This PR is identical to #9030 but has an additional commit to add this config.
Pull request type