Lines Matching refs:image

16 - 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
118 location, then hand-off control to that image. This may be performed in
122 This image was previously abbreviated as ``BL0`` but in some systems, the SCP
124 make sense to interleave the image terminology for AP and SCP; both AP and SCP
134 This image was previously abbreviated as BL3-0 but from the SCP's point of view,
153 secure and normal world. The "level" of the BL image is relative to the world
155 of "NS" implies a secure world image.
160 This image does the minimum necessary AP secure world configuration required to
167 This image does the minimum necessary SCP secure world configuration required to
184 underscore and the level of the firmware image.