Searched refs:either (Results 276 – 300 of 370) sorted by relevance
1...<<1112131415
/Zephyr-latest/doc/connectivity/networking/conn_mgr/ |
D | implementation.rst | 224 …ld asynchronously wait for valid connection parameters to be configured, either indefinitely, or u… 240 * Set the iface either to dormant or to carrier-down as soon as interruption of service is detected.
|
/Zephyr-latest/boards/st/stm32h747i_disco/doc/ |
D | index.rst | 161 using either ``stm32h747i_disco/stm32h747xx/m7`` or ``stm32h747i_disco/stm32h747xx/m4``
|
/Zephyr-latest/doc/connectivity/networking/api/ |
D | net_l2.rst | 143 the network packet only when the transmission as a whole was either successful
|
/Zephyr-latest/boards/espressif/esp32s3_eye/doc/ |
D | index.rst | 54 …SB power is connected to the board. If it is not turned on, it indicates either the USB power is n…
|
/Zephyr-latest/boards/nxp/s32z2xxdc2/doc/ |
D | index.rst | 287 either in lock-step or split-lock mode. By default, Zephyr runs on the first
|
/Zephyr-latest/boards/nordic/nrf5340dk/doc/ |
D | index.rst | 184 image for the application core. The Secure image can be built using either
|
/Zephyr-latest/doc/kernel/usermode/ |
D | overview.rst | 153 another thread that is either in supervisor mode or has permission on both
|
/Zephyr-latest/doc/develop/test/ |
D | bsim.rst | 173 as either helper functions for the main script, or can be used for local development utilities, e.g.
|
/Zephyr-latest/boards/st/stm32wb5mmg/doc/ |
D | stm32wb5mmg.rst | 166 a valid STM32WB Coprocessor binaries (either 'Full stack' or 'HCI Layer').
|
/Zephyr-latest/samples/net/lwm2m_client/ |
D | README.rst | 195 To join into already existing OT network, either enable CONFIG_OPENTHREAD_JOINER=y
|
/Zephyr-latest/boards/native/native_sim/doc/ |
D | index.rst | 166 This target requires either a 64 bit system with multilib support installed or 185 When building with either :ref:`minimal <c_library_minimal>` or :ref:`Picolibc<c_library_picolibc>` 523 This can be done in two ways, either with the command line option ``--<uart_name>_stdinout``
|
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
D | dfu.rst | 201 the device may either boot up unprovisioned after applying the new firmware or require to be 277 send the image to. The Initiator gets the full list of Target nodes either by querying the potential
|
/Zephyr-latest/doc/build/dts/ |
D | howtos.rst | 173 to obtain a reference at runtime. If it returns ``NULL`` it can either mean that 421 In either case:
|
/Zephyr-latest/cmake/modules/ |
D | kconfig.cmake | 46 # KCONFIG_ROOT has either been specified as a CMake variable or is
|
/Zephyr-latest/doc/connectivity/bluetooth/ |
D | bluetooth-arch.rst | 167 SPI), while the Controller build runs either the
|
D | bluetooth-le-host.rst | 106 called pairing is used. This process can either be triggered implicitly
|
/Zephyr-latest/boards/nordic/nrf7002dk/doc/ |
D | index.rst | 188 image for the application core. The Secure image can be built using either
|
/Zephyr-latest/arch/arc/ |
D | Kconfig | 238 This option enables either:
|
/Zephyr-latest/doc/develop/west/ |
D | config.rst | 185 matches the regular expression, that element of the list either
|
/Zephyr-latest/boards/arm/v2m_musca_b1/doc/ |
D | index.rst | 261 DAPLink firmware for either QSPI or eFlash for booting.
|
/Zephyr-latest/doc/kernel/memory_management/ |
D | heap.rst | 42 provided must be either a ``NULL`` value or a pointer previously
|
/Zephyr-latest/boards/snps/em_starterkit/doc/ |
D | index.rst | 186 it either to EM9D or EM11D. To boot up the EM9D on the board, all dip
|
/Zephyr-latest/doc/services/device_mgmt/ |
D | mcumgr_callbacks.rst | 132 Some callbacks expect a return status to either allow or disallow an operation,
|
/Zephyr-latest/boards/arm/v2m_musca_s1/doc/ |
D | index.rst | 255 selector slider switch for either QSPI or eMRAM for booting.
|
/Zephyr-latest/boards/phytec/phyboard_polis/doc/ |
D | index.rst | 9 The phyBOARD-Polis, either a development platform for the
|
1...<<1112131415