Searched refs:AP (Results 1 – 21 of 21) sorted by relevance
| /trusted-firmware-a-3.7.0/docs/plat/marvell/armada/misc/ |
| 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 | | +-+---------+ …
|
| D | mvebu-ccu.rst | 13 specific AP.
|
| D | mvebu-io-win.rst | 24 specific AP.
|
| /trusted-firmware-a-3.7.0/docs/threat_model/ |
| D | threat_model_rss_interface.rst | 1 Threat Model for RSS - 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 RSS firmware will be provided by the RSS
23 it includes the RSS and highlights the interface between the AP and the RSS
24 cores. The interface description only focuses on the AP-RSS 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 RSS is
|
| D | threat_model_arm_cca.rst | 105 | | measurements and retrieve data used for AP images |
|
| /trusted-firmware-a-3.7.0/docs/getting_started/ |
| 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 …]
|
| /trusted-firmware-a-3.7.0/docs/plat/arm/tc/ |
| 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).
27 The execution begins from SCP_BL1. SCP_BL1 powers up the AP which starts
29 FIP to SRAM. The SCP has access to AP SRAM. The address and size of SCP_BL2
31 RAM and starts executing it. The AP then continues executing the rest of TF-A
|
| /trusted-firmware-a-3.7.0/docs/resources/diagrams/plantuml/ |
| D | rss_measured_boot_flow.puml | 13 box AP
54 == RSS Runtime / AP Boot phase ==
55 Rnote over RSS_S, AP_BL1: MHU init between RSS and AP
78 == RSS / AP Runtime ==
|
| D | rss_attestation_flow.puml | 4 box AP
|
| /trusted-firmware-a-3.7.0/docs/plat/arm/morello/ |
| 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
|
| /trusted-firmware-a-3.7.0/include/plat/marvell/armada/a8k/common/ |
| D | armada_common.h | 55 AP enumerator
|
| /trusted-firmware-a-3.7.0/docs/design_documents/ |
| D | rss.rst | 5 (RSS) and the application processor (AP). According to the ARM reference design
6 the RSS 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
30 the communication. RSS is capable of mapping the AP memory to its address space.
32 data between memory belonging to RSS or AP. In this way, a bigger amount of data
38 interface. One pair provides message sending from AP to RSS and the other pair
39 from RSS to AP. The sender and receiver are connected via channels. There is an
74 | AP | | |
137 - ``OTP assets management``: Public keys used by AP during the trusted boot
138 process can be requested from RSS. Furthermore, AP can request RSS to
[all …]
|
| /trusted-firmware-a-3.7.0/plat/marvell/armada/a8k/common/ |
| D | plat_ble_setup.c | 658 case(AP): in ble_skip_image_gpio()
|
| /trusted-firmware-a-3.7.0/docs/design/ |
| D | trusted-board-boot-build.rst | 88 - NS_BL2U. The AP non-secure Firmware Updater image.
|
| 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)
1832 | AP TZC |
1877 | AP TZC |
1921 | AP TZC |
1968 | AP TZC |
2010 | AP TZC |
|
| /trusted-firmware-a-3.7.0/docs/plat/arm/ |
| D | arm-build-options.rst | 111 compatible change to the MTL protocol, used for AP/SCP communication.
|
| /trusted-firmware-a-3.7.0/docs/perf/ |
| D | psci-performance-juno.rst | 380 AP CPU to enter WFI before making the channel available to other CPUs, which
|
| /trusted-firmware-a-3.7.0/docs/plat/marvell/armada/ |
| D | build.rst | 127 Total amount of CPs (South Bridge) connected to AP. When the parameter is omitted,
|
| /trusted-firmware-a-3.7.0/docs/components/ |
| D | firmware-update.rst | 177 authentication). Secure world certificates and non-AP images are examples
|
| /trusted-firmware-a-3.7.0/docs/ |
| D | porting-guide.rst | 261 Defines the maximum message size between AP and RSS. Need to define if
322 If the AP Firmware Updater Configuration image, BL2U is used, the following
1973 The AP Firmware Updater Configuration, BL2U, is an optional part of the FWU
1977 #. (Optional) Transferring the optional SCP_BL2U binary image from AP secure
1979 ``SCP_BL2U_BASE`` defines the address in AP secure memory where SCP_BL2U
2055 Application Processor (AP) for BL2U execution to continue.
|
| D | change-log.md | 2272 …- add MHU addresses for AP-RSS comms on TC2 ([6299c3a](https://review.trustedfirmware.org/plugins/…
2273 …- add RSS-AP message size macro ([445130b](https://review.trustedfirmware.org/plugins/gitiles/TF-A…
3016 …- rename AP-RSS message size macro ([70247dd](https://review.trustedfirmware.org/plugins/gitiles/T…
3805 …- change the AP runtime UART address ([07302a2](https://review.trustedfirmware.org/plugins/gitiles…
7520 - Add support for SCMI AP core configuration protocol v1.0
7521 - Use SCMI AP core protocol to set the warm boot entrypoint
7758 for communication between SCP and the AP CPU, replacing Boot-Over_MHU (BOM)
|
