Please note: We are aware of an issue affecting replies on the Arm Community forums, which may not be loading as expected.

We apologize for any inconvenience and appreciate your patience while we investigate and work to resolve the issue.

Thank you for your understanding.

  • State Suggested Answer
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 348 subscribers
  • Views 3337 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

How to control the Non-Secure MPU exclusively inside the Secure world in the Cortex M33?

Antonio N

Hello,

I am currently working on a project where I need the NonSecure MPU (NS-MPU) to be exclusively controllable by the Secure World. I know it is possible to control the NS-MPU inside the Secure World using an alias address. At the same time, Is there a way to block the Non-Secure World from accessing the NS-MPU controllers?

Parents
  • 0

    Hi, check from your UC documentation if you have some registers to limit access to MPU_CTRL and other in those cases:

    - Unprivileged: In this case, just put your NS application in unprivileged mode
    - In secure mode to lock write access: for example on STM32U5 family you can configure LOCKNSMPU to disable Non-Secure MPU registers access

Reply
  • 0

    Hi, check from your UC documentation if you have some registers to limit access to MPU_CTRL and other in those cases:

    - Unprivileged: In this case, just put your NS application in unprivileged mode
    - In secure mode to lock write access: for example on STM32U5 family you can configure LOCKNSMPU to disable Non-Secure MPU registers access

Children
No data