| /rk3399_ARM-atf/docs/plat/ |
| H A D | imx9.rst | 45 together to generate a binary file called flash.bin, the imx-mkimage tool is 46 used to generate flash.bin, and flash.bin needs to be flashed into SD card 52 Details on how to prepare, generate & deploy the boot image be found in following documents:
|
| H A D | imx8ulp.rst | 54 together to generate a binary file called flash.bin, the imx-mkimage tool is 55 used to generate flash.bin, and flash.bin needs to be flashed into SD card 61 Details on how to prepare, generate & deploy the boot image be found in following documents:
|
| H A D | imx8.rst | 52 to generate a binary file called flash.bin, the imx-mkimage tool is used 53 to generate flash.bin, and flash.bin needs to be flashed into SD card
|
| H A D | imx8m.rst | 45 together to generate a binary file called flash.bin, the imx-mkimage tool is 46 used to generate flash.bin, and flash.bin needs to be flashed into SD card 67 When setting MEASURED_BOOT=1 on imx8mm we can let TF-A generate event logs
|
| H A D | warp7.rst | 20 We need to use a file generated by u-boot in order to generate a .imx image the 23 to generate the TF-A .imx image.
|
| H A D | allwinner.rst | 44 The default build options should generate a working firmware image. There are
|
| H A D | nvidia-tegra.rst | 97 files help support ARMLINK linker to generate BL31 binaries. For now, there
|
| /rk3399_ARM-atf/docs/plat/nxp/ |
| H A D | nxp-ls-tbbr.rst | 16 -- NXP CST tool gives an option to generate it. 26 -- NXP CST tool gives an option to generate the RSA key pair and its hash. 49 - To generate CSF header, path of CST repository needs to be specified as CST_DIR 53 - GENERATE_COT=1 adds the tool 'cert_create' to the build environment to generate: 94 - To generate CSF header, path of CST repository needs to be specified as CST_DIR 98 - Default input file requires user to generate RSA key pair named
|
| /rk3399_ARM-atf/tools/sptool/ |
| H A D | sptool.py | 105 def generate(self, f_out : str): member in SpPkg 137 pkg.generate(args.o)
|
| /rk3399_ARM-atf/plat/arm/board/common/ |
| H A D | board_common.mk | 72 $(error Cannot generate public key: no ROT_KEY defined) 153 $(error Cannot generate hash: no PROT_KEY defined) 160 $(error Cannot generate hash: no SWD_KEY defined)
|
| /rk3399_ARM-atf/docs/tools/ |
| H A D | cot-dt2c.rst | 4 This tool is used to automatically generate the corresponding c file for a 7 tool can generate the c file for the platform that does not support CoT DT 54 which can generate the C file given the CoT descriptors. Before
|
| H A D | memory-layout-tool.rst | 37 The tool can be used to generate a visualisation of the symbol table. By 121 generate a table (per memory type), showing memory allocation and usage. This is
|
| /rk3399_ARM-atf/lib/libfdt/ |
| H A D | meson.build | 60 pkgconfig.generate(
|
| /rk3399_ARM-atf/docs/components/ |
| H A D | romlib-design.rst | 102 generate a dependency file of the included index files which can be directly 114 The ``romlib_generator.py genwrappers`` does not generate wrappers for the
|
| H A D | granule-protection-tables-design.rst | 118 and PAS type as arguments to generate the pas_region_t structure. As the names
|
| /rk3399_ARM-atf/docs/design_documents/ |
| H A D | cmake_framework.rst | 67 configuration management tool (e.g. Kconfig) shall be used to generate these 108 In the development phase first we run CMake, which will generate the buildsystem
|
| /rk3399_ARM-atf/docs/plat/qti/ |
| H A D | rb3gen2.rst | 57 It will generate a tar ball in the build folder for RB3Gen2 something like:
|
| /rk3399_ARM-atf/docs/getting_started/ |
| H A D | docs-build.rst | 104 dependencies to generate the documents, so in this case, one way to
|
| H A D | build-options.rst | 283 generate A32 code. This option is enabled by default only in AArch64 debug 722 for the Trusted Board Boot feature in the BL1 and BL2 images, to generate
|
| /rk3399_ARM-atf/lib/zlib/ |
| H A D | crc32.c | 345 # error Need a 64-bit integer type in order to generate crc32.h. in make_crc_table()
|
| /rk3399_ARM-atf/docs/design/ |
| H A D | interrupt-framework-design.rst | 173 platform. A interrupt controller could generate a type of interrupt as either an 262 is considered and it is assumed that the FIQ signal is used to generate Secure-EL1 263 interrupts and the IRQ signal is used to generate non-secure interrupts in either 524 the FIQ signal is used to generate Secure-EL1 interrupts and the IRQ signal 525 is used to generate non-secure interrupts in either security state.
|
| H A D | trusted-board-boot.rst | 301 library version to generate the X.509 certificates. The specific version of the
|
| /rk3399_ARM-atf/docs/process/ |
| H A D | coding-style.rst | 51 analysis is used to regularly generate a report of current MISRA defects and to
|
| /rk3399_ARM-atf/docs/threat_model/ |
| H A D | supply_chain_threat_model.rst | 59 - *cert_create*: This tool is used to generate certificates for binary images.
|
| /rk3399_ARM-atf/docs/ |
| H A D | change-log.md | 338 …- generate FIP for DDR initialization ([aa63c23](https://review.trustedfirmware.org/plugins/gitile… 3060 …- generate tbbr c file CoT dt2c ([479c833](https://review.trustedfirmware.org/plugins/gitiles/TF-A… 4502 …- don't generate build-id ([304ad94](https://review.trustedfirmware.org/plugins/gitiles/TF-A/trust… 4777 …- generate stm32 file ([e5839ed](https://review.trustedfirmware.org/plugins/gitiles/TF-A/trusted-f… 5033 …- generate `ARM_BL2_SP_LIST_DTS` file from `sp_layout.json` ([20629b3](https://review.trustedfirmw… 9279 …- generate two memory nodes for larger than 2 GiB channel 0 ([21924f2](https://review.trustedfirmw… 10628 - build_macros: Add CREATE_SEQ function to generate sequence of numbers 10731 migrate to implicit rules, derive map file name from target name, generate 12682 - The mbed TLS SHA1 functions are not needed, as SHA256 is used to generate
|