Lines Matching refs:in
5 resets in Trusted Firmware-A (TF-A). It also describes how the platform
7 resulting in a simplified and more optimised boot flow.
9 This document should be used in conjunction with the :ref:`Firmware Design`
16 The TF-A reset code is implemented in BL1 by default. The following high-level
28 above is still relevant, as all these operations will occur in BL31 in
40 If the reset vector address (reflected in the reset vector base address register
43 detection can be skipped, resulting in the following boot flow:
65 applies. This results in the following boot flow:
82 This results in the following boot flow:
101 logic in the BL31 entry point to support this use case.
108 images might be done by the Trusted Boot Firmware or by platform code in BL31.
115 It allows the Arm FVP port to support the ``RESET_TO_BL31`` configuration, in
116 which case the ``bl31.bin`` image must be loaded to its run address in Trusted
119 the FVP models in this way.
122 the right support in the SCP firmware, this is currently not implemented so the
125 The ``RESET_TO_BL31`` configuration requires some additions and changes in the
133 ``PROGRAMMABLE_RESET_ADDRESS`` and ``COLD_BOOT_SINGLE_CPU`` build options in the
145 that can be passed in registers by previous boot stages. Instead, the platform
146 code in BL31 needs to know, or be able to determine, the location of the BL32
147 (if required) and BL33 images and provide this information in response to the
152 receive parameters in registers depending on their actual boot sequence. On
153 those occasions, and in addition to ``RESET_TO_BL31``, these platforms should
159 This might be done by the Trusted Boot Firmware or by platform code in BL31.