Home
last modified time | relevance | path

Searched refs:loaded (Results 1 – 25 of 54) sorted by relevance

123

/rk3399_ARM-atf/drivers/renesas/common/io/
H A Dio_rcar.c391 static int32_t loaded = IO_NOT_SUPPORTED; in load_bl33x() local
408 if (loaded != IO_NOT_SUPPORTED) { in load_bl33x()
409 return loaded; in load_bl33x()
417 loaded = IO_FAIL; in load_bl33x()
418 return loaded; in load_bl33x()
427 loaded = IO_FAIL; in load_bl33x()
428 return loaded; in load_bl33x()
434 loaded = IO_FAIL; in load_bl33x()
435 return loaded; in load_bl33x()
441 loaded = IO_FAIL; in load_bl33x()
[all …]
/rk3399_ARM-atf/docs/plat/arm/fvp/
H A Dfvp-aemv8-base.rst26 a specific DTS for all the CPUs to be loaded.
89 config allowing BL31 to be loaded at any valid address for execution.
91 - Since a FIP is not loaded when using BL31 as reset entrypoint, the
96 and loaded via the ``--data cluster0.cpu0="<path-to>/<fdt>"@0x82000000``
100 specific DTS for all the CPUs to be loaded.
150 config allowing SP_MIN to be loaded at any valid address for execution.
H A Dfvp-specific-configs.rst5 that have to be loaded, the Non-Secure FWU ROM (NS-BL1U), and the
8 The additional fip images must be loaded with:
61 #. The EL3 payload may be pre-loaded in volatile memory using the following
132 For example, if the kernel is loaded at ``0x80080000`` the firmware can be
/rk3399_ARM-atf/docs/components/spd/
H A Doptee-dispatcher.rst15 understand the risks involved with allowing the Trusted OS to be loaded this
24 OP-TEE is loaded.
/rk3399_ARM-atf/fdts/
H A Dtc-fpga.dtsi33 * android image will be side loaded to this location
/rk3399_ARM-atf/docs/design/
H A Dalt-boot-flows.rst46 not loaded by TF-A. Therefore, there are 2 possible scenarios:
52 - The EL3 payload needs to be loaded in volatile memory (e.g. DRAM) at
75 without a BL33 and prepare to jump to a BL33 image loaded at address
H A Dreset-design.rst95 processors are loaded by some firmware running on a secure system processor
104 BL31 is loaded to its runtime address, which must match the CPU's ``RVBAR_EL3``
116 which case the ``bl31.bin`` image must be loaded to its run address in Trusted
H A Dtrusted-board-boot-build.rst42 are loaded from that path instead of the default OS path. Export this
101 #. The optional FWU_FIP contains any additional images to be loaded from
H A Dfirmware-design.rst122 - 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
[all …]
/rk3399_ARM-atf/docs/plat/
H A Dintel-stratix10.rst79 INFO: Image id=3 loaded: 0xffe1c000 - 0xffe24034
82 INFO: Image id=5 loaded: 0x50000 - 0x550000
H A Dpoplar.rst125 INFO: Image id=1 loaded at address 0xe9000, size = 0x5008
133 INFO: Image id=3 loaded at address 0x129000, size = 0x8038
136 INFO: Image id=5 loaded at address 0x37000000, size = 0x58f17
H A Drcar-gen3.rst231 INFO: Image id=3 loaded: 0x44000000 - 0x4403e000
236 INFO: Image id=4 loaded: 0x44100000 - 0x44200000
241 INFO: Image id=5 loaded: 0x50000000 - 0x50100000
H A Drpi3.rst62 between them so that the addresses they are loaded to match the ones specified
65 The device tree block is loaded by the VideoCore loader from an appropriate
66 file, but we can specify the address it is loaded to in ``config.txt``.
68 The file ``kernel8.img`` contains a kernel image that is loaded to the address
70 a AArch32 Linux kernel image is loaded in ``Documentation/arm/Booting``:
76 that it is loaded above 32MiB in order to avoid the need to relocate
212 because the file ``kernel8.img`` can be loaded anywhere by modifying the file
H A Drz-g2.rst205 INFO: Image id=3 loaded: 0x44000000 - 0x4403e000
210 INFO: Image id=5 loaded: 0x50000000 - 0x50100000
/rk3399_ARM-atf/docs/plat/arm/automotive_rd/
H A Drdaspen.rst20 Once loaded, the RSE signals the System Control Processor firmware (SCP-firmware)
37 * Completes its dynamic configuration from the FW_CONFIG loaded.
100 If it is not set, then ``BL33`` will be loaded directly after ``BL31``.
/rk3399_ARM-atf/plat/arm/board/fvp/fdts/
H A Dfvp_fw_config.dts37 * is loaded at base of DRAM.
/rk3399_ARM-atf/docs/components/
H A Dsecure-partition-manager.rst92 secure partitions are to be loaded by BL2 on behalf of the SPMC.
220 When SPMC resides at a lower EL i.e., S-EL1 or S-EL2, it is loaded by BL2 as the
221 BL32 image. The SPMC manifest is loaded by BL2 as the ``TOS_FW_CONFIG`` image `[7]`_.
/rk3399_ARM-atf/docs/plat/arm/tc/
H A Dindex.rst9 loaded by AP BL2 from FIP in flash to SRAM for copying by SCP (SCP has access
/rk3399_ARM-atf/docs/plat/st/
H A Dstm32mpus.rst23 Only BL2 (with STM32 header) is loaded by ROM code. The other binaries are
/rk3399_ARM-atf/docs/resources/diagrams/plantuml/
H A Drse_measured_boot_flow.puml23 Rnote over RSE_BL2, AP_BL31: Stored in flash, loaded and executed in RAM
/rk3399_ARM-atf/docs/about/
H A Dfeatures.rst96 the EL3 Runtime Software is loaded using other firmware or a separate
97 secure system processor, or where a non-TF-A ROM expects BL2 to be loaded
/rk3399_ARM-atf/drivers/nxp/auth/csf_hdr_parser/
H A Dinput_bl2_ch237 # Specify the target where image will be loaded. (Default is NOR_16B) - [Optional]
/rk3399_ARM-atf/docs/design_documents/
H A Dmeasured_boot_dtpm_poc.rst57 loaded. Currently U-boot does not have Discrete TPM support for the
277 MESS:00:00:02.469610:0: Device tree loaded to 0x200000 (size 0x823f)
289 INFO: Image id=1 loaded: 0x100b4000 - 0x100c0281
335 INFO: Image id=3 loaded: 0x100e0000 - 0x100e706b
338 INFO: Image id=5 loaded: 0x11000000 - 0x110a8ad8
H A Drse.rst13 released from reset and their initial code is loaded then they continue their
55 meant for signalling that the sender loaded the data to the channel registers
319 by the bootloaders when the firmware image is loaded and measured. The metadata
396 INFO: FCONF: Config file with image ID:31 loaded at address = 0x4001010
398 INFO: Image id=24 loaded: 0x4001300 - 0x400153a
411 INFO: FCONF: Config file with image ID:24 loaded at address = 0x4001300
414 INFO: Image id=1 loaded: 0x404d000 - 0x406412a
/rk3399_ARM-atf/docs/components/fconf/
H A Dtb_fw_bindings.rst127 indicates that the partition is position independent and can be loaded at

123