Searched refs:image (Results 326 – 350 of 966) sorted by relevance
1...<<11121314151617181920>>...39
151 label = "image-0";155 label = "image-1";159 label = "image-scratch";
211 label = "image-0";217 label = "image-1";223 label = "image-scratch";
210 label = "image-0";214 label = "image-1";218 label = "image-scratch";
206 label = "image-0";210 label = "image-1";214 label = "image-scratch";
76 bmaptool copy phytec-qt5demo-image-phyboard-lyra-am62xx-3.wic.xz /dev/sdX111 …x-PD23.2.1/images/ampliphy-xwayland/phyboard-lyra-am62xx-3/phytec-qt5demo-image-phyboard-lyra-am62…114 …x-PD23.2.1/images/ampliphy-xwayland/phyboard-lyra-am62xx-3/phytec-qt5demo-image-phyboard-lyra-am62…
150 label = "image-0";154 label = "image-1";158 label = "image-scratch";
171 label = "image-0";177 label = "image-1";183 label = "image-scratch";
17 to build an application image for a specified board configuration.27 application image30 Each application image contains both the application's code and the33 Once an application image is loaded onto a board, the image takes control43 which can load and execute an application image. It may be an actual59 information that may be required to actually build a Zephyr image for it.78 compile and link an image for a particular hardware system. This string84 A group of one or more :term:`CPU cores <CPU core>`, all executing the same image
110 label = "image-0";185 label = "image-1";189 /* Allocate 128 KiB scratch for image swap */191 label = "image-scratch";
64 # This is needed for QEMU to load the ELF image86 # This is needed for QEMU to load the ELF image
99 label = "image-0";103 label = "image-1";
192 label = "image-0";196 label = "image-1";200 label = "image-scratch";
240 label = "image-0";246 label = "image-1";252 label = "image-scratch";
173 label = "image-0";177 label = "image-1";181 label = "image-scratch";
85 label = "image-0";89 label = "image-1";93 label = "image-scratch";
13 bool "HCI IPC image on network core"
13 # Note: Please use JLINK above V7.50 (Only support run cm4 image when debugging due to default boot…
44 additionally generate a TF-M image for the Secure Execution45 environment, along with the Zephyr image. The Zephyr image48 ensures that the Zephyr image is built as a Non-Secure image. Both68 Build profile used to build tfm_s image. The available values are199 Version of the secure image. This version is also used for merged207 Version of the non-secure image.251 to be embedded in the image trailer. As per "Hardware-based downgrade prevention" in284 When this is 1, the S and NS are considered as 1 image and must be424 hex "ROM Start Offset accounting for BL2 Header in the NS image"454 binary consisting of the TF-M Secure firmware image, optionally, the[all …]
18 .. image:: img/mps2_an521.jpg79 non-secure processing environment. The non-secure Zephyr image is offset to397 firmware image. The Secure image can be built using either Zephyr403 By default the Secure image for the MPS2+ AN521 (CPU0) is built409 The process to build the Secure firmware image using TF-M and the Non-Secure410 firmware image using Zephyr requires the following steps:419 * Build the Non-Secure firmware image as a regular Zephyr application420 * Build a TF-M (secure) firmware image421 * Merge the output image binaries together422 * Optionally build a bootloader image (MCUboot)[all …]
33 #. Copy the Zephyr EFI image :file:`zephyr/zephyr.efi` to the92 Zephyr application image.
36 Use the following procedures for booting an image for an Alder Lake N CRB board.56 A Zephyr EFI image file named :file:`zephyr.efi` is automatically
157 label = "image-0";161 label = "image-1";
146 label = "image-0";150 label = "image-1";
14 Default is to do 1:1 mapping for the kernel image (including code and data)53 * :kconfig:option:`CONFIG_KERNEL_VM_OFFSET`: kernel image starts at this offset81 | image |112 script. This is the virtual address of the beginning of the kernel image at116 script. This is the virtual address of the end of the kernel image at boot time.127 is the end of the kernel image.
188 image for the application core. The Secure image can be built using either199 The process to build the Secure firmware image using TF-M and the Non-Secure200 firmware image using Zephyr requires the following steps:209 * Build the Non-Secure firmware image as a regular Zephyr application210 * Build a TF-M (secure) firmware image211 * Merge the output image binaries together212 * Optionally build a bootloader image (MCUboot)217 required, to adjust the Non-Secure image Flash and SRAM starting address
