Ioannis Glaropoulos 4051f277ef boards: nrf5340: do not attempt to boot NETWORK MCU from Secure image ... Building Zephyr with CONFIG_TRUSTED_EXECUTION_SECURE=y implies building also a Non-Secure image. The Non-Secure image will, in this case do the remainder of actions to properly configure and boot the Network MCU. So the (strictly) secure firmware image does not need to execute the configuration and the booting of the Network MCU, except for the part that does security attribution. In the absence of any TrustZone awareness, the single Application MCU firmware will do all the required steps to configure and boot the Network MCU. Signed-off-by: Ioannis Glaropoulos <Ioannis.Glaropoulos@nordicsemi.no>		2020-07-23 14:07:16 +02:00
..
arc	dts: remove incorrect use of device_type property	2020-07-23 06:37:41 -05:00
arm	boards: nrf5340: do not attempt to boot NETWORK MCU from Secure image	2020-07-23 14:07:16 +02:00
common
nios2
posix
riscv
shields	boards: shields: mikroe_eth_click: add lpcxpresso55s69 support	2020-07-17 11:59:41 -05:00
x86	dts: x86: cleanup memory node	2020-07-23 11:01:16 +02:00
xtensa	boards: intel_s1000_crb: add zephyr,flash-controller to DTS	2020-07-09 14:03:14 -04:00
CMakeLists.txt
deprecated.cmake
index.rst
Kconfig