| /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
6 extension into memory, access its symbols and call its functions.
8 Loading an extension
11 An extension may be loaded using any implementation of a :c:struct:`llext_loader`
19 passing in the extension name and the configured loader. Once that completes
20 successfully, the extension is loaded into memory and is ready to be used.
23 When :ref:`User Mode <usermode_api>` is enabled, the extension will not be
27 Initializing and cleaning up the extension
30 The extension may define a number of initialization functions that must be
34 extension.
[all …]
|
| D | config.rst | 11 The LLEXT subsystem needs a static heap to be allocated for extension related
21 large enough to allow the extension sections to be allocated with the
60 and copies all data into allocated memory; this is done to allow the extension
67 Allow the extension to be loaded by directly referencing section data
75 extension remains allocated until the extension is unloaded.
80 phase. Once the extension is unloaded, the buffer must be reloaded
94 When an extension is loaded, the LLEXT subsystem must find the address of all
95 the symbols residing in the main application that the extension references.
99 LLEXT linker at extension load time. This process is pretty slow due to the
126 forbidden to load an extension that was compiled with
|
| D | build.rst | 9 The easiest path to achieve this is to build the extension as part of the
12 main Zephyr application and the extension(s), which will all automatically be
16 convenient; maybe the extension is built using a different compiler suite or as
17 part of a different project altogether. In this case, the extension developer
31 Building the extension
34 An extension can be defined in the app's ``CMakeLists.txt`` by invoking the
52 packaged extension;
54 create the extension.
56 The exact steps of the extension building process depend on the currently
76 The final extension file name.
[all …]
|
| D | debug.rst | 6 Debugging extensions is a complex task. Since the extension code is by
8 does not contain the symbols for extension code. Furthermore, the extension is
11 final locations of the symbols in the extension code.
36 The final extension binary, stripped to the essential data required for
48 and let it run. This will load the extension into memory and relocate it.
52 5. Type this command in the GDB console to load this extension's symbols:
63 6. The extension symbols are now available to the debugger. You can set
66 Steps 4-6 can be repeated for every extension that is loaded by the
93 properly follow stack traces outside the extension code.
96 switch between the main and extension symbol tables as required, but it rapidly
[all …]
|
| /Zephyr-latest/arch/riscv/ |
| D | Kconfig.isa | 30 Standard integer multiplication and division instruction extension,
41 The standard atomic instruction extension is denoted by instruction
51 Standard instruction-set extension for single-precision
62 Standard double-precision floating-point instruction-set extension,
86 Standard extension for 128-bit binary floating-point instructions
95 RISC-V standard compressed instruction set extension, named "C",
104 The "Zicsr" extension introduces support for the full set of CSR
112 The "Zifencei" extension includes the FENCE.I instruction that
119 (Zaamo) - Atomic memory operation subset of the A extension
121 The Zaamo extension enables support for AMO*.W/D-style instructions.
[all …]
|
| /Zephyr-latest/samples/subsys/llext/edk/ |
| D | README.rst | 5 Enable linkable loadable extension development outside the Zephyr tree using
25 The application also creates different memory domains for each extension, thus
29 Note that the kernel extension is only available when the EDK is built with
117 [app]Loading extension [kext1].
118 [app]Thread 0x20840 created to run extension [kext1], at privileged mode.
122 [app]Loading extension [ext1].
123 [app]Thread 0x20a30 created to run extension [ext1], at userspace.
126 [app]Loading extension [ext2].
127 [app]Thread 0x20938 created to run extension [ext2], at userspace.
|
| /Zephyr-latest/samples/subsys/llext/shell_loader/ |
| D | README.rst | 37 This sample also includes the source for a very basic extension,
58 the extension via the :c:macro:`EXPORT_SYMBOL` macro. Compiling with this
63 symbols defined in the extension ELF file via the Kconfig option
67 The compiled extension can be inspected with the usual binutils utilities to
160 llext - Loadable extension commands
166 unload :Unload an extension by name. Syntax:
168 list_symbols :List extension symbols. Syntax:
170 call_fn :Call extension function with prototype void fn(void). Syntax:
173 The hex string generated above can be used to load the extension:
179 This extension can then be seen in the list of loaded extensions (``list``), its symbols printed
[all …]
|
| D | CMakeLists.txt | 11 # Add a target for building the extension code
|
| /Zephyr-latest/tests/misc/llext-edk/extension/ |
| D | CMakeLists.txt | 8 project(extension) project
34 add_custom_target(extension ALL DEPENDS ${PROJECT_BINARY_DIR}/${PROJECT_NAME}.llext) target
|
| /Zephyr-latest/doc/develop/west/ |
| D | extensions.rst | 7 source code. These are called **west extension commands**, or just "extensions"
10 information on west extension commands, and has a tutorial for writing your
36 To disable support for extension commands, set the ``commands.allow_extensions``
51 Note that the files containing extension commands are not imported by west
57 There are three steps to adding your own extension:
64 Note that west ignores extension commands whose names are the same as a
75 this class will be instantiated and used when your extension is run.
85 Basic example of a west extension.'''
89 from west.commands import WestCommand # your extension must subclass this
139 describes your extension to west.
[all …]
|
| /Zephyr-latest/soc/andestech/ae350/ |
| D | Kconfig | 75 bool "Andes V5 PowerBrake extension"
79 The PowerBrake extension throttles performance by reducing instruction
83 bool "Andes V5 EXEC.IT extension"
88 The EXEC.IT extension (Execution on Instruction Table) generate
|
| /Zephyr-latest/drivers/interrupt_controller/ |
| D | Kconfig.clic | 24 The selective hardware vectoring extension gives users the flexibility
34 Enables legacy clic, where smclicshv extension is not supported and
|
| /Zephyr-latest/tests/net/lib/http_server/common/src/ |
| D | main.c | 443 if (strncmp(ct->extension, "html", ct->extension_len) == 0) { in ZTEST()
445 } else if (strncmp(ct->extension, "css", ct->extension_len) == 0) { in ZTEST()
447 } else if (strncmp(ct->extension, "js", ct->extension_len) == 0) { in ZTEST()
449 } else if (strncmp(ct->extension, "jpg", ct->extension_len) == 0) { in ZTEST()
451 } else if (strncmp(ct->extension, "png", ct->extension_len) == 0) { in ZTEST()
453 } else if (strncmp(ct->extension, "svg", ct->extension_len) == 0) { in ZTEST()
455 } else if (strncmp(ct->extension, "mpg", ct->extension_len) == 0) { in ZTEST()
458 zassert_unreachable("unknown extension (%s)", ct->extension); in ZTEST()
|
| /Zephyr-latest/tests/drivers/fuel_gauge/sbs_gauge/ |
| D | Kconfig | 10 Enabling this option adds test sources that verify if the battery cutoff extension to the
|
| /Zephyr-latest/tests/subsys/llext/ |
| D | CMakeLists.txt | 50 # generate extension targets for each extension in 'ext_names'
73 # Manually fix the pre_located extension's text address at a multiple of 4
|
| /Zephyr-latest/drivers/rtc/ |
| D | rtc_rx8130ce.c | 99 uint8_t extension; member
361 data->reg.extension |= EXT_WADA; in rx8130ce_alarm_set_time()
428 if (data->reg.extension & EXT_WADA) { in rx8130ce_alarm_get_time()
672 data->reg.extension &= ~EXT_TE; in rx8130ce_init()
677 data->reg.extension |= EXT_FSEL1 | EXT_FSEL0; in rx8130ce_init()
680 data->reg.extension &= ~EXT_FSEL0; in rx8130ce_init()
681 data->reg.extension |= EXT_FSEL1; in rx8130ce_init()
684 data->reg.extension |= EXT_FSEL0; in rx8130ce_init()
685 data->reg.extension &= ~EXT_FSEL1; in rx8130ce_init()
688 data->reg.extension &= ~(EXT_FSEL1 | EXT_FSEL0); in rx8130ce_init()
|
| /Zephyr-latest/samples/subsys/llext/modules/ |
| D | README.rst | 5 Call a function in a loadable extension module,
26 load the extension and call the function. The caller code is in
48 - The following commands build and run the sample so that the extension code is
|
| /Zephyr-latest/soc/openisa/rv32m1/ |
| D | CMakeLists.txt | 6 # options are y-selected; provide full arch string with the custom extension otherwise.
|
| /Zephyr-latest/boards/st/nucleo_g070rb/doc/ |
| D | index.rst | 10 - Two types of extension resources:
13 - ST morpho extension pin headers for full access to all STM32 I/Os
31 - Two types of extension resources:
34 - ST morpho extension pin headers for full access to all STM32 I/Os
|
| /Zephyr-latest/boards/st/nucleo_g071rb/doc/ |
| D | index.rst | 10 - Two types of extension resources:
13 - ST morpho extension pin headers for full access to all STM32 I/Os
31 - Two types of extension resources:
34 - ST morpho extension pin headers for full access to all STM32 I/Os
|
| /Zephyr-latest/cmake/sca/eclair/ECL/ |
| D | language_extensions.ecl | 1 -doc_begin="The following extension have been approved."
|
| /Zephyr-latest/boards/renesas/rzt2l_rsk/doc/ |
| D | index.rst | 9 Octal Flash so you can evaluate various functions of the RZ/T2L without an extension board.
13 so you can evaluate various functions of the RZ/T2L without an extension board
15 * Pin headers for external extension enable you to evaluate many use cases
|
| /Zephyr-latest/boards/shields/m5stack_core2_ext/doc/ |
| D | index.rst | 10 extension connector. It features an MPU6886 6-axis motion tracker (6DOF IMU)
|
| /Zephyr-latest/include/zephyr/net/http/ |
| D | server.h | 157 const char *extension; member
164 .extension = STRINGIFY(_extension), \
|
| /Zephyr-latest/doc/develop/tools/ |
| D | vscode.rst | 47 generate the :file:`compile_commands.json` file that will provide the C/C++ extension with the
56 Configure the C/C++ extension
107 …tension Pack: https://marketplace.visualstudio.com/items?itemName=ms-vscode.cpptools-extension-pack
|
