Lines Matching full:image
4 Secure TI devices require a boot image that is authenticated by ROM
6 device is essentially useless. In order to create a valid boot image for
7 a secure device from TI, the initial public software image must be signed
10 Information on the details on the complete boot image format can be obtained
27 viable boot image. The build process will look for the environment
32 bootable image was not created.
34 Within the SECDEV package exists an image creation script:
36 ${TI_SECURE_DEV_PKG}/scripts/create-boot-image.sh
39 boot image formats and requirements differ between secure SOC from TI,
44 package for creating a bootable SPL image for secure TI devices.
49 create-boot-image.sh \
52 <IMAGE_FLAG> is a value that specifies the type of the image to
53 generate OR the action the image generation tool will take. Valid
55 SPI_X-LOADER - Generates an image for SPI flash (byte swapped)
56 X-LOADER - Generates an image for non-XIP flash
57 MLO - Generates an image for SD/MMC/eMMC media
58 2ND - Generates an image for USB, UART and Ethernet
66 image. The output binary images should be used in place of the standard
69 u-boot-spl_HS_SPI_X-LOADER - byte swapped boot image for SPI flash
70 u-boot-spl_HS_X-LOADER - boot image for NAND or SD/MMC/eMMC rawmode
71 u-boot-spl_HS_MLO - boot image for SD/MMC/eMMC media
72 u-boot-spl_HS_2ND - boot image for USB, UART and Ethernet
73 u-boot_HS_XIP_X-LOADER - boot image for NOR or QSPI Xip flash
81 create-boot-image.sh \
84 <IMAGE_FLAG> is a value that specifies the type of the image to
85 generate OR the action the image generation tool will take. Valid
87 SPI_X-LOADER - Generates an image for SPI flash (byte
91 ISSW - Generates an image for all other boot modes
98 image. The output binary images should be used in place of the standard
101 u-boot-spl_HS_SPI_X-LOADER - byte swapped boot image for SPI flash
102 u-boot_HS_XIP_X-LOADER - boot image for NOR or QSPI flash
103 u-boot-spl_HS_ISSW - boot image for all other boot media
111 create-boot-image.sh \
114 <IMAGE_TYPE> is a value that specifies the type of the image to
115 generate OR the action the image generation tool will take. Valid
117 X-LOADER - Generates an image for NOR or QSPI boot modes
118 MLO - Generates an image for SD/MMC/eMMC boot modes
119 ULO - Generates an image for USB/UART peripheral boot modes
124 <OUTPUT_FILE> is the full path and filename of the final secure image.
128 u-boot-spl_HS_MLO - boot image for SD/MMC/eMMC. This image is
133 u-boot-spl_HS_ULO - boot image for USB/UART peripheral boot modes
134 u-boot-spl_HS_X-LOADER - boot image for all other flash memories
143 create-boot-image.sh \
152 <OUTPUT_FILE> is the full path and filename of the final secure image.
156 u-boot_HS_MLO - signed and encrypted boot image that can be used to
163 The SPL image is responsible for loading the next stage boot loader,
164 which is the main u-boot image. For secure TI devices, the SPL will
168 image that it loads.
171 process use the FIT image format for the u-boot.img (CONFIG_SPL_FRAMEWORK
173 components that the SPL loads include a specific DTB image and u-boot
174 image. These DTB image may be one of many available to the boot
176 authenticated by the SPL as they are loaded from the FIT image, the
178 they are integrated into the FIT image. When those images are extracted
179 from the FIT image at boot time, they are post-processed to verify that
186 FIT image. Note that the last part of this log message is the (truncated)
191 an input binary image:
193 ${TI_SECURE_DEV_PKG}/scripts/secure-binary-image.sh
196 image formats and requirements can differ between the various secure
199 TI SECDEV package for creating a u-boot.img image for secure TI
209 Invoking the secure-binary-image script for Secure Devices
212 secure-binary-image.sh <INPUT_FILE> <OUTPUT_FILE>
214 <INPUT_FILE> is the full path and filename of the input binary image
216 <OUTPUT_FILE> is the full path and filename of the output secure image.