docs/design/firmware-design.rst

122    -  FW_CONFIG is loaded by BL1, then its address is passed in ``arg0`` to BL2.
124    -  If HW_CONFIG is loaded by BL1, then its address is passed in ``arg2`` to
126    -  If SOC_FW_CONFIG is loaded by BL2, then its address is passed in ``arg1``
128    -  Similarly, if HW_CONFIG is loaded by BL1 or BL2, then its address is
130    -  For other BL3x images, if the firmware configuration file is loaded by
131       BL2, then its address is passed in ``arg0`` and if HW_CONFIG is loaded
321 SVC mode (for AArch32) . BL2 is linked against and loaded at a platform-specific
362 dynamic configuration files. The files are loaded and can be parsed as
375 using the Boot Over MHU (BOM) protocol after being loaded in the trusted SRAM
479 BL32 is loaded in DRAM in this case, to avoid other images reclaiming
486 The image for this stage is loaded by BL2 and BL1 passes control to BL31 at
488 loaded at a platform-specific base address (more information can be found later
1807 to load a new image is free to prevent overwriting a previously loaded image.
1809 relevant BL images to be loaded.
1838 -  BL2 is loaded below BL1 RW
1841    is loaded at the top of the Trusted SRAM, such that its NOBITS sections will
1846 -  On Juno, SCP_BL2 is loaded temporarily into the EL3 Runtime Software memory
1850 -  BL32 (for AArch64) can be loaded in one of the following locations:
1857    When BL32 (for AArch64) is loaded into Trusted SRAM, it is loaded below
1910     0x04040000 +----------+  loaded by BL2  +----------------+
1955     0x04040000 +--------------+  loaded by BL2  +----------------+
2000     0x04040000 +----------+  loaded by BL2  +----------------+
2043     0x08000000 +----------+                  BL31 is loaded
2046     0x04040000 +----------+  loaded by BL2  +----------------+
2085     0x08000000 +----------+                  BL31 is loaded
2088     0x04040000 +----------+  loaded by BL2  +----------------+
2105 potentially other payloads) into a single archive that can be loaded by TF-A
2175 package that can be loaded by TF-A from platform storage. The tool currently
2188 Bootloader images are loaded according to the platform policy as specified by