| /rk3399_ARM-atf/docs/threat_model/firmware_threat_model/ |
| H A D | index.rst | 6 is not necessarily the best approach. Instead, we provide a collection of
9 which focuses on the most common configuration we expect to see. The other
19 features within the project, we have not reached that point yet. We expect
30 data flow diagram, as well as a list of threats we have identified using the
|
| H A D | threat_model_arm_cca.rst | 76 which need more time to stabilize. Thus, we do not consider threats that may
120 In this threat model, we use the same method to analyse threats as in the
128 - At this time we only consider the ``Server`` target environment. New threats
|
| /rk3399_ARM-atf/docs/design_documents/ |
| H A D | cmake_framework.rst | 40 To overcome these and other problems, we need to create workarounds for some
104 In the provisioning phase, first we have to obtain the necessary resources, i.e.
105 clone the code repository and other dependencies. Next we have to do the
108 In the development phase first we run CMake, which will generate the buildsystem
110 supported). After this we run the selected build tool which in turn calls the
111 compiler, linker, packaging tool, etc. Finally we can run and debug the output
121 First, we create a setting group called *mem_conf* and fill it with several
126 Next, we create a target called *fw1* and add the *mem_conf* setting group to
128 the parameters declared in the setting group. Then we set the target type to
130 the settings group, we can use it for conditionally adding source files. E.g.
|
| H A D | measured_boot_poc.rst | 51 OP-TEE TA and therefore we need to include the OP-TEE OS image.
74 - **TPM Kernel module**: In order to interact with the fTPM service, we need
84 extensions to enable Measured Boot and an fTPM service. Therefore, we can rely
172 Then we can issue the ``ftpm`` command, which is an alias that
408 Following up with the fTPM startup process, we can see that all the
435 by means of ``tpm_pcrread`` command. Note that we are only interested in the
436 SHA256 logs here, as this is the algorithm we used on TF-A for the measurements
467 In this PoC we are only interested in PCR0, which must be non-null. This is
477 we do not validate here if the content of PCR0 is correct or not. For this
478 PoC, we are only focused on the fact that the event log could be passed to a third
|
| /rk3399_ARM-atf/docs/process/ |
| H A D | security.rst | 7 We disclose all security vulnerabilities we find, or are advised about, that are
9 vulnerabilities and inform users as best we can about all possible issues.
18 Although we try to keep TF-A secure, we can only do so with the help of the
31 Afterwards, we encourage you to write-up your findings about the TF-A source
|
| H A D | platform-ports-policy.rst | 22 are affected by a deprecation / removal decision, we encourage their maintainers
43 period before deleting it (typically 2 release cycles). In this case, we keep
|
| H A D | commit-style.rst | 84 The permissible `scopes` are more flexible, and we maintain a list of them in
90 While we don't enforce scopes strictly, we do ask that commits use these if they
|
| H A D | code-review-guidelines.rst | 4 Why do we do code reviews?
8 other's code, we can help catch issues that were missed by the author
115 - Design issues ("This won't scale well when we introduce feature X.")
116 - Improvements ("Would it be better if we did Y instead?")
|
| /rk3399_ARM-atf/docs/plat/ |
| H A D | imx8m.rst | 61 In U-boot we turn on the UEFI secure boot features so it can verify
62 grub. And we use grub to verify linux kernel.
67 When setting MEASURED_BOOT=1 on imx8mm we can let TF-A generate event logs
69 maximum size PLAT_IMX8M_DTO_MAX_SIZE. Then in U-boot we can apply the DTB
|
| H A D | allwinner.rst | 97 world only. Since this SRAM region is very limited (48 KB), we take
101 The mapping we use on those SoCs is as follows:
130 lacks the "ARISC" management processor (SCP) we use. BL31 thus needs to
133 SRAM size, we use the normal 1:1 mapping with 32 bits worth of virtual
|
| H A D | ti-k3.rst | 18 loads the needed images for A53 startup, because of this we do not need BL1 or
|
| H A D | rpi3.rst | 42 This means that we can use the default AArch32 kernel provided in the official
44 anything else we need is in ``armstub8.bin``. This way we can forget about the
48 Ideally, we want to load the kernel and have all cores available, which means
49 that we need to make the secondary cores work in the way the kernel expects, as
53 To get the most out of a AArch32 kernel, we want to boot it in Hypervisor mode
66 file, but we can specify the address it is loaded to in ``config.txt``.
83 This means that we need to avoid the first 128 MiB of RAM when placing the
400 the existing ``kernel7.img`` (we have already copied a AArch64 kernel).
|
| H A D | rpi4.rst | 67 we use as much of this workflow as possible.
78 To keep things simple, we will just use the kernel load address as the BL33
|
| H A D | qemu-sbsa.rst | 5 Armv8-A. While running Qemu from command line, we need to supply two Flash
|
| /rk3399_ARM-atf/docs/about/ |
| H A D | lts.rst | 58 In this section we will define exactly what constitutes LTS for TF-A.
59 Specifically, we will define the following characteristics:
119 5 years and we can discuss extending it to 7 years later on. The LTS release
154 As we work with the LTS branch of TFTF, we might also need fixes for TFTF
160 CI Scripts moves forward with TF-A changes, since we need to checkout the
163 Though we are unlikely to update CI scripts, but time to time migrating a newer
169 Both Hafnium and OP-TEE move forward with TF-A changes so we need to freeze their
192 Going forward we should strive to make the period smaller and smaller until
213 being released. Note that here we don’t allow the extra testing and debugging
214 time that we had between Nov 2022 and early Feb 2023. This is because there
[all …]
|
| H A D | contact.rst | 30 Every other week, we organize a call with all interested TF-A contributors.
|
| /rk3399_ARM-atf/plat/arm/board/fvp/fdts/ |
| H A D | fvp_fw_config.dts | 35 * non shared SRAM. The runtime checks ensure we don't
|
| H A D | fvp_stmm_spmc_at_el3_manifest.dts | 11 * To get proper define value for StandaloneMm, we need to define manually
|
| H A D | fvp_stmm_rust_spmc_manifest.dts | 11 * To get proper define value for StandaloneMm, we need to define manually
|
| /rk3399_ARM-atf/plat/arm/board/juno/fdts/ |
| H A D | juno_stmm_spmc_at_el3_manifest.dts | 11 * To get proper define value for StandaloneMm, we need to define manually
|
| /rk3399_ARM-atf/plat/nvidia/tegra/scat/ |
| H A D | bl31.scat | 103 * address, but we need to place them in a separate page so that we can set
|
| /rk3399_ARM-atf/ |
| H A D | readme.rst | 21 In collaboration with interested parties, we will continue to enhance TF-A
|
| /rk3399_ARM-atf/docs/components/ |
| H A D | context-management-library.rst | 47 that are not influenced by Normal World operations. Therefore, for each CPU, we
184 Apart from these files, we have some context related source files under ``BL1``
450 disabled for Secure and Realm worlds. In this case, we don't need to explicitly
453 lower exception levels of Secure and Realm worlds. In this scenario, we save the
454 general purpose and Pauth registers while we enter EL3 from lower ELs via
455 ``prepare_el3_entry`` and restore them back while we exit EL3 to lower ELs
504 Apart from the CPU context structure, we have another structure to manage some
565 Root Context needs to be setup as early as possible before we try and access/modify
|
| /rk3399_ARM-atf/docs/perf/ |
| H A D | psci-performance-n1sdp.rst | 4 For this test we used the N1 System Development Platform (`N1SDP`_), which
|
| /rk3399_ARM-atf/docs/components/spd/ |
| H A D | tlk-dispatcher.rst | 10 In order to compile TLK-D, we need a BL32 image to be present. Since, TLKD
|