Lines Matching refs:to
5 images referred to in the Trusted Firmware project.
10 - Some of the names and abbreviated names have changed to accommodate new
11 requirements. The changed names are as backward compatible as possible to
13 code, documentation and build artefacts may still refer to the previous names;
14 these will inevitably take time to catch up.
16 - The main name change is to prefix each image with the processor it corresponds
17 to (for example ``AP_``, ``SCP_``, ...). In situations where there is no
19 permitted to omit the processor prefix (for example, just BL1 instead of
26 new form is to just omit the dash and not use subscript formatting.
29 example, function names) it's not possible to use this character. All dashes
46 Typically, this is the first code to execute on the AP and cannot be modified.
47 Its primary purpose is to perform the minimum initialization necessary to load
49 location, then hand-off control to that image.
55 Boot Firmware". Its primary purpose is to perform any additional initialization
56 required to load and authenticate all 3rd level firmware images into their
57 executable RAM locations, then hand-off control to the EL3 Runtime Firmware.
63 is to handle transitions between the normal and secure world.
68 Typically this is a TEE or Trusted OS, providing runtime secure services to the
69 normal world. However, it may refer to a more abstract Secure-EL1 Payload (SP).
79 For example, UEFI or uboot. Its primary purpose is to boot a normal world OS.
98 Typically, this is the first code to execute on the SCP and cannot be modified.
99 Its primary purpose is to perform the minimum initialization necessary to load
101 location, then hand-off control to that image. This may be performed in
107 make sense to interleave the image terminology for AP and SCP; both AP and SCP
115 SCP needs to load/authenticate multiple 3rd level images in future.
125 to be considered in a production Trusted Board Boot solution.
130 Typically, this is the first normal world code to execute on the AP during a
131 firmware update operation, and cannot be modified. Its primary purpose is to
133 with ``AP_BL1`` to authenticate those images.
136 secure and normal world. The "level" of the BL image is relative to the world
137 it's in so it makes sense to encode "NS" in the normal world images. The absence
143 This image does the minimum necessary AP secure world configuration required to
150 This image does the minimum necessary SCP secure world configuration required to
158 to load a new set of firmware images from an external interface and write them
164 Some systems may have additional processors to the AP and SCP. For example, a