| /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 | 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 | 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
|
| /Zephyr-latest/arch/riscv/ |
| D | Kconfig.isa | 30 Standard integer multiplication and division instruction extension,
39 The standard atomic instruction extension is denoted by instruction
49 Standard instruction-set extension for single-precision
60 Standard double-precision floating-point instruction-set extension,
84 Standard extension for 128-bit binary floating-point instructions
93 RISC-V standard compressed instruction set extension, named "C",
102 The "Zicsr" extension introduces support for the full set of CSR
110 The "Zifencei" extension includes the FENCE.I instruction that
|
| /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/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/tests/net/lib/http_server/common/src/ |
| D | main.c | 369 if (strncmp(ct->extension, "html", ct->extension_len) == 0) { in ZTEST()
371 } else if (strncmp(ct->extension, "css", ct->extension_len) == 0) { in ZTEST()
373 } else if (strncmp(ct->extension, "js", ct->extension_len) == 0) { in ZTEST()
375 } else if (strncmp(ct->extension, "jpg", ct->extension_len) == 0) { in ZTEST()
377 } else if (strncmp(ct->extension, "png", ct->extension_len) == 0) { in ZTEST()
379 } else if (strncmp(ct->extension, "svg", ct->extension_len) == 0) { in ZTEST()
381 } else if (strncmp(ct->extension, "mpg", ct->extension_len) == 0) { in ZTEST()
384 zassert_unreachable("unknown extension (%s)", ct->extension); in ZTEST()
|
| /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/neorv32/ |
| D | Kconfig | 19 # NEORV32 RISC-V ISA A extension implements only LR/SC, not AMO
35 "C" extension (Compressed Instructions).
|
| /Zephyr-latest/tests/subsys/llext/ |
| D | CMakeLists.txt | 48 # generate extension targets foreach extension given by 'ext_names'
71 # Manually fix the pre_located extension's text address at a multiple of 4
|
| /Zephyr-latest/samples/subsys/llext/shell_loader/ |
| D | README.rst | 39 llext - Loadable extension commands
45 unload :Unload an extension by name. Syntax:
47 list_symbols :List extension symbols. Syntax:
49 call_fn :Call extension function with prototype void fn(void). Syntax:
133 The resulting hex string can be used to load the extension.
139 This extension can then be seen in the list of loaded extensions (``list``), its symbols printed
140 (``list_symbols``), and the hello_world function which the extension exports can be called and
|
| /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/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/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/cmake/sca/eclair/ECL/ |
| D | language_extensions.ecl | 1 -doc_begin="The following extension have been approved."
|
| /Zephyr-latest/tests/lib/devicetree/api_ext/ |
| D | app.overlay | 7 * Application overlay for testing the devicetree.h extension API's.
|
| /Zephyr-latest/include/zephyr/net/http/ |
| D | server.h | 147 const char *extension; member
154 .extension = STRINGIFY(_extension), \
|
| /Zephyr-latest/cmake/ |
| D | llext-edk.cmake | 5 # build an llext extension. It does so by copying all headers accessible from
7 # cmake.cflags one) with all flags necessary to build the extension.
9 # The tarball can be extracted and used in the extension build system to include
15 # - llext_edk_name: Name of the extension, used to name the tarball and the
27 # edk directory. This is necessary when building an extension that only
|
| /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/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/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
|
| /Zephyr-latest/lib/posix/options/ |
| D | Kconfig.c_lib_ext | 6 bool "POSIX general C library extension"
|
