Searched refs:their (Results 251 – 275 of 360) sorted by relevance
1...<<1112131415
| /Zephyr-latest/doc/develop/getting_started/ |
| D | index.rst | 168 you can install dependencies from their respective websites and ensure
632 Text includes source code, terminal commands, and their output.
|
| /Zephyr-latest/doc/develop/application/ |
| D | index.rst | 297 as needed to add and remove repositories, or change their contents.
562 library, each on their own line, like so:
663 are still in early stages of their development cycle. Such features will be
664 marked ``[EXPERIMENTAL]`` in their Kconfig title.
852 and :makevar:`CONF_FILE` environment variables or by setting their values
|
| /Zephyr-latest/dts/arm/microchip/ |
| D | mec5.dtsi | 546 * Some devices are capable of having their registers mapped to
|
| /Zephyr-latest/boards/snps/nsim/arc_v/doc/ |
| D | index.rst | 108 avoid intermixing their output.
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | tls_credentials_shell.rst | 237 These formats and their (case-insensitive) keywords are as follows:
|
| /Zephyr-latest/doc/connectivity/networking/ |
| D | overview.rst | 120 technologies. Applications can send data according to their needs to desired
|
| /Zephyr-latest/doc/services/llext/ |
| D | build.rst | 153 and use the compile flags in their build system to build the extension.
|
| /Zephyr-latest/doc/services/sensing/ |
| D | index.rst | 241 Sensing subsystem using device tree to configuration all sensor instances and their properties,
|
| /Zephyr-latest/cmake/modules/ |
| D | kernel.cmake | 121 # all targets exports their compile commands to fetch object files.
|
| /Zephyr-latest/boards/native/nrf_bsim/doc/ |
| D | nrf52_bsim.rst | 205 These nRF bsim boards use the `native simulator`_ at their core, so you can chose with which
|
| /Zephyr-latest/doc/develop/test/ |
| D | twister.rst | 915 will be put into lists ordered as their appearance in recordings.
996 shell_commands: <list of pairs of commands and their expected output> (default empty)
997 Specify a list of shell commands to be executed and their expected output.
1016 The file should contain a list of commands and their expected output. For example:
1196 hardware map needs to be created with all connected devices and their
1197 details such as the serial device, baud and their IDs if available.
|
| D | bsim.rst | 38 to run all standard Zephyr twister tests, but with models of a real SOC HW, and their drivers.
|
| /Zephyr-latest/doc/releases/ |
| D | migration-guide-3.5.rst | 195 will see last 3 bytes of their MAC address modified by this change.
236 suitable SJW, but their SJW cannot be overwritten by the caller.
|
| /Zephyr-latest/doc/connectivity/networking/conn_mgr/ |
| D | implementation.rst | 39 As such, these functions should be called sparingly, due to their relatively high search cost.
118 This is because all connectivity bindings contain a :ref:`conn_mgr_impl_ctx` of their associated co…
|
| /Zephyr-latest/boards/espressif/esp32_ethernet_kit/doc/ |
| D | index.rst | 49 and their interconnections.
556 OpenOCD that are not upstreamed yet. Espressif maintains their own fork of
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | blob.rst | 121 The application may implement their own BLOB stream, or use the implementations provided by Zephyr:
|
| /Zephyr-latest/boards/espressif/esp32s3_eye/doc/ |
| D | index.rst | 258 Espressif maintains their own fork of the project. The custom OpenOCD can be obtained at
|
| /Zephyr-latest/doc/build/dts/ |
| D | bindings-upstream.rst | 162 Driver developers should use their best judgment as to whether a value can be
|
| /Zephyr-latest/doc/kernel/services/other/ |
| D | fatal.rst | 245 Applications are free to implement their own error handling policy by
|
| /Zephyr-latest/boards/raspberrypi/rpi_pico/doc/ |
| D | index.rst | 14 It is also possible to flash and debug the boards with their SWD interface,
|
| /Zephyr-latest/doc/ |
| D | glossary.rst | 98 reference of their usage and will automatically be suspended or resumed.
|
| /Zephyr-latest/doc/develop/west/ |
| D | zephyr-cmds.rst | 154 <bin-blobs>` declared in one or more :ref:`modules <modules>` via their
|
| /Zephyr-latest/doc/kernel/memory_management/ |
| D | demand_paging.rst | 170 their corresponding page frames and storage. These are the functions
|
| /Zephyr-latest/doc/project/ |
| D | release_process.rst | 87 As fixes make their way into the mainline, the patch rate will slow over time.
142 - Evaluate bugs as potential blockers based on their severity and prevalence.
|
| /Zephyr-latest/boards/native/doc/ |
| D | arch_soc.rst | 41 with focus on their radio (e.g. BT LE) and utilize the `BabbleSim`_ physical layer
416 the Zephyr thread stack allocation for their call stacks or automatic
|
1...<<1112131415
