Searched refs:protocols (Results 51 – 72 of 72) sorted by relevance
123
| /Zephyr-latest/doc/kernel/usermode/ |
| D | overview.rst | 21 protocols, and filesystems such that malicious third-party code or data
|
| /Zephyr-latest/doc/ |
| D | glossary.rst | 12 (Application Program Interface) A defined set of routines and protocols for
|
| /Zephyr-latest/boards/ti/cc3235sf_launchxl/doc/ |
| D | index.rst | 40 offloads Wi-Fi and internet protocols from the application MCU.
|
| /Zephyr-latest/doc/develop/test/ |
| D | bsim.rst | 9 In the Zephyr project we use the `Babblesim`_ simulator to test some of the Zephyr radio protocols,
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | sockets.rst | 73 protocols with standard socket calls. See :c:enum:`net_ip_protocol_secure` type
|
| /Zephyr-latest/doc/connectivity/bluetooth/ |
| D | bluetooth-le-host.rst | 6 The Bluetooth Host implements all the higher-level protocols and
|
| /Zephyr-latest/doc/security/ |
| D | secure-coding.rst | 118 to be explicitly enabled. Then, all features, protocols, and drivers
|
| D | sensor-threat.rst | 412 protocols and routing issues on various networks.
|
| /Zephyr-latest/boards/st/steval_stwinbx1/doc/ |
| D | index.rst | 21 NFC or USB protocols to a host application running on a smartphone/PC to implement applications suc…
|
| /Zephyr-latest/boards/st/sensortile_box_pro/doc/ |
| D | index.rst | 20 sensor data through either the BLE or USB protocols to a host application running
|
| /Zephyr-latest/doc/security/standards/ |
| D | etsi-303645.rst | 459 network service protocols that are relied upon by the device and where the manufacturer
|
| /Zephyr-latest/doc/develop/flash_debug/ |
| D | probes.rst | 16 connect to the device running Zephyr using the JTAG or SWD protocols. Debug
|
| /Zephyr-latest/doc/build/dts/ |
| D | bindings-syntax.rst | 529 For a single bus supporting multiple protocols, e.g. I3C and I2C, the ``bus:``
|
| /Zephyr-latest/doc/releases/ |
| D | release-notes-1.7.rst | 213 * ``ZEP-847`` - Network protocols must be moved to subsys/net/lib
|
| D | release-notes-3.6.rst | 137 based on ST SPI protocols V1 and V2. As a result, :dtcompatible:`st,hci-spi-v1` and
|
| D | release-notes-1.14.rst | 463 API and moved the majority of components and protocols to use the
829 * New BSD socket based APIs were created for these components and protocols:
|
| D | release-notes-3.7.rst | 334 by :kconfig:option:`CONFIG_BT_AVDTP`. They implement the protocols and procedures that
|
| D | release-notes-2.0.rst | 435 Zephyr Vendor Specific Commands, and user-defined protocols
|
| D | release-notes-2.4.rst | 1644 * :github:`23949` - Question: Is there any example for BR/EDR profile/protocols (like A2DP, AVDTP, …
|
| D | release-notes-3.2.rst | 1039 it represents hardware which can communicate over multiple bus protocols.
|
| /Zephyr-latest/subsys/net/ip/ |
| D | Kconfig | 982 a network packet or for timed radio protocols like IEEE 802.15.4
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/audio/ |
| D | bluetooth-le-audio-arch.rst | 13 {{{ GATT | GAP } | Low-level protocols (L2CAP, ATT, etc.)} | GAP | ISO}
|
123
