Searched refs:some (Results 251 – 275 of 591) sorted by relevance
1...<<11121314151617181920>>...24
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | provisioning.rst | 43 may be specified, which can point the provisioner to the location of some Out
126 production, which the provisioner can query in some application specific
|
| /Zephyr-latest/kernel/ |
| D | Kconfig.vm | 37 base addresses being aligned to some common value (which allows
157 ensure that there are some page frames available for paging
|
| /Zephyr-latest/doc/build/sysbuild/ |
| D | index.rst | 25 The following are some key concepts used in this document:
53 The following are some key sysbuild features indicated in this figure:
63 sysbuild can direct them to the right build system. In some cases, such as
730 be configured or flashed in a specific order. For example, if you need some
750 (in some order) before doing the same for ``my_sample``, when building these
760 (in some order), when flashing these domains in a single invocation.
|
| /Zephyr-latest/doc/services/zbus/ |
| D | index.rst | 91 The above figure illustrates some states, from (a) to (d), for channels from ``C1`` to ``C5``,
187 In the figure below, the letters indicate some action related to the VDED execution. The X-axis
214 - T1 starts and, at some point, publishes to channel A.
271 - T1 starts and, at some point, publishes to channel A.
380 Based on the fact that developers can use zbus to solve many different problems, some challenges
394 * Keep the listeners quick-as-possible (deal with them as ISRs). If some processing is needed,
530 allows original creators of a channel to exert some authority over other developers/publishers who
733 ZBus was designed to be as flexible and extensible as possible. Thus, there are some features
734 designed to provide some control and extensibility to the bus.
|
| /Zephyr-latest/doc/build/dts/ |
| D | howtos.rst | 87 works best for your requirements. Here are some examples:
124 In some situations the device cannot be known at build-time, e.g., if it depends
152 devicetree. In some situations your code will compile but it will fail to link
277 -- Found devicetree overlay: .../some/file.overlay
346 /delete-property/ some-unwanted-property;
|
| /Zephyr-latest/arch/ |
| D | Kconfig | 161 # This is due to some tests using _Static_assert which is a 2011 feature, but
163 # This was in general ok, but with some host compilers and C library versions
466 Enable installation of interrupts at runtime, which will move some
468 on some architectures increase code size.
561 On some architectures, part of the vector table may be reserved for
1002 Note that some compiler configurations may activate a floating point
1051 This option enables querying some architecture-specific hardware for
1074 This option enables querying some architecture-specific hardware for
|
| /Zephyr-latest/samples/subsys/zbus/remote_mock/ |
| D | README.rst | 11 …en, the script sends back information when it would simulate a publish to some channel. Finally, t…
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | coap_client.rst | 53 - The request failed for some reason
|
| /Zephyr-latest/doc/connectivity/networking/ |
| D | networking_with_host.rst | 35 in some cases, you might need to use the SLIP method for host connectivity.
|
| /Zephyr-latest/boards/vngiotlab/nrf51_vbluno51/doc/ |
| D | index.rst | 126 Here are some sample applications that you can use to test different
|
| /Zephyr-latest/boards/shields/x_nucleo_idb05a1/doc/ |
| D | index.rst | 47 Additionally, depending on your host board, some modifications of the BLE
|
| /Zephyr-latest/doc/safety/ |
| D | safety_requirements.rst | 44 In other words a person writing these requirements usually has some knowledge of the Zephyr RTOS
|
| /Zephyr-latest/doc/build/kconfig/ |
| D | preprocessor-functions.rst | 122 Assume that the devicetree for some board looks like this:
|
| /Zephyr-latest/doc/connectivity/bluetooth/ |
| D | bluetooth-le-host.rst | 78 There are some sample applications for the central role available in the
111 Man-In-The-Middle (MITM) attacks, it is recommended to use some
117 device lacks some feature the corresponding callback may be set to NULL.
|
| /Zephyr-latest/doc/develop/debug/ |
| D | index.rst | 292 There is a possibility to log all or some of the I2C transactions done by the application.
342 display0: some-display@a {
345 sensor3: some-sensor@b {
|
| /Zephyr-latest/doc/develop/languages/cpp/ |
| D | index.rst | 153 challenging. The purpose of this section is to document some best "header
164 enforces policies and maintains such combinatorial explosions under some
239 Some pre-C11 GCC versions support some form of anonymous unions. They
|
| /Zephyr-latest/doc/develop/west/ |
| D | build-flash-debug.rst | 99 Here are some ``west build`` usage examples, grouped by area.
184 Using ``--pristine=auto`` makes ``west build`` detect some of these situations
503 west flash --hex-file path/to/some/other.hex
512 example, some runners support an ``--erase`` flag, which mass-erases
617 west debug --elf-file path/to/some/other.elf
618 west debugserver --elf-file path/to/some/other.elf
627 example, some runners support flags which allow you to set the network
|
| /Zephyr-latest/boards/shields/esp_8266/doc/ |
| D | index.rst | 66 present some tips to easily success. The ESP WIFI was tested with an ESP-01
|
| /Zephyr-latest/share/zephyr-package/cmake/ |
| D | zephyr_package_search.cmake | 13 # For Zephyr 3.0 and earlier, the Zephyr_DIR might in some cases be
|
| /Zephyr-latest/doc/connectivity/bluetooth/shell/audio/ |
| D | bap_broadcast_assistant.rst | 5 Note that in the examples below, some lines of debug have been
|
| /Zephyr-latest/doc/hardware/arch/ |
| D | arc-support-status.rst | 9 This page describes current state of Zephyr for ARC processors and some future
|
| /Zephyr-latest/doc/hardware/peripherals/sensor/ |
| D | index.rst | 24 Using sensors from an application there are some APIs and terms that are helpful
|
| /Zephyr-latest/samples/drivers/ethernet/eth_ivshmem/ |
| D | README.rst | 18 some fixes that are not yet on the "master" branch:
|
| /Zephyr-latest/boards/ronoth/lodev/doc/ |
| D | index.rst | 22 The embedded STMicro STM32L073RZ has some GPIOs and SPI2 internally committed to the LoRaWAN
|
| /Zephyr-latest/cmake/linker/armlink/ |
| D | target.cmake | 105 # address which in some cases leads to overlapping section errors.
|
1...<<11121314151617181920>>...24
