Difference between revisions of "J-Link ARMv8-M"

From SEGGER Wiki
Jump to: navigation, search
(TrustZone)
(Non-secure debug access)
Line 5: Line 5:
 
=== Secure debug access===
 
=== Secure debug access===
 
=== Non-secure debug access===
 
=== Non-secure debug access===
#The reset functionality (via SYSRESETREQ) can be disabled for non-secure mode using the AIRCR.SYSRESETREQS bit. Unfortunately, the debugger cannot read the SYSRESETREQS bit in non-secure mode thus cannot determine if reset functionality is available or not. The only possibility to determine if it's available or not is to issue a reset via AIRCR.SYSRESETREQ and to check if DHCSR.S_RESET_ST gets set afterwards. If not, reset is not available in the current configuration.
+
*The reset functionality (via SYSRESETREQ) can be disabled for non-secure mode using the AIRCR.SYSRESETREQS bit. Unfortunately, the debugger cannot read the SYSRESETREQS bit in non-secure mode thus cannot determine if reset functionality is available or not. The only possibility to determine if it's available or not is to issue a reset via AIRCR.SYSRESETREQ and to check if DHCSR.S_RESET_ST gets set afterwards. If not, reset is not available in the current configuration.

Revision as of 10:50, 8 May 2024

This article describes the debugging specifics for devices based on the ARMv8-M architecture.

TrustZone

Secure debug access

Non-secure debug access

  • The reset functionality (via SYSRESETREQ) can be disabled for non-secure mode using the AIRCR.SYSRESETREQS bit. Unfortunately, the debugger cannot read the SYSRESETREQS bit in non-secure mode thus cannot determine if reset functionality is available or not. The only possibility to determine if it's available or not is to issue a reset via AIRCR.SYSRESETREQ and to check if DHCSR.S_RESET_ST gets set afterwards. If not, reset is not available in the current configuration.