Searched refs:ELF (Results 1 – 15 of 15) sorted by relevance
| /rk3399_ARM-atf/make_helpers/ |
| H A D | build_macros.mk | 587 $(eval ELF := $(call IMG_ELF,$(1))) 609 $(ELF): $(BUILD_PLAT)/romlib/romlib.bin | $$$$(@D)/ 616 $(ELF): $(OBJS) $(DEFAULT_LINKER_SCRIPT) $(LINKER_SCRIPTS) | $$$$(@D)/ libraries $(BL_LIBS) 637 $(DUMP): $(ELF) | $$$$(@D)/ 641 $(BIN): $(ELF) | $$$$(@D)/ 650 $(1): $(ELF) $(DUMP)
|
| /rk3399_ARM-atf/plat/rockchip/rk3399/drivers/m0/ |
| H A D | Makefile | 53 ELF := $(BUILD)/$(PLAT_M0).elf macro 98 $(ELF) : $(OBJS) $(OBJS_COMMON) $(LINKERFILE)
|
| /rk3399_ARM-atf/docs/plat/qti/ |
| H A D | msm8916.rst | 81 The BL31 ELF image is generated in ``build/$PLAT/release/bl31/bl31.elf``. 90 The BL32 ELF image is generated in ``build/$PLAT/release/bl32/bl32.elf``. 124 The ELF image must be "signed" before flashing it, even if the board has secure 129 case you can simply sign the ELF image using a randomly generated key. You can 138 On AArch32 the ELF image is called ``bl32.elf``.
|
| /rk3399_ARM-atf/docs/plat/arm/corstone1000/ |
| H A D | index.rst | 29 - Obtain AArch64 ELF bare-metal target `toolchain <https://developer.arm.com/tools-and-software/op…
|
| /rk3399_ARM-atf/docs/tools/ |
| H A D | memory-layout-tool.rst | 39 main memory regions in an ELF file (i.e. text, bss, rodata) but can be modified 120 command is provided, the script analyses the ELF binaries in the build path to 155 ELF segments as well as sections.
|
| /rk3399_ARM-atf/docs/getting_started/ |
| H A D | initial-build.rst | 91 from the corresponding ELF files:
|
| H A D | build-options.rst | 232 of the binary image. If set to 1, then only the ELF image is built.
|
| /rk3399_ARM-atf/docs/plat/arm/arm_fpga/ |
| H A D | index.rst | 83 Additionally there is a ``bl31.axf`` ELF file, which contains BL31, as well
|
| /rk3399_ARM-atf/docs/plat/arm/juno/ |
| H A D | index.rst | 207 be used to load the EL3 payload's ELF file over JTAG on Juno.
|
| /rk3399_ARM-atf/tools/memory/ |
| H A D | poetry.lock | 167 description = "Library for analyzing ELF files and DWARF debugging information"
|
| /rk3399_ARM-atf/docs/plat/arm/fvp/ |
| H A D | fvp-specific-configs.rst | 55 command may be used to load the EL3 payload ELF image over JTAG:
|
| /rk3399_ARM-atf/docs/design/ |
| H A D | auth-framework.rst | 330 x509v3 certificates, signed ELF files or any other platform specific format). 435 or ELF format. The IPM supports three parsing methods. An image has to use one
|
| H A D | firmware-design.rst | 681 additional register information to BL31, or a ELF image loader that can convey 882 This structure is allocated in a special ELF section ``.rt_svc_descs``, enabling 1651 binary on the disk. In the ELF terminology, they are called ``PROGBITS`` 1655 space in the binary on the disk. The ELF binary just contains some 1658 In the ELF terminology, they are called ``NOBITS`` sections.
|
| /rk3399_ARM-atf/ |
| H A D | poetry.lock | 755 description = "Library for analyzing ELF files and DWARF debugging information"
|
| /rk3399_ARM-atf/docs/ |
| H A D | change-log.md | 9150 …- avoid re-linking from executable ELF file ([a67ac76](https://review.trustedfirmware.org/plugins/…
|