| /rk3399_ARM-atf/docs/design/ |
| H A D | cpu-specific-build-macros.rst | 12 vulnerability workarounds should be applied at runtime.
15 `CVE-2017-5715`_. This flag can be set to 0 by the platform if none
28 `CVE-2018-3639`_. This build option should be set to 1 if the target
33 This build option should be set to 1 if the target platform contains at
38 in EL3 FW. This build option should be set to 1 if the target platform contains
42 This build option should be set to 1 if the target platform contains at
46 This build option should be set to 1 if the target platform contains at
55 are applied to each CPU by the reset handler. The errata details can be found
78 for it to specify which errata workarounds should be enabled or not.
86 CPU. This needs to be enable
[all...] |
| H A D | auth-framework.rst | 8 #. It should be possible for a platform port to specify the Chain of Trust in
120 platform and cannot be modified.
128 it could be any other data that requires authentication.
145 be used to authenticate the next image in the CoT.
165 #. Specifying the CoT for each image that needs to be authenticated. Details of
166 how a CoT can be specified by the platform are explained later. The platform
177 parameters are stored as X509v3 extensions, the corresponding OID must be
184 cannot be interpreted by the CM, e.g. if an image has to be verified using a
185 NV counter, then the value of the counter to compare with can only be
197 other things, the authentication and image parsing methods must be specified
[all …]
|
| /rk3399_ARM-atf/docs/process/ |
| H A D | platform-ports-policy.rst | 15 Due to evolving requirements and enhancements, there might be changes affecting
16 platform compatibility, which means the previous interface needs to be deprecated
27 the release after which each one will be removed. When an interface is
28 deprecated, the page must be updated to indicate the release after which the
29 interface will be removed. This must be at least 1 full release cycle in future.
30 For non-trivial interface changes, an email should be sent out to the `TF-A
40 can be a 1-stage or 2-stage process (up to the maintainers).
42 - *2-stage*: The source code can be kept in the repository for a cooling off
46 - *1-stage*: The source code can be deleted straight away. In this case, both
50 platform ports (or soon to be) to this day.
|
| H A D | faq.rst | 21 to get an estimate of when it will be merged.
23 * The quality of the patch set. Patches are likely to be merged more quickly if
36 * How many other patch sets are waiting to be integrated and the risk of
49 the delay will be less than 1 day. If the TF maintainers are trying to merge
51 Typically, it will be 1-2 days.
54 receiving patches that will not be merged into the release. In this case, the
55 patches will be merged onto ``integration``, which will temporarily diverge from
56 the release branch. The ``integration`` branch will be rebased onto ``master``
57 after the release, and then ``master`` will be fast-forwarded to ``integration``
74 if any, can be examined.
|
| /rk3399_ARM-atf/docs/components/fconf/ |
| H A D | index.rst | 10 platform specific data, allowing a "property" to be queried and a value
16 platform-defined tables. In the future, it may be provided as part of a device
26 Examples namespace can be:
33 Properties can be accessed with the ``FCONF_GET_PROPERTY(a,b,property)`` macro.
38 Properties composing the |FCONF| have to be stored in C structures. If
47 Hence each ``populate()`` function must be registered with a specific
59 Hence the ``populate()`` callback must be registered to the (|FCONF|) framework
61 would be called inside the generic ``fconf_populate()`` function during
73 Then, a wrapper has to be provided to match the ``FCONF_GET_PROPERTY()`` macro:
83 This second level wrapper can be used to remap the ``FCONF_GET_PROPERTY()`` to
[all …]
|
| H A D | fconf_properties.rst | 5 properties are not related to a specific platform and can be queried from
15 - Must be the string "fconf,dyn_cfg-dtb_registry".
17 Then a list of subnodes representing a configuration |DTB|, which can be used
18 by |FCONF|. Each subnode should be named according to the information it
19 contains, and must be formed with the following fields:
|
| /rk3399_ARM-atf/docs/plat/ |
| H A D | imx8m.rst | 36 Target_SoC should be "imx8mq" for i.MX8MQ SoC.
37 Target_SoC should be "imx8mm" for i.MX8MM SoC.
38 Target_SoC should be "imx8mn" for i.MX8MN SoC.
39 Target_SoC should be "imx8mp" for i.MX8MP SoC.
46 used to generate flash.bin, and flash.bin needs to be flashed into SD card
47 with certain offset for BOOT ROM. the u-boot and imx-mkimage will be upstreamed
48 soon, this doc will be updated once they are ready, and the link will be posted.
59 BL2 will be in the FIT image and SPL will verify it.
60 All of the BL3x will be put in the FIP image. BL2 will verify them.
68 with a DTB overlay. The overlay will be put at PLAT_IMX8M_DTO_BASE with
[all …]
|
| H A D | imx8.rst | 45 Target_SoC should be "imx8qm" for i.MX8QM SoC.
46 Target_SoC should be "imx8qx" for i.MX8QX SoC.
53 to generate flash.bin, and flash.bin needs to be flashed into SD card
55 u-boot and imx-mkimage will be upstreamed soon, this doc will be updated
56 once they are ready, and the link will be posted.
|
| /rk3399_ARM-atf/docs/components/ |
| H A D | sdei.rst | 45 events can be explicitly dispatched in response to other exceptions, for
64 - The event number: this must be a positive 32-bit integer.
69 - If it's not applicable to an event, this shall be left as ``0``.
71 - If the event is dynamic, this should be specified as ``SDEI_DYN_IRQ``.
75 To define event 0, the macro ``SDEI_DEFINE_EVENT_0()`` should be used. This
78 To define an event that's meant to be explicitly dispatched (i.e., not as a
80 should be used. It accepts two parameters:
87 Once the event descriptor arrays are defined, they should be exported to the
90 ``REGISTER_SDEI_MAP()`` macro must be used in the same file where the arrays are
97 - There must be exactly one descriptor in the private array, and none in the
[all …]
|
| H A D | granule-protection-tables-design.rst | 14 access allowed to each security state can be seen in the table below.
52 region must be mapped in Level 1 table.
54 The Level 1 tables entries with the same PAS can be combined to form a
69 is the smallest unit of memory that can be independently assigned to a PAS.
72 PPS and PGS are passed into the APIs at runtime and can be determined in
83 structure used by the granule transition service which will be covered more
88 Table creation API calls can be found in ``plat/arm/common/arm_common.c`` and
89 runtime initialization API calls can be seen in
100 its attributes that can be used by the GPT library to initialize the tables.
115 ``GPT_MAP_REGION_BLOCK`` and ``GPT_MAP_REGION_GRANULE`` be used to populate
[all …]
|
| /rk3399_ARM-atf/docs/components/spd/ |
| H A D | trusty-dispatcher.rst | 7 Detailed information and build instructions can be found on the Android
14 Custom boot parameters can be passed to Trusty by providing a platform
21 If this function is provided ``args->arg0`` must be set to the memory
25 can be set to a platform specific parameter block, and ``args->arg2``
26 should then be set to the size of that block.
|
| /rk3399_ARM-atf/make_helpers/ |
| H A D | constraints.mk | 22 $(error SPMC_AT_EL3 and ENABLE_RME cannot both be enabled.)
51 $(error FEAT_RME must be enabled when FEAT_MEC is enabled.)
54 $(error FEAT_TCR2 must be enabled when FEAT_MEC is enabled.)
57 $(error FEAT_SCTLR2 must be enabled when FEAT_MEC is enabled.)
77 $(warning "The SPD and its BL32 companion will be present but ignored.")
82 $(error SPM cannot be enabled in both S-EL2 and EL3.)
91 $(error SEL0 SP cannot be enabled without SPMC at EL3)
131 BL33_PAYLOAD_BASE is used and won't be added to the FIP file.")
135 PRELOADED_BL33_BASE is used and won't be added to the FIP file.")
140 # use USE_COHERENT_MEM. Require that USE_COHERENT_MEM must be se
[all...] |
| /rk3399_ARM-atf/docs/ |
| H A D | architecture_features.rst | 16 versions (8.X, 9.X) to which they apply can be found in `Feature_description`_
457 higher exception levels, other features might be used by TF-A code itself.
477 If the feature flag is set to 2, support for the feature will be compiled in,
478 but its existence will be checked at runtime, so it works on CPUs with or
490 b) a feature is to be used by EL3 itself
501 - The flag's name should be in the form ``ENABLE_FEAT_ABC``.
510 - Add any constraints in ``make_helpers/constraints.mk``. This will usually be
512 be found in the main description of the feature in the Arm ARM.
516 A pair of functions must be defined in the form of ``is_feat_abc_present()``
520 - The ``_supported`` variant is the one that should usually be use
[all...] |
| H A D | porting-guide.rst | 25 interfaces as they get introduced in the code base should be *strongly*
48 propose a patch that moves the code to ``plat/common`` so that it can be
54 This section covers the modifications that should be made by the platform for
103 The following variables, functions and constants must be defined by the platform
117 likely to be suitable for all platform ports.
171 states for each level may be sparsely allocated between 0 and this value
179 possible at every power domain level in the platform. This macro should be
197 Defines the base address in secure ROM where BL1 originally lives. Must be
208 at runtime. Must be aligned on a page-size boundary.
218 Must be aligne
[all...] |
| /rk3399_ARM-atf/docs/about/ |
| H A D | lts.rst | 61 - criteria for selecting patches which will be backported to LTS branches
66 We must have an objective criterion for selecting patches to be backported to
69 a. there will be less -- ideally no -- discussion when selecting patches to backport
70 b. large parts of the process can be automated
74 #. No features will be backported.
82 #. Patches can only be backported from the master branch. In other words, the
83 master branch will be a superset of all the changes in any LTS branch.
87 This section approaches three questions: for how long should an LTS release be
88 supported, how frequently should LTS releases be made and at which time(s) of
89 the year should the releases be made.
[all …]
|
| H A D | release-information.rst | 7 The project currently aims to do a release once every 6 months which will be
8 tagged on the master branch. There will be a code freeze (stop merging
11 required for the release will be merged. The maintainers are free to use their
12 judgement on what changes are essential for the release. A release branch may be
16 The release testing will be performed on release candidates and depending on
17 issues found, additional release candidates may be created to fix the issues.
87 after which it will be removed.
102 after which it will be removed.
|
| /rk3399_ARM-atf/docs/plat/arm/arm_fpga/ |
| H A D | index.rst | 19 a single build. Image specific data must be described in the DTB or should
20 be auto-detected at runtime.
24 The /cpus node in the DT will be added and filled accordingly, as long as
44 tree blob (DTB). This DT will be used by TF-A for dynamic configuration,
47 fill the CPU topology nodes. It will also be passed on to BL33, by
54 a command line can be put somewhere into memory, so that BL31 will
56 To avoid random garbage, there needs to be a "CMD:" signature before the
59 FPGA image (which can be written by the FPGA payload uploader, but is
60 read-only to the CPU). The FPGA payload tool should be given a text file
71 addresses need to differ for a certain setup, they can be passed on the
[all …]
|
| /rk3399_ARM-atf/docs/plat/arm/fvp/ |
| H A D | fvp-build-options.rst | 6 - ``FVP_CLUSTER_COUNT`` : Configures the cluster count to be used to
8 cluster topology and this option can be used to override the default value.
10 - ``FVP_INTERCONNECT_DRIVER``: Selects the interconnect driver to be built. The
26 - ``FVP_USE_GIC_DRIVER`` : Selects the GIC driver to be built. Options:
32 - ``FVP_HW_CONFIG_DTS`` : Specify the path to the DTS file to be compiled
36 like shifted affinity format for MPIDR, cannot be detected at build time
39 - ``FVP_HW_CONFIG`` : Specify the path to the HW_CONFIG blob to be packaged in
54 blob at build time. Takes a path to an initrd file. Can be used as an
|
| /rk3399_ARM-atf/docs/plat/st/ |
| H A D | stm32mpus.rst | 6 MPUs, more details and dedicated configuration can be found in each STM32 MPU
17 The TF-A image must be properly formatted with a STM32 header structure
19 Tool stm32image can be used to prepend this header to the generated TF-A binary.
34 Boot media(s) supported by BL2 must be specified in the build command.
48 Only one storage or serial device should be selected in the build command line,
53 - | ``DTB_FILE_NAME``: to precise board device-tree blob to be used.
68 The SD-card has to be formatted with GPT.
|
| /rk3399_ARM-atf/tools/nxp/create_pbl/ |
| H A D | README | 19 -i <BL2 Bin file-name> - file to be added to rcw file.
20 -c <SoC Number> - SoC numeric identifier, may be one of
24 -b <boot source id> - Boot source id string, may be one of
27 image is to be copied
43 -i Input file that is to be added to rcw file.
46 -d Destination address to which file has to be copied
|
| /rk3399_ARM-atf/docs/components/measured_boot/ |
| H A D | event_log.rst | 5 These properties are not related to a specific platform and can be queried
16 - Must be the string "arm,tpm_event_log".
19 can be used by Measured Boot driver. Each property is named according
27 and this property should be removed when this feature is supported.
|
| /rk3399_ARM-atf/docs/getting_started/ |
| H A D | tools-build.rst | 7 can be used if not updating the OpenSSL version on the OS. In order to do
11 libraries. More info about ``OPENSSL_DIR`` can be found at
20 Firmware-A Tests`_ (`tftf.bin``) may be used. Refer to to the `TFTF
40 The resulting FIP may be found in:
62 The tool binary can be located in:
99 # Images will be unpacked to the working directory
115 More information about FIP can be found in the :ref:`Firmware Design` document.
124 previous section), but it can also be built separately with the following
132 'cert_create' tool can be built with the following command. Note that the target
141 verbose. The following command should be used to obtain help about the tool:
[all …]
|
| H A D | initial-build.rst | 21 also select the clang or armclang assembler. Arm Compiler 6 will be selected
26 should be set as described above.
37 work with TF-A). ``CROSS_COMPILE`` need not be set for Clang. Please note,
38 that the default linker may be manually overridden using the ``LD`` variable.
40 Clang will be selected when the base name of the path assigned to ``CC``
74 provided by TF-A to demonstrate how PSCI Library can be integrated with
77 to integrate PSCI library with AArch32 EL3 Runtime Software can be found
102 - Build products for a specific build variant can be removed using:
110 The build tree can be removed completely using:
|
| /rk3399_ARM-atf/docs/design_documents/ |
| H A D | dtpm_drivers.rst | 22 and hardware bus types in order to be compatible with different platforms.
70 - ``MBOOT_TPM_HASH_ALG``: The hash algorithm to be used by the TPM, currently
75 on the selected TPM interface, the appropriate drivers will be built and
79 Ideally there should be four options:
96 The TPM needs to be initialized based on the platform, the hardware interfaces
97 need to be set up independently, and once they are setup, the TPM commands
98 ``tpm_interface_init()`` and subsequently ``tpm_startup()`` can be called.
99 ``tpm_startup()`` only needs to be called once after startup, or if the system
102 An example of platform specific TPM hardware initialization for the rpi3 can be
108 Once the TPM is setup, the TPM ``pcr_extend`` operation can be used to extend
[all …]
|
| H A D | cmake_framework.rst | 25 * TF-M is already using CMake, reducing fragmentation for tf.org projects can be
41 tasks, wrap CMake functions, etc. Since this functionality can be useful in
64 The related parameters shall be packed into a group (or "setting group"). The
65 setting groups shall be defined and filled with content in config files.
67 configuration management tool (e.g. Kconfig) shall be used to generate these
69 conflict checking, these shall be handled by the configuration tool.
77 the previous section. A group can be applied onto a target, i.e. a collection of
78 macros, flags, etc. can be applied onto the given output executable/library.
92 generation or dtc for device tree compilation. These tools have to be found
94 used, any other necessary tools can be added later.
[all …]
|