Home
last modified time | relevance | path

Searched refs:image (Results 1 – 25 of 111) sorted by relevance

12345

/trusted-firmware-a-latest/fdts/
Dcot_descriptors.dtsi17 image-id =<TRUSTED_BOOT_FW_CERT_ID>;
36 image-id = <TRUSTED_KEY_CERT_ID>;
48 image-id = <SCP_FW_KEY_CERT_ID>;
59 image-id = <SCP_FW_CONTENT_CERT_ID>;
70 image-id = <SOC_FW_KEY_CERT_ID>;
80 image-id = <SOC_FW_CONTENT_CERT_ID>;
94 image-id = <TRUSTED_OS_FW_KEY_CERT_ID>;
105 image-id = <TRUSTED_OS_FW_CONTENT_CERT_ID>;
125 image-id = <NON_TRUSTED_FW_KEY_CERT_ID>;
136 image-id = <NON_TRUSTED_FW_CONTENT_CERT_ID>;
[all …]
Dstm32mp1-cot-descriptors.dtsi17 image-id = <STM32MP_CONFIG_CERT_ID>;
31 image-id = <TRUSTED_KEY_CERT_ID>;
43 image-id = <TRUSTED_OS_FW_KEY_CERT_ID>;
54 image-id = <TRUSTED_OS_FW_CONTENT_CERT_ID>;
74 image-id = <NON_TRUSTED_FW_KEY_CERT_ID>;
85 image-id = <NON_TRUSTED_FW_CONTENT_CERT_ID>;
100 image-id = <HW_CONFIG_ID>;
106 image-id = <FW_CONFIG_ID>;
112 image-id = <BL32_IMAGE_ID>;
118 image-id = <BL32_EXTRA1_IMAGE_ID>;
[all …]
/trusted-firmware-a-latest/tools/fiptool/
Dfiptool.c175 if (desc->image) { in free_image_desc()
176 free(desc->image->buffer); in free_image_desc()
177 free(desc->image); in free_image_desc()
342 image_t *image; in parse_fip() local
355 image = xzalloc(sizeof(*image), in parse_fip()
357 image->toc_e = *toc_entry; in parse_fip()
358 image->buffer = xmalloc(toc_entry->size, in parse_fip()
368 memcpy(image->buffer, buf + toc_entry->offset_address, in parse_fip()
386 assert(desc->image == NULL); in parse_fip()
387 desc->image = image; in parse_fip()
[all …]
Dfiptool.h39 struct image *image; member
43 typedef struct image { struct
/trusted-firmware-a-latest/docs/design/
Dauth-framework.rst10 particular image/certificate.
75 a root of trust and culminates in a single data image. The following diagram
76 illustrates how this maps to a CoT for the BL31 image described in the
126 authentication image contains information to authenticate a data image or
127 another authentication image. A data image is usually a boot loader binary, but
133 For every image in a Chain of Trust, the following high level operations are
136 #. Allocate memory for the image either statically or at runtime.
138 #. Identify the image and load it in the allocated memory.
140 #. Check the integrity of the image as per its type.
142 #. Authenticate the image as per the cryptographic algorithms used.
[all …]
Dtrusted-board-boot.rst26 - The BL1 image, on the assumption that it resides in ROM so cannot be
43 image. An image can be authenticated by calculating its hash and matching it
65 non secure world image (BL33). The public part is stored in one of the
71 sign the content certificate for the BL3X image. The public part is stored
88 of the BL2 image.
104 image.
113 It is self-signed with the BL31 key. It contains a hash of the BL31 image.
122 It is self-signed with the BL32 key. It contains a hash of the BL32 image.
131 It is self-signed with the BL33 key. It contains a hash of the BL33 image.
151 - BL1 loads the BL2 image. Its hash is calculated and compared with the hash
[all …]
/trusted-firmware-a-latest/plat/marvell/
Dmarvell.mk7 BOOT_IMAGE := boot-image.bin
8 BOOT_ENC_IMAGE := boot-image-enc.bin
9 FLASH_IMAGE := flash-image.bin
/trusted-firmware-a-latest/docs/components/
Dfirmware-update.rst59 - Retrieve the image specification (offset and length) of updated images
61 - Set these image specification in the corresponding I/O policies of the
69 and also if the system successfully booted the Normal-world image then
78 .. image:: ../resources/diagrams/PSA-FWU.png
110 :ref:`Trusted Board Boot` design document, which describes the image
137 - FWU image authentication
154 TF-A uses abbreviated image terminology for FWU images like for other TF-A
167 Each FWU image and certificate is identified by a unique ID, defined by the
168 platform, which BL1 uses to fetch an image descriptor (``image_desc_t``) via a
173 The image descriptor includes the following information:
[all …]
Dcot-binding.rst7 and 'image' nodes) mentioning properties of the certificate and image respectively.
49 - image-id
57 It refers to their parent image, which typically contains
138 image-id = <TRUSTED_KEY_CERT_ID>;
150 image-id = <SCP_FW_KEY_CERT_ID>;
173 Description: Container of image nodes
187 Describes image properties which will be used during
192 - image-id
193 Usage: Required for every image with unique id.
200 Required for every image to provide a reference to
[all …]
/trusted-firmware-a-latest/drivers/arm/css/scp/
Dcss_bom_bootloader.c104 int css_scp_boot_image_xfer(void *image, unsigned int image_size) in css_scp_boot_image_xfer() argument
111 assert((uintptr_t) image == SCP_BL2_BASE); in css_scp_boot_image_xfer()
121 checksum = *(uint32_t *) image; in css_scp_boot_image_xfer()
122 image = (char *) image + sizeof(checksum); in css_scp_boot_image_xfer()
174 cmd_data_payload->offset = (uintptr_t) image - ARM_TRUSTED_SRAM_BASE; in css_scp_boot_image_xfer()
Dcss_sds.c18 int css_scp_boot_image_xfer(void *image, unsigned int image_size) in css_scp_boot_image_xfer() argument
30 image_offset = (uintptr_t) image - ARM_TRUSTED_SRAM_BASE; in css_scp_boot_image_xfer()
/trusted-firmware-a-latest/docs/plat/marvell/armada/
Duart-booting.rst10 Armada37x0 UART image downloading
13 There are two options how to download UART image into any Armada37x0 board.
47 produced by ``mrvl_uart`` target or also with ``flash-image.bin`` file produced by ``mrvl_flash``
63 To download single file image built by ``mrvl_flash`` target at the highest speed, run:
67 > mox-imager -D /dev/ttyUSB<port#> -E -b 6000000 -t flash-image.bin
78 not loose any boot output. It also prints boot output which is sent either by image files or by
79 bootrom during transferring of image files. This mini terminal can be quit by CTRL-\\ + C keypress.
82 A7K/A8K/CN913x UART image downloading
85 A7K/A8K/CN913x uses same image ``flash-image.bin`` for both flashing and booting over UART.
86 For downloading image over UART it is possible to use mvebu64boot tool.
[all …]
Dbuild.rst16 Set U-Boot image path (relatively to TF-A root or absolute path)
29 Set MSS/SCP image path (mandatory only for A7K/A8K/CN913x when MSS_SUPPORT=1)
38 Install ARM 32-bit cross compiler, which is required for building WTMI image for CM3
106 Build trusted(=1)/non trusted(=0) image, default is non trusted.
145 When enabled it is required to specify path to the MSS firmware image via ``SCP_BL2``
152 Specify path to the MSS fimware image binary which will run on Cortex-M3 coprocessor.
275 The path of the binary can point to an image which
276 does nothing, an image which supports EFUSE or a customized CM3 firmware
277 binary. The default image is ``fuse.bin`` that built from sources in WTP
278 folder, which is the next option. If the default image is OK, then this
[all …]
/trusted-firmware-a-latest/lib/optee/
Doptee_utils.c41 optee_image_t *image) in parse_optee_image() argument
46 init_load_addr = ((uint64_t)image->load_addr_hi << 32) | in parse_optee_image()
47 image->load_addr_lo; in parse_optee_image()
48 init_size = image->size; in parse_optee_image()
55 if ((image->load_addr_hi == UINT32_MAX) && in parse_optee_image()
56 (image->load_addr_lo == UINT32_MAX)) { in parse_optee_image()
/trusted-firmware-a-latest/plat/xilinx/common/
Dplat_startup.c206 entry_point_info_t *image; in xbl_handover() local
251 image = bl32; in xbl_handover()
262 image = bl33; in xbl_handover()
290 image->pc = HandoffParams->partition[i].entry_point; in xbl_handover()
293 EP_SET_EE(image->h.attr, EP_EE_BIG); in xbl_handover()
295 EP_SET_EE(image->h.attr, EP_EE_LITTLE); in xbl_handover()
/trusted-firmware-a-latest/docs/getting_started/
Dimage-terminology.rst16 - The main name change is to prefix each image with the processor it corresponds
37 - The image names are not case sensitive. For example, ``bl1`` is
49 required by the platform. For example, most platforms require a BL33 image
57 and authenticate an updateable AP firmware image into an executable RAM
58 location, then hand-off control to that image.
80 single or primary image executing at Secure-EL1. In systems where there are
101 abbreviated name should identify the vendor as well as the image
109 image is not provided, TF-A builds Test Realm Payload (TRP) image by default
110 and uses it as the RMM image.
117 and authenticate an updateable SCP firmware image into an executable RAM
[all …]
/trusted-firmware-a-latest/tools/marvell/doimage/secure/
Dsec_img_7K.cfg1 # Trusted boot image extension definitions
6 # Only a key with csk_key_index will be used for signing the image
17 # AES-256 symmetric key for image encryption
Dsec_img_8K.cfg1 # Trusted boot image extension definitions
6 # Only a key with csk_key_index will be used for signing the image
17 # AES-256 symmetric key for image encryption
/trusted-firmware-a-latest/plat/marvell/armada/common/mss/
Dmss_scp_bootloader.c307 static int split_and_load_bl2_image(void *image) in split_and_load_bl2_image() argument
314 file_hdr = (file_header_t *)image; in split_and_load_bl2_image()
326 img_hdr = (img_header_t *)((uintptr_t)image + sizeof(file_header_t)); in split_and_load_bl2_image()
327 single_img = (uintptr_t)image + sizeof(file_header_t) + in split_and_load_bl2_image()
350 int scp_bootloader_transfer(void *image, unsigned int image_size) in scp_bootloader_transfer() argument
353 assert((uintptr_t) image == SCP_BL2_BASE); in scp_bootloader_transfer()
364 if (split_and_load_bl2_image(image)) in scp_bootloader_transfer()
/trusted-firmware-a-latest/drivers/renesas/common/auth/
Dauth_mod.c48 } image[RCAR_IMAGE_ID_MAX] = { in auth_mod_verify_img() local
102 if (img_id != image[index].id) in auth_mod_verify_img()
105 ret = rcar_get_certificate(image[index].cert, &cert_addr); in auth_mod_verify_img()
122 ERROR("Verification Failed 0x%x, %s\n", ret, image[index].name); in auth_mod_verify_img()
/trusted-firmware-a-latest/drivers/brcm/
Dscp.c46 int download_scp_patch(void *image, unsigned int image_size) in download_scp_patch() argument
48 unsigned int *pheader = (unsigned int *)(image); in download_scp_patch()
/trusted-firmware-a-latest/tools/nxp/create_pbl/
DREADME6 RCW image is placed first followed by the,
8 Input BL2 image stored on the,
27 image is to be copied
28 -o <output filename> - Name of PBL image generated
32 -f <Address> - BL2 image offset
/trusted-firmware-a-latest/docs/security_advisories/
Dsecurity-advisory-tfv-1.rst29 the normal world, while retaining the essential image authentication
52 implementation is designed to copy an image into secure memory for subsequent
68 * clip the block to the required image size.
74 WARN("BL1-FWU: Copy argument block_size > remaining image size."
78 /* Make sure the image src/size is mapped. */
84 INFO("BL1-FWU: Continuing image copy in blocks\n");
86 /* Copy image for given block size. */
92 This code fragment is executed when the image copy operation is performed in
104 /* Make sure the image src/size is mapped. */
119 /* Update the image size. */
[all …]
/trusted-firmware-a-latest/docs/plat/
Dsocionext-uniphier.rst8 image from a non-volatile storage to the on-chip SRAM, and jumps over to it.
19 of each case. The image authentication for the UniPhier platform fully
23 it can not verify the BL2 image by itself. Instead, the UniPhier BL assures
26 fits in the 64KB limit. The concatenated image is loaded by the internal boot
37 the image is verified by the SoC's own method.
42 setup, it decompresses the appended BL2 image into the DRAM, then jumps to
64 SoCs. The U-Boot image (``u-boot.bin``) must be built in advance. For the build
82 `mbed TLS`_ is needed as the cryptographic and image parser modules.
92 If desired, FIP can include an SCP BL2 image. If BL2 finds an SCP BL2 image
Dintel-stratix10.rst40 - Build atf providing the previously generated UEFI as the BL33 image
77 INFO: BL2: Loading image id 3
78 INFO: Loading image id=3 at address 0xffe1c000
80 INFO: BL2: Loading image id 5
81 INFO: Loading image id=5 at address 0x50000

12345