Lines Matching refs:secure

1 README on how boot images are created for secure TI devices
7 a secure device from TI, the initial public software image must be signed
11 from Texas Instruments. The tools used to generate boot images for secure
12 devices are part of a secure development package (SECDEV) that can be
17 The secure development package is access controlled due to NDA and export
31 	warning is issued during the build to indicate that a final secure
38 	This is called as part of the SPL/u-boot build process. As the secure
39 	boot image formats and requirements differ between secure SOC from TI,
44 	package for creating a bootable SPL image for secure TI devices.
65 	<OUTPUT_FILE> is the full path and filename of the final secure
67 	non-secure binary images (see the platform-specific user's guides and
68 	releases notes for how the non-secure images are typically used)
97 	<OUTPUT_FILE> is the full path and filename of the final secure
99 	non-secure binary images (see the platform-specific user's guides and
100 	releases notes for how the non-secure images are typically used)
124 	<OUTPUT_FILE> is the full path and filename of the final secure image.
126 	non-secure binary images (see the platform-specific user's guides
127 	and releases notes for how the non-secure images are typically used)
132 		non-secure devices)
148 	<OUTPUT_FILE> is the full path and filename of the final secure image.
150 	non-secure binary images (see the platform-specific user's guides
151 	and releases notes for how the non-secure images are typically used)
160 	which is the main u-boot image. For secure TI devices, the SPL will
162 	device's ROM boot process. In order to continue the secure boot
166 	The configurations for secure TI platforms are written to make the boot
171 	process. In order to secure these components so that they can be
173 	build procedure for secure TI devices will secure these images before
176 	they are still secure. The outlined security-related SPL post-processing
178 	must be enabled for the secure boot scheme to work. In order to allow
179 	verifying proper operation of the secure boot chain in case of successful
189 	${TI_SECURE_DEV_PKG}/scripts/secure-binary-image.sh
191 	This is called as part of the u-boot build process. As the secure
192 	image formats and requirements can differ between the various secure
195 	TI SECDEV package for creating a u-boot.img image for secure TI
198 	The SPL/u-boot code contains calls to dedicated secure ROM functions
201 	is that they are accessed by invoking an ARM secure monitor call to
202 	the device's secure ROM (fixed read-only-memory that is secure and
203 	only accessible when the ARM core is operating in the secure mode).
205 	Invoking the secure-binary-image script for Secure Devices
208 	secure-binary-image.sh <INPUT_FILE> <OUTPUT_FILE>
212 	<OUTPUT_FILE> is the full path and filename of the output secure image.