Home
last modified time | relevance | path

Searched refs:other (Results 376 – 400 of 808) sorted by relevance

1...<<11121314151617181920>>...33

/Zephyr-latest/samples/bluetooth/mesh_provisioner/
DREADME.rst46 For other boards, build and flash the application as follows:
/Zephyr-latest/tests/bsim/bluetooth/ll/edtt/
DREADME.txt44 other Zephyr app, targeting the nrf52_bsim.
/Zephyr-latest/boards/nuvoton/numaker_m2l31ki/doc/
Dindex.rst19 - Two LEDs: one is for power indication and the other is for user-defined
/Zephyr-latest/arch/x86/core/
DKconfig.intel6491 supporting user-level threads that are protected from each other and
/Zephyr-latest/doc/develop/getting_started/
Dindex.rst9 Windows (instructions for other Linux distributions are discussed in
38 On other versions, see `this Apple support topic
387 include a compiler, assembler, linker and other programs required to build
539 * Try other :zephyr:code-sample-category:`samples`
599 Doing this makes it easier for people to help you, and also helps other users
/Zephyr-latest/doc/services/portability/posix/option_groups/
Dindex.rst34 When using Newlib, Picolibc, or other C libraries conforming to the ISO C Standard, the
52 When using Newlib, Picolibc, or other C libraries conforming to the ISO C Standard, the
66 When using Newlib, Picolibc, or other C libraries conforming to the ISO C Standard, the entire
125 When using Newlib, Picolibc, or other C libraries conforming to the ISO C Standard, the
474 and ``raise()``, as well as the other POSIX functions listed below, may exhibit undefined
/Zephyr-latest/doc/services/zbus/
Dindex.rst26 messages. Additionally, besides other actions, threads can publish and observe channels. When a
32 (hardware independent) talks to other threads via software bus. Note that the threads are decoupled
33 from each other because they only use zbus channels and do not need to know each other to talk.
121 can do that, and the change does not affect other parts of the system. Likewise, we would like to
123 No other change is required in order to make that work. Thus, the developer would do that for every
129 can easily be reused in other solutions. The new solution must implement the interfaces (set of
365 * No other threads (that are not involved in the communication) with priority between T1 and S1 can
530 allows original creators of a channel to exert some authority over other developers/publishers who
534 only messages with ``move`` equal to 0, -1, and 1 are valid. Publish function will discard all other
625 For accessing channels or observers from files other than its defining files, it is necessary to
[all …]
/Zephyr-latest/scripts/pylib/twister/twisterlib/
Dtestinstance.py173 def __lt__(self, other): argument
174 return self.name < other.name
/Zephyr-latest/doc/connectivity/bluetooth/shell/audio/
Dcsip.rst14 set. While the coordinated set is locked, no other clients may lock the set.
35 read the set information, which is needed to identify other set members.
Dgmap.rst5 Unlike most other low-layer profiles, GMAP is a profile that exists and has a service (GMAS) on all
/Zephyr-latest/samples/kernel/metairq_dispatch/
DREADME.rst49 other threads, including cooperative ones that cannot normally be
84 look different based upon the clock frequency of the board and other
/Zephyr-latest/doc/build/dts/
Dintro-input-output.rst40 describe the CPU or system-on-chip Zephyr runs on, perhaps by including other
41 ``.dtsi`` files. They can also describe other common hardware features shared by
/Zephyr-latest/doc/contribute/
Dguidelines.rst49 Components using other Licenses
53 use other licensing, as described in :ref:`Zephyr_Licensing`.
55 Importing code into the Zephyr OS from other projects that use a license
56 other than the Apache 2.0 license needs to be fully understood in
122 (c) The contribution was provided directly to me by some other
150 ``git commit -s``. Use other commits in the zephyr git history as examples.
170 are included in pull requests submitted by other contributors. It is expected
178 around working with contributions submitted by other developers.
280 Miscellaneous code that doesn't belong to any of the other top-level
287 Various programs and other files used to build and test Zephyr
[all …]
/Zephyr-latest/doc/connectivity/networking/conn_mgr/
Dimplementation.rst103 Once defined, you can make a connectivity implementation available to other compilation units by de…
194 In other words, no matter how the underlying technology behaves, your implementation must make it a…
222 In other words, the connectivity implementation should not give up on the connection attempt, even …
260 Zephyr ifaces may be accessed from other threads without respecting the binding mutex.
276 In other words, it should be possible for an application to directly use your underlying technology…
343 In other words, it should be possible to configure builds that include Connectivity Manager, as wel…
/Zephyr-latest/doc/develop/application/
Dindex.rst17 makes it easier to use ``west build`` and other commands with it. (You can
54 * **CMakeLists.txt**: This file tells the build system where to find the other
66 more devicetree overlays, and other default files are also searched for.
72 with other settings to produce the final configuration. The purpose of
77 Kconfig fragments, and other default files are also searched for.
120 | :ref:`freestanding | other locations |
239 other west commands to build, flash, and debug.
274 needed. Make any other changes you need to other files.
381 #. Set up any other files you may need, such as :ref:`twister <twister_script>`
496 #. If your application uses a configuration file or files other than
[all …]
/Zephyr-latest/doc/connectivity/usb/device/
Dusb_device.rst63 the next interface, preventing other composite functions from working.
164 backend for other subsystems by setting :ref:`devicetree-chosen-nodes`
187 when the CDC ACM port is used without any real UART on the other side because
473 number, interrupt IN endpoint 0x81 and bulk OUT endpoint 0x01, while the other
480 obtain endpoint addresses, types, and other properties. This allows function
503 device configurations in combination with other functions. This may also be
569 Steering Committee, may allocate other USB Product IDs based on well-motivated
/Zephyr-latest/drivers/serial/
DKconfig.nrfx43 enhancement compared to other two modes (default and hardware assisted).
/Zephyr-latest/boards/shields/ls0xx_generic/doc/
Dindex.rst11 few other pins. Note that the SCS is active high for this display.
/Zephyr-latest/drivers/flash/
DKconfig.nrf56 to perform other task by MCU.
/Zephyr-latest/doc/develop/languages/c/
Dminimal_libc.rst53 other de-facto standard sources have been added to the minimal libc.
/Zephyr-latest/boards/ronoth/lodev/
Dronoth_lodev.dts28 * On Ronoth LoDev and perhaps other boards,
/Zephyr-latest/samples/shields/x_nucleo_iks01a3/standard/
DREADME.rst47 In addition to sensors on board it is possible to place any other compatible
/Zephyr-latest/samples/boards/espressif/flash_memory_mapped/
DREADME.rst36 To check the output of this sample, run ``west espressif monitor`` or any other serial
/Zephyr-latest/drivers/ethernet/
DKconfig.nxp_s32_netc36 work to do. This is to prevent the RX thread to starve other threads. Each
/Zephyr-latest/samples/drivers/ipm/ipm_imx/
DREADME.rst30 it back. The other core is usually not running Zephyr but Linux on i.MX

1...<<11121314151617181920>>...33