Searched full:nonsecure (Results 1 – 25 of 27) sorted by relevance
12
/Zephyr-latest/dts/bindings/misc/ |
D | nordic,split-channel-groups.yaml | 13 nonsecure-channel-groups: 17 that are to be configured as nonsecure. In Trustzone systems, this 18 property is only evaluated for secure peripherals, as nonsecure channels
|
D | nordic,split-channels.yaml | 30 nonsecure-channels: 34 are to be configured as nonsecure. In Trustzone systems, this property 35 is only evaluated for secure peripherals, as nonsecure channels are
|
/Zephyr-latest/dts/arm/nordic/ |
D | nrf9280_cpurad.dtsi | 55 nonsecure-channels = <8 9 10 11 12>; 64 nonsecure-channels = <0>; 71 nonsecure-channels = <0>;
|
D | nrf54h20_cpurad.dtsi | 62 nonsecure-channels = <8 9 10 11 12>; 72 nonsecure-channels = <0 2 3>; 80 nonsecure-channels = <0 2 3>;
|
/Zephyr-latest/boards/nordic/nrf54l15dk/ |
D | nrf54l15dk_nrf54l15_cpuapp.dts | 36 label = "image-0-nonsecure"; 44 label = "image-1-nonsecure";
|
D | nrf54l15dk_nrf54l05_cpuapp.dts | 47 label = "image-0-nonsecure"; 55 label = "image-1-nonsecure";
|
D | nrf54l15dk_nrf54l10_cpuapp.dts | 47 label = "image-0-nonsecure"; 55 label = "image-1-nonsecure";
|
/Zephyr-latest/boards/arm/v2m_musca_b1/ |
D | v2m_musca_b1_musca_b1_ns.yaml | 2 name: ARM V2M MUSCA B1 NonSecure
|
/Zephyr-latest/boards/arm/v2m_musca_s1/ |
D | v2m_musca_s1_musca_s1_ns.yaml | 2 name: ARM V2M MUSCA-S1 NonSecure
|
/Zephyr-latest/boards/st/b_u585i_iot02a/ |
D | b_u585i_iot02a_stm32u585xx_ns.dts | 54 label = "image-0-nonsecure"; 64 label = "image-1-nonsecure";
|
/Zephyr-latest/boards/st/nucleo_l552ze_q/ |
D | nucleo_l552ze_q_stm32l552xx_ns.dts | 57 label = "image-0-nonsecure"; 67 label = "image-1-nonsecure";
|
/Zephyr-latest/tests/drivers/flash/common/boards/ |
D | b_u585i_iot02a_stm32u585xx_ns.overlay | 17 label = "image-0-nonsecure";
|
/Zephyr-latest/boards/nordic/nrf54l20pdk/ |
D | nrf54l20_cpuapp_common.dtsi | 61 label = "image-0-nonsecure"; 69 label = "image-1-nonsecure";
|
/Zephyr-latest/dts/common/nordic/ |
D | nrf5340_cpuapp_partition.dtsi | 41 label = "image-0-nonsecure"; 49 label = "image-1-nonsecure";
|
D | nrf91xx_partition.dtsi | 41 label = "image-0-nonsecure"; 49 label = "image-1-nonsecure";
|
/Zephyr-latest/tests/arch/arm/arm_tz_wrap_func/src/ |
D | README.txt | 4 __TZ_WRAP_FUNC() is part of the nonsecure TrustZone API, but is itself 6 of secure/nonsecure firmware.
|
/Zephyr-latest/arch/arm/include/cortex_m/ |
D | tz_ns.h | 9 * @brief TrustZone API for use in nonsecure firmware 12 * The following API can be used by the nonsecure firmware to interact with the
|
/Zephyr-latest/tests/arch/arm/arm_thread_swap_tz/src/ |
D | main.c | 45 /* Check that the main thread was executing in nonsecure mode. */ in work_func() 47 "EXC_RETURN not nonsecure: 0x%x\n", main_thread->arch.mode_exc_return); in work_func()
|
/Zephyr-latest/modules/trusted-firmware-m/ |
D | CMakeLists.txt | 333 # Note that the Nonsecure FW is replaced by the Zephyr app in regular Zephyr 339 TFM_NS_BIN_FILE ${TFM_NS_BIN_FILE} # TFM Nonsecure FW (unsigned) 340 TFM_NS_HEX_FILE ${TFM_NS_HEX_FILE} # TFM Nonsecure FW (unsigned) 342 TFM_NS_SIGNED_BIN_FILE ${TFM_NS_SIGNED_BIN_FILE} # TFM Nonsecure FW (signed) 343 TFM_S_NS_SIGNED_BIN_FILE ${TFM_S_NS_SIGNED_BIN_FILE} # Merged TFM Secure/Nonsecure FW (signed)
|
/Zephyr-latest/boards/nxp/lpcxpresso55s69/ |
D | lpcxpresso55s69.dtsi | 129 label = "image-0-nonsecure"; 137 label = "image-1-nonsecure";
|
/Zephyr-latest/boards/ezurio/bl5340_dvk/ |
D | bl5340_dvk_nrf5340_cpuapp_common.dtsi | 337 label = "image-0-nonsecure"; 368 label = "image-1-nonsecure";
|
/Zephyr-latest/boards/nordic/nrf54h20dk/ |
D | nrf54h20dk_nrf54h20_cpuapp.dts | 227 nonsecure-channels = <5 6>;
|
/Zephyr-latest/boards/nordic/nrf9280pdk/ |
D | nrf9280pdk_nrf9280_cpuapp.dts | 221 nonsecure-channels = <5 6>;
|
/Zephyr-latest/samples/tfm_integration/tfm_ipc/ |
D | README.rst | 24 The sys_reboot call is routed to TF-M, since the nonsecure app is not allowed
|
/Zephyr-latest/doc/services/logging/ |
D | index.rst | 523 of the binaries (Secure or Nonsecure) on an ARM TrustZone core. 563 each core has both a Secure and a Nonsecure domain. If *core A nonsecure* (A_NS) is the 565 *core B nonsecure* (A_NS-B_NS). *B_NS* domain has one link, to *core B secure*
|
12