| /rk3399_ARM-atf/docs/plat/marvell/armada/misc/ |
| H A D | mvebu-a8k-addr-map.rst | 10 …|| AP DMA | | | | | +-------------+ …
11 …|| SD/eMMC | | CA72 CPUs | | AP MSS | +-------------+ …
14 …| | | | | +----- Translaton | |AP |…
19 …| | +-| translation | | Lookup +---- +--------- AP SPI |…
22 …| +------------| SMMU +---------+ | | Windows +--------- AP MCI0/1 |…
25 …| - | | +--------- AP STM |…
27 …| AP | | +-+---------+ …
|
| H A D | mvebu-ccu.rst | 13 specific AP.
|
| H A D | mvebu-io-win.rst | 24 specific AP.
|
| /rk3399_ARM-atf/docs/plat/arm/automotive_rd/ |
| H A D | rd1ae.rst | 15 Application Processor (AP) BL2 image and signals the System Control Processor (SCP)
16 to power up the AP. The AP then runs AP BL2
20 1. AP BL2:
23 * Copies the AP BL31 image from Secure Flash to Secure SRAM
24 * Copies the AP BL32 (OP-TEE) image from Secure Flash to Secure DRAM
25 * Copies the AP BL33 (U-Boot) image from Secure Flash to Normal DRAM
26 * Transfers the execution to AP BL31
28 2. AP BL31:
31 * Transfers the execution to AP BL32 and then transfers the execution to AP BL33
35 3. AP BL32:
[all …]
|
| H A D | rdaspen.rst | 19 Application Processor (AP) BL2 image into the Trusted SRAM at a fixed address.
21 running on Safety Island Cluster 0 (SI CL0) to initiate the AP power-up sequence.
23 The SCP-firmware then sets the reset vector base address (RVBAR) for the AP, ensuring
25 powers on AP Cluster 0, allowing the AP to run AP BL2.
27 The following tasks are executed for each AP BL stage:
29 1. AP BL2:
43 * Reads and loads AP BL31 image into the Trusted SRAM.
44 * (Optional step) Computes AP BL31 image measurement and invokes extend operation of TF-M
49 * (If present) Reads and loads AP BL32 (Secure Payload) image into Secure DRAM
50 * (Optional step, if present) Computes AP BL32 image measurement and invokes extend
[all …]
|
| /rk3399_ARM-atf/docs/threat_model/firmware_threat_model/ |
| H A D | threat_model_rse_interface.rst | 1 Threat Model for RSE - AP interface
9 next to the Application Processor (AP).
15 AP. Otherwise, the TF-A :ref:`Generic Threat Model` document is applicable for
16 the AP core. The threat model for the RSE firmware will be provided by the RSE
23 it includes the RSE and highlights the interface between the AP and the RSE
24 cores. The interface description only focuses on the AP-RSE interface the rest
45 are applicable for the AP core, here only the differences are highlighted.
47 - ID 11: The access to the communication interface between AP and RSE is
|
| H A D | threat_model_firmware_handoff.rst | 52 | DF7 | | Information produced during any stage of the AP boot |
|
| H A D | threat_model_arm_cca.rst | 105 | | measurements and retrieve data used for AP images |
|
| H A D | threat_model.rst | 926 the Event Log which is located on the secure on-chip memory of the AP. The
963 hardware solutions, such as an encrypted AP/dTPM bus, or software-based
|
| /rk3399_ARM-atf/docs/getting_started/ |
| H A D | image-terminology.rst | 18 ambiguity (for example, within AP specific code/documentation), it is
52 AP Boot ROM: ``AP_BL1``
55 Typically, this is the first code to execute on the AP and cannot be modified.
57 and authenticate an updateable AP firmware image into an executable RAM
60 AP RAM Firmware: ``AP_BL2``
63 This is the 2nd stage AP firmware. It is currently also known as the "Trusted
71 Also known as "SoC AP firmware" or "EL3 monitor firmware". Its primary purpose
82 abbreviation should be avoided; use the recommended **Other AP 3rd level
85 AP Normal World Firmware: ``AP_BL33``
90 Other AP 3rd level images: ``AP_BL3_XXX``
[all …]
|
| /rk3399_ARM-atf/docs/plat/arm/tc/ |
| H A D | index.rst | 9 loaded by AP BL2 from FIP in flash to SRAM for copying by SCP (SCP has access
10 to AP SRAM).
25 The execution begins from SCP_BL1. SCP_BL1 powers up the AP which starts
27 FIP to SRAM. The SCP has access to AP SRAM. The address and size of SCP_BL2
29 RAM and starts executing it. The AP then continues executing the rest of TF-A
|
| /rk3399_ARM-atf/docs/resources/diagrams/plantuml/ |
| H A D | rse_measured_boot_flow.puml | 13 box AP
54 == RSE Runtime / AP Boot phase ==
55 Rnote over RSE_S, AP_BL1: MHU init between RSE and AP
78 == RSE / AP Runtime ==
|
| H A D | rse_attestation_flow.puml | 4 box AP
|
| /rk3399_ARM-atf/docs/plat/arm/morello/ |
| H A D | index.rst | 17 It performs minimum initialization necessary to load and authenticate the AP
18 firmware image (the FIP image) from the AP QSPI NOR Flash Memory into the
|
| /rk3399_ARM-atf/include/plat/marvell/armada/a8k/common/ |
| H A D | armada_common.h | 55 AP enumerator
|
| /rk3399_ARM-atf/docs/design_documents/ |
| H A D | rse.rst | 5 (RSE) and the application processor (AP). According to the ARM reference design
6 the RSE is an independent core next to the AP and the SCP on the same die. It
12 its own images and the initial images of SCP and AP. When AP and SCP are
36 mapping the AP memory to its address space.
38 data between memory belonging to RSE or AP. In this way, a bigger amount of data
44 interface. One pair provides message sending from AP to RSE and the other pair
45 from RSE to AP. The sender and receiver are connected via channels. There is an
80 | AP | | |
143 - ``OTP assets management``: Public keys used by AP durin
[all...] |
| /rk3399_ARM-atf/plat/arm/board/neoverse_rd/platform/rdv3/fdts/ |
| H A D | rdv3_spmc_sp_manifest.dts | 82 reg = /* AP Memory Expansion 2 - Secure Flash*/
|
| /rk3399_ARM-atf/plat/marvell/armada/a8k/common/ |
| H A D | plat_ble_setup.c | 658 case(AP): in ble_skip_image_gpio()
|
| /rk3399_ARM-atf/docs/design/ |
| H A D | trusted-board-boot-build.rst | 106 - NS_BL2U. The AP non-secure Firmware Updater image.
|
| H A D | firmware-design.rst | 52 - Boot Loader stage 1 (BL1) *AP Trusted ROM*
60 - Boot Loader stage 1 (BL1) *AP Trusted ROM*
376 memory. The SCP executes SCP_BL2 and signals to the Application Processor (AP)
1892 | AP TZC |
1937 | AP TZC |
1981 | AP TZC |
2028 | AP TZC |
2070 | AP TZC |
|
| /rk3399_ARM-atf/docs/perf/ |
| H A D | psci-performance-juno.rst | 353 AP CPU to enter WFI before making the channel available to other CPUs, which
|
| /rk3399_ARM-atf/docs/plat/arm/ |
| H A D | arm-build-options.rst | 124 compatible change to the MTL protocol, used for AP/SCP communication.
|
| /rk3399_ARM-atf/docs/plat/marvell/armada/ |
| H A D | build.rst | 127 Total amount of CPs (South Bridge) connected to AP. When the parameter is omitted,
|
| /rk3399_ARM-atf/docs/components/ |
| H A D | firmware-update.rst | 177 authentication). Secure world certificates and non-AP images are examples
|
| /rk3399_ARM-atf/docs/ |
| H A D | porting-guide.rst | 261 Defines the maximum message size between AP and RSE. Need to define if
322 If the AP Firmware Updater Configuration image, BL2U is used, the following
2069 The AP Firmware Updater Configuration, BL2U, is an optional part of the FWU
2073 #. (Optional) Transferring the optional SCP_BL2U binary image from AP secure
2075 ``SCP_BL2U_BASE`` defines the address in AP secure memory where SCP_BL2U
2151 Application Processor (AP) for BL2U execution to continue.
|