https://embeddedsecurity.io/sec-tz-basics
TLDR - "non secure" is a security state of the processor. in that mode, it may have limited access to flash/memory (and in the case of RP2350 DMA channels, peripherals GPIOs, etc.). It is basically a sandbox under the control of the secure software
The RP2350 Arm CPUs at boot are in the secure state and has full access to all the hardware of the system. As such it is similar to RP2040. You explicitly have to launch non-secure software if you want to use it (though as I say the 2.0.0. SDK does not yet support easily writing non-secure software with the SDK to run along side secure software).
Fun fact: The USB/UART boot loader in the bootrom runs in "non-secure" mode to reduce potential attack surfaces.
TLDR - "non secure" is a security state of the processor. in that mode, it may have limited access to flash/memory (and in the case of RP2350 DMA channels, peripherals GPIOs, etc.). It is basically a sandbox under the control of the secure software
The RP2350 Arm CPUs at boot are in the secure state and has full access to all the hardware of the system. As such it is similar to RP2040. You explicitly have to launch non-secure software if you want to use it (though as I say the 2.0.0. SDK does not yet support easily writing non-secure software with the SDK to run along side secure software).
Fun fact: The USB/UART boot loader in the bootrom runs in "non-secure" mode to reduce potential attack surfaces.
Statistics: Posted by kilograham — Tue Sep 03, 2024 12:02 am