Lines Matching refs:the
4 Socionext UniPhier Armv8-A SoCs use Trusted Firmware-A (TF-A) as the secure
8 image from a non-volatile storage to the on-chip SRAM, and jumps over to it.
11 problem is BL2 does not fit in the 64KB limit if
14 `UniPhier BL`_. This loader runs in the on-chip SRAM, initializes the DRAM,
15 expands BL2 there, and hands the control over to it. Therefore, all images
18 The UniPhier platform works with/without TBB. See below for the build process
19 of each case. The image authentication for the UniPhier platform fully
20 complies with the Trusted Board Boot Requirements (TBBR) specification.
22 The UniPhier BL does not implement the authentication functionality, that is,
23 it can not verify the BL2 image by itself. Instead, the UniPhier BL assures
24 the BL2 validity in a different way; BL2 is GZIP-compressed and appended to
25 the UniPhier BL. The concatenation of the UniPhier BL and the compressed BL2
26 fits in the 64KB limit. The concatenated image is loaded by the internal boot
27 ROM (and verified if the chip fuses are blown).
35 This is hard-wired ROM, so never corrupted. It loads the UniPhier BL (with
36 compressed-BL2 appended) into the on-chip SRAM. If the SoC fuses are blown,
37 the image is verified by the SoC's own method.
41 This runs in the on-chip SRAM. After the minimum SoC initialization and DRAM
42 setup, it decompresses the appended BL2 image into the DRAM, then jumps to
43 the BL2 entry.
47 This runs in the DRAM. It extracts more images such as BL31, BL33 (optionally
49 they are all authenticated by the standard mechanism of TF-A.
50 After loading all the images, it jumps to the BL31 entry.
54 They all run in the DRAM. See :ref:`Firmware Design` for details.
60 BL2 must be compressed for the reason above. The UniPhier's platform makefile
64 SoCs. The U-Boot image (``u-boot.bin``) must be built in advance. For the build
65 procedure of U-Boot, refer to the document in the `U-Boot`_ project.
82 `mbed TLS`_ is needed as the cryptographic and image parser modules.
83 Refer to the :ref:`Prerequisites` document for the appropriate version of
86 To enable TBB, add the following options to the build command::
93 in FIP, BL2 loads it into DRAM and kicks the SCP. Most of UniPhier boards
96 To include SCP BL2, add the following option to the build command::
102 To enable BL32, add the following options to the build command::
106 If you use TSP for BL32, ``BL32=<path-to-BL32>`` is not required. Just add the
112 .. [1] Some SoCs can load 80KB, but the software implementation must be aligned
113 to the lowest common denominator.