Searched refs:been (Results 251 – 275 of 466) sorted by relevance
1...<<111213141516171819
| /Zephyr-latest/samples/subsys/fs/littlefs/ |
| D | README.rst | 80 This example has been devised and initially tested on :zephyr:board:`nucleo_h743zi`
|
| /Zephyr-latest/boards/snps/nsim/arc_v/doc/ |
| D | index.rst | 51 ``zephyr`` toolchain support because corresponding target CPU support hasn't been added to Zephyr 128 Now the debug environment has been set up, and it's possible to debug the application with gdb
|
| /Zephyr-latest/subsys/mgmt/mcumgr/grp/img_mgmt/ |
| D | Kconfig | 90 erasing slots that have been set for next boot but the device has not 91 reset yet, so has not yet been swapped.
|
| /Zephyr-latest/drivers/wifi/esp32/ |
| D | Kconfig.esp32 | 125 The buffer is freed after the data frame has been sent by the WiFi driver. 200 …received. The MGMT buffer is freed after the MGMT data frame has been processed by the WiFi driver. 322 Only for station in WIFI_PS_MIN_MODEM or WIFI_PS_MAX_MODEM. If no packet has been
|
| /Zephyr-latest/doc/services/tfm/ |
| D | overview.rst | 10 Zephyr RTOS has been PSA Certified since Zephyr 2.0.0 with TF-M 1.0, and 91 valid, have not been tampered with, and come from a reliable source. The 262 :kconfig:option:`CONFIG_BUILD_WITH_TFM` flag has been enabled.
|
| /Zephyr-latest/doc/security/ |
| D | secure-coding.rst | 8 They have usually been thought of as isolated, disconnected 247 mainline code until the security issues have been addressed. 277 have been resolved.
|
| /Zephyr-latest/boards/nxp/imx93_evk/doc/ |
| D | index.rst | 342 resources to the inmates. The inmates CANNOT use resources such as the CPU that haven't been 366 They will only be aware of the cores they have been assigned through the config 382 This board has been designed for SOF so it's only intended to be used with SOF.
|
| /Zephyr-latest/doc/connectivity/networking/conn_mgr/ |
| D | implementation.rst | 37 …e iterated over to find out what (if any) connectivity implementation has been bound to a given if… 184 …nnectivity implementations will faithfully implement the features that have been delegated to them. 222 …ot give up on the connection attempt, even if valid connection parameters have not been configured. 343 …s that include Connectivity Manager, as well as the iface that would have been bound to the implem…
|
| /Zephyr-latest/doc/build/kconfig/ |
| D | setting.rst | 166 after the main project configuration has been applied and before any board overlay 167 configuration files have been applied. 279 Since the type of the symbol (``int``) has already been given at the first
|
| /Zephyr-latest/doc/services/device_mgmt/smp_groups/ |
| D | smp_group_8.rst | 39 an idle timeout has not been reached and another transport does not make use 168 an idle timeout has not been reached, but files are not exclusively owned by 171 requests (as long as an idle timeout has not been reached and another transport
|
| /Zephyr-latest/boards/u-blox/ubx_evkannab1/doc/ |
| D | index.rst | 74 Other hardware features have not been enabled yet for this board.
|
| /Zephyr-latest/doc/releases/ |
| D | index.rst | 82 Release notes contain a list of changes that have been made to the different
|
| D | release-notes-4.2.rst | 66 * ``arduino_uno_r4_minima`` and ``arduino_uno_r4_wifi`` board targets have been deprecated in favor
|
| /Zephyr-latest/doc/build/flashing/ |
| D | configuration.rst | 44 respective core have been flashed.
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | blob_srv.rst | 49 Once the transfer has been set up on the BLOB Transfer Server, it's ready for receiving the BLOB.
|
| D | blob.rst | 75 BLOB Transfer Client to all targeted BLOB Transfer Servers. Once all chunks in a block have been 82 before requesting more chunks. This repeats until all chunks have been transferred, or the BLOB
|
| /Zephyr-latest/doc/services/net_buf/ |
| D | index.rst | 30 Once the pool has been defined, buffers can be allocated from it with:
|
| /Zephyr-latest/boards/renesas/voice_ra4e1/doc/ |
| D | index.rst | 27 Following is a list of the specific features that have been implemented:
|
| /Zephyr-latest/doc/hardware/peripherals/sensor/ |
| D | read_and_decode.rst | 19 that have been run into with :ref:`sensor-fetch-and-get`.
|
| /Zephyr-latest/doc/kernel/services/data_passing/ |
| D | stacks.rst | 22 * A **queue** of integer data values that have been added but not yet removed.
|
| /Zephyr-latest/tests/bsim/bluetooth/mesh/ |
| D | README.rst | 109 has been called - otherwise, it will fail.
|
| /Zephyr-latest/samples/subsys/modbus/rtu_server/ |
| D | README.rst | 16 This sample has been tested with the nRF52840-DK and FRDM-K64F boards,
|
| /Zephyr-latest/samples/boards/nordic/mesh/onoff-app/ |
| D | README.rst | 41 This sample has been tested on the Nordic nRF52840-PDK board, but would
|
| /Zephyr-latest/samples/boards/nordic/mesh/onoff_level_lighting_vnd_app/ |
| D | README.rst | 59 This sample has been tested on the Nordic nRF52840-PDK board, but would
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | net_l2.rst | 96 After all the network data has been received, the device driver needs to 115 Ethernet. What has been described above, especially for ``recv()``, applies
|
1...<<111213141516171819