You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Dual Core example with TrustZone secure and nonsecure application has secure checking disabled in the MCUXpresso Config Tools project file.
Application boots primary core (core0) in the secure state and configures pins, clocks and security parameters via TrustZone, MBC (Memory Block Checker), AHBSC (Secure AHB Controller) etc. from main function by calling BOARD_InitBootTEE.
Secondary core is enabled afterwards and primary core switches to non-secure application that toggles red LED (LED0). The application executing on the secondary core toggles green LED (LED1).
When "Enable Secure Checking" (ENABLE_SECURE_CHECKING bits 3-2) is enabled in MISC_CTRL_REG the application executing on secondary core (core1) is unable to toggle LED (on/off).
The security violation is detected but the root cause is unknown.
Investigate the security violation root cause and update security configuration accordingly.
The text was updated successfully, but these errors were encountered:
The Dual Core example with TrustZone secure and nonsecure application has secure checking disabled in the MCUXpresso Config Tools project file.
Application boots primary core (core0) in the secure state and configures pins, clocks and security parameters via TrustZone, MBC (Memory Block Checker), AHBSC (Secure AHB Controller) etc. from main function by calling BOARD_InitBootTEE.
Secondary core is enabled afterwards and primary core switches to non-secure application that toggles red LED (LED0). The application executing on the secondary core toggles green LED (LED1).
When "Enable Secure Checking" (ENABLE_SECURE_CHECKING bits 3-2) is enabled in MISC_CTRL_REG the application executing on secondary core (core1) is unable to toggle LED (on/off).
The security violation is detected but the root cause is unknown.
Investigate the security violation root cause and update security configuration accordingly.
The text was updated successfully, but these errors were encountered: