Searched refs:image (Results 276 – 300 of 966) sorted by relevance
1...<<11121314151617181920>>...39
/Zephyr-latest/tests/drivers/spi/spi_loopback/boards/ |
D | max32662evkit.overlay | 7 /* Increase SRAM2 size to get enough space for image */
|
/Zephyr-latest/samples/bluetooth/cap_acceptor/ |
D | Kconfig.sysbuild | 13 bool "HCI IPC image on network core"
|
D | sysbuild.cmake | 5 # For builds in the nrf5340, we build the netcore image with the controller
|
/Zephyr-latest/samples/bluetooth/cap_initiator/ |
D | Kconfig.sysbuild | 13 bool "HCI IPC image on network core"
|
D | sysbuild.cmake | 5 # For builds in the nrf5340, we build the netcore image with the controller
|
/Zephyr-latest/samples/bluetooth/central_hr/ |
D | Kconfig.sysbuild | 13 bool "HCI IPC image on network core"
|
D | sysbuild.cmake | 5 # For builds in the nrf5340, we build the netcore image with the controller
|
/Zephyr-latest/samples/bluetooth/pbp_public_broadcast_sink/ |
D | Kconfig.sysbuild | 13 bool "HCI IPC image on network core"
|
D | sysbuild.cmake | 5 # For builds in the nrf5340, we build the netcore image with the controller
|
/Zephyr-latest/samples/bluetooth/pbp_public_broadcast_source/ |
D | Kconfig.sysbuild | 13 bool "HCI IPC image on network core"
|
D | sysbuild.cmake | 5 # For builds in the nrf5340, we build the netcore image with the controller
|
/Zephyr-latest/tests/bluetooth/shell/ |
D | Kconfig.sysbuild | 13 bool "HCI IPC image on network core"
|
/Zephyr-latest/samples/bluetooth/peripheral_hr/ |
D | Kconfig.sysbuild | 13 bool "HCI IPC image on network core"
|
D | sysbuild.cmake | 5 # For builds in the nrf5340, we build the netcore image with the controller
|
/Zephyr-latest/tests/subsys/fs/littlefs/boards/ |
D | mimxrt1060_evk_mimxrt1062_qspi.overlay | 18 label = "image-0";
|
/Zephyr-latest/boards/nxp/lpcxpresso55s69/doc/ |
D | index.rst | 112 NS target for CPU0 does not work correctly without a secure image to configure 114 image, run any of the ``tfm_integration`` samples. When using the NS target 115 ``CONFIG_BUILD_WITH_TFM`` is always enabled to ensure that a valid S image is 197 | slot0_ns | 0x00030000[96k] | Second image, core 1 or NS | 199 | slot1 | 0x00048000[160k] | Updates slot0 image | 201 | slot1_ns | 0x00070000[96k] | Updates slot0_ns image | 216 | TFM_S | 0x00008000[160k] | Secure image | 218 | Zephyr_NS | 0x00030000[96k] | Non-Secure image | 339 the resulting image (``tfm_merged.hex``) with a J-Link as follows 349 We need to reset the board manually after flashing the image to run this code. [all …]
|
/Zephyr-latest/boards/nordic/nrf5340dk/doc/ |
D | index.rst | 184 image for the application core. The Secure image can be built using either 190 By default the Secure image for nRF5340 application core is built 197 The process to build the Secure firmware image using TF-M and the Non-Secure 198 firmware image using Zephyr requires the following steps: 207 * Build the Non-Secure firmware image as a regular Zephyr application 208 * Build a TF-M (secure) firmware image 209 * Merge the output image binaries together 210 * Optionally build a bootloader image (MCUboot) 215 required, to adjust the Non-Secure image Flash and SRAM starting address
|
/Zephyr-latest/boards/st/nucleo_h743zi/ |
D | nucleo_h743zi.dts | 250 /* application image slot: 256KB */ 252 label = "image-0"; 258 label = "image-1"; 264 label = "image-scratch";
|
/Zephyr-latest/samples/bluetooth/bap_broadcast_sink/ |
D | sysbuild.cmake | 5 # For builds in the nrf5340, we build the netcore image with the controller
|
/Zephyr-latest/samples/bluetooth/bap_broadcast_source/ |
D | sysbuild.cmake | 5 # For builds in the nrf5340, we build the netcore image with the controller
|
/Zephyr-latest/samples/bluetooth/bap_unicast_client/ |
D | sysbuild.cmake | 5 # For builds in the nrf5340, we build the netcore image with the controller
|
/Zephyr-latest/samples/bluetooth/bap_unicast_server/ |
D | sysbuild.cmake | 5 # For builds in the nrf5340, we build the netcore image with the controller
|
/Zephyr-latest/share/sysbuild/template/ |
D | CMakeLists.txt | 5 # Generic sysbuild CMakeLists.txt file used as sysbuild entry point for multi-image builds.
|
/Zephyr-latest/snippets/nordic-flpr/ |
D | README.rst | 11 FLPR code is to be executed from SRAM, so the FLPR image must be built
|
/Zephyr-latest/boards/seeed/lora_e5_mini/ |
D | lora_e5_mini.dts | 111 label = "image-0"; 115 label = "image-1";
|
1...<<11121314151617181920>>...39