• State Accepted Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 1 reply
  • Subscribers 88 subscribers
  • Views 6274 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

What sort of visibility does a non-secure debugger have of the secure sections?

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
    An ARMv8-M Processing Element such as Cortex-M33 or Cortex-M23 that implements the ARMv8-M Security Extension may or may not have Secure Debug enabled or disabled. There is a configuration option for the microcontroller vendor that determines whether a debugger is allowed to perform secure and non-secure accesses or only non-secure accesses. If the MCU is configured to only support non-secure debug, it will not have access to the secure memory and registers. Similarly there is a configuration option for the microcontroller vendor that determines whether a debugger is permitted to perform secure and non-secure trace, for example, ETM trace, or only non-secure trace. If the MCU only includes non-secure trace, then again, the debugger will only be able to capture trace when it is executing non-secure code.
Reply
  • +1
    An ARMv8-M Processing Element such as Cortex-M33 or Cortex-M23 that implements the ARMv8-M Security Extension may or may not have Secure Debug enabled or disabled. There is a configuration option for the microcontroller vendor that determines whether a debugger is allowed to perform secure and non-secure accesses or only non-secure accesses. If the MCU is configured to only support non-secure debug, it will not have access to the secure memory and registers. Similarly there is a configuration option for the microcontroller vendor that determines whether a debugger is permitted to perform secure and non-secure trace, for example, ETM trace, or only non-secure trace. If the MCU only includes non-secure trace, then again, the debugger will only be able to capture trace when it is executing non-secure code.
Children
No data