Searched refs:ELF (Results 1 – 25 of 55) sorted by relevance
123
| /Zephyr-latest/tests/robot/ |
| D | common.robot | 5 Execute Command $elf = ${ELF}
|
| /Zephyr-latest/boards/common/ |
| D | renode_robot.board.cmake | 6 # ELF: used in common.robot to set the `elf` variable in the default .resc script defined i…
11 board_runner_args(renode-robot "--renode-robot-arg=--variable=ELF:@${PROJECT_BINARY_DIR}/${KERNEL_E…
|
| /Zephyr-latest/doc/services/llext/ |
| D | load.rst | 4 Once an extension is built and the ELF file is available, it can be loaded into
13 to read the ELF data. A loader also provides some minimal context (memory)
15 containing an ELF in addressable memory in memory is available as
37 ``.init_array`` sections of the ELF file with the :c:func:`llext_bringup`
45 ELF file. This may have security implications if its origin is untrusted.
|
| D | debug.rst | 7 definition not built with the Zephyr application, the final Zephyr ELF file
32 An intermediate ELF file with full debugging information.
58 where ``<path-to-debug.elf>`` is the full path of the ELF file with debug
76 area of the ELF buffer or the LLEXT heap.
99 Edit the ELF file
103 experience. The idea is to edit the main Zephyr ELF file to remove information
109 procedure, as there can be many different layers; for example, the ELF buffer
229 mistakenly reference the ELF buffer in the Zephyr application instead of the
296 Editing the ELF file
299 In this alternative approach, the patches to the Zephyr ELF file must be
[all …]
|
| D | index.rst | 9 Extensions are precompiled executables in ELF format that can be verified,
|
| D | config.rst | 26 ELF object type
68 into the ELF buffer. To be effective, this requires the use of an ELF
|
| /Zephyr-latest/boards/qemu/x86/ |
| D | Kconfig.defconfig | 64 # This is needed for QEMU to load the ELF image
86 # This is needed for QEMU to load the ELF image
|
| /Zephyr-latest/soc/intel/intel_adsp/tools/ |
| D | cavstwist.sh | 107 ELF=$BLDDIR/zephyr/zephyr.elf.mod
|
| /Zephyr-latest/boards/arduino/nano_33_ble/support/ |
| D | startup.cmm | 25 PRINT %ERROR "Missing ELF file path"
103 ; load ELF
|
| /Zephyr-latest/boards/nxp/ucans32k1sic/support/ |
| D | startup.cmm | 10 ; - elfFile filepath of ELF to load *
35 PRINT %ERROR "Missing ELF file path"
|
| /Zephyr-latest/include/zephyr/linker/ |
| D | llext-sections.ld | 24 * Zephyr ELF for post-processing, but it is not included in the final binary.
|
| D | intlist.ld | 23 * matter where this region goes as it is stripped from the final ELF image.
|
| /Zephyr-latest/boards/nxp/mr_canhubk3/support/ |
| D | startup.cmm | 9 ; - elfFile filepath of ELF to load *
33 PRINT %ERROR "Missing ELF file path"
|
| /Zephyr-latest/soc/intel/intel_adsp/common/ |
| D | CMakeLists.txt | 42 # Generate rimage modules from the base kernel ELF file. Note the
44 # where if the copy removes all the sections from an input ELF program
51 # .module!) if it has any of ALLOC, WRITABLE or EXEC flags in the ELF
|
| /Zephyr-latest/doc/kernel/usermode/ |
| D | mpu_userspace.rst | 12 ELF file and finds all of the thread stack objects. A set of privileged
|
| D | kernelobjects.rst | 53 appears in the ELF symbol table. It is permitted to declare kernel objects
55 generated ELF file to find kernel objects and places their memory addresses
103 the DWARF debug information present in the generated ELF file for the kernel.
|
| /Zephyr-latest/doc/services/profiling/ |
| D | perf.rst | 19 in the stack trace to function names using symbols from the ELF file, and to prints them in the
|
| /Zephyr-latest/include/zephyr/arch/x86/ |
| D | memory.ld | 23 * Setting LMAs here helps let QEMU or any other ELF-aware loader know where to
109 * final ELF image. The address doesn't even have to be valid on the
|
| /Zephyr-latest/subsys/llext/ |
| D | Kconfig | 23 bool "Single object ELF file"
31 bool "Relocatable ELF file"
39 bool "Shared library ELF file"
|
| /Zephyr-latest/tests/subsys/llext/ |
| D | CMakeLists.txt | 46 # ELF shared libraries do not support init sections
|
| /Zephyr-latest/arch/x86/zefi/ |
| D | README.txt | 46 basically Windows DLLs. But our compiler only generates code for ELF
51 in ELF get found via GOT and PLT tables that are populated at load
|
| /Zephyr-latest/boards/quicklogic/quick_feather/doc/ |
| D | index.rst | 78 - Connect via GDB and load an ELF file:
|
| /Zephyr-latest/samples/subsys/llext/modules/ |
| D | README.rst | 12 llext subsystem allows for the loading of relocatable ELF files at runtime;
|
| /Zephyr-latest/boards/nxp/s32z2xxdc2/support/ |
| D | startup.cmm | 11 ; - elfFile filepath of ELF to load *
37 PRINT %ERROR "Missing ELF file path"
|
| /Zephyr-latest/cmake/bintools/ |
| D | bintools_template.cmake | 99 # readelf_flag_headers : Flag to use for specifying ELF headers should be read
119 # symbols_infile : ELF file name
|
123
