• State Accepted Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 1 reply
  • Subscribers 89 subscribers
  • Views 6429 views
  • Users 0 members are here
Options
Related
How was your experience today?
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

At what point in time is the boot security map fixed into the chip?

Ed Player

This question was raised in the 'How to implement a secure IoT system on ARMv8-M' webinar, view all the questions in the round up blog post. 

Parents
  • +1
    If the ARMv8-M implementation decides that the SAU configures all memory as Secure at boot time, which is the case for Cortex-M33 and Cortex-M23, then on reset the SAU_CTRL.ALLNS register is always reset to zero, setting all memory, apart from some specific regions in the PPB space, to Secure state. Setting SAU_CTRL.ALLNS bit to zero prevents an external SAU (Implementation Defined Attribution Unit) overriding any security level. If the ARMv8-M implementation decides that on reset that the SAU_CTRL.ALLNS register is always reset to 1, then it is up to the IDAU to determine the default security settings at reset. This will typically be fixed at the time of manufacturer.
Reply
  • +1
    If the ARMv8-M implementation decides that the SAU configures all memory as Secure at boot time, which is the case for Cortex-M33 and Cortex-M23, then on reset the SAU_CTRL.ALLNS register is always reset to zero, setting all memory, apart from some specific regions in the PPB space, to Secure state. Setting SAU_CTRL.ALLNS bit to zero prevents an external SAU (Implementation Defined Attribution Unit) overriding any security level. If the ARMv8-M implementation decides that on reset that the SAU_CTRL.ALLNS register is always reset to 1, then it is up to the IDAU to determine the default security settings at reset. This will typically be fixed at the time of manufacturer.
Children
No data