Searched refs:ATT (Results 1 – 25 of 30) sorted by relevance
12
| /Zephyr-latest/subsys/bluetooth/host/ |
| D | Kconfig.gatt | 1 # Bluetooth ATT/GATT configuration options
6 menu "ATT and GATT Options"
9 bool "Print ATT error codes as strings [EXPERIMENTAL]"
12 This configuration enables printing of ATT error
17 int "Number of ATT buffers"
22 These buffers are only used for sending anything over ATT.
26 int "Number of ATT prepare write buffers"
30 Number of buffers available for ATT prepare write, setting
38 If an ATT request fails due to insufficient security, the host will
39 try to elevate the security level and retry the ATT request.
[all …]
|
| D | Kconfig.l2cap | 1 # Bluetooth ATT/GATT configuration options
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/ |
| D | att.rst | 3 Attribute Protocol (ATT)
|
| D | gatt.rst | 52 to 128-bit UUIDs when the UUID is contained in an ATT PDU.
|
| /Zephyr-latest/samples/bluetooth/mtu_update/ |
| D | README.rst | 10 Question: What do I have to do to update my ATT MTU?
12 | Answer: To get an ATT MTU of x octets, do the following:
25 Answer: Yes. [#mtu_exchange]_ The Bluetooth specification mandates a symmetric MTU for ATT.
|
| /Zephyr-latest/doc/connectivity/bluetooth/ |
| D | bluetooth-le-host.rst | 275 ATT timeout
278 If the peer device does not respond to an ATT request (such as read or write)
279 within the ATT timeout, the host will automatically initiate a disconnect. This
282 special cases for ATT timeouts.
286 :alt: ATT timeout
|
| D | features.rst | 66 * Enhanced ATT (EATT)
|
| D | bluetooth-arch.rst | 189 the core protocols such as L2CAP, ATT, and SMP is also here.
|
| /Zephyr-latest/doc/releases/ |
| D | release-notes-1.6.rst | 300 * ``ZEP-940`` - Fail to get ATT response
313 * ``ZEP-1074`` - ATT retrying misbehaves when ATT insufficient Authentication is received
337 * ``ZEP-1195`` - Wrong ATT error code passed to the application
|
| D | release-notes-2.1.rst | 463 * :github:`21177` - Long ATT MTU reports wrong length field in write callback.
472 * :github:`21059` - Bluetooth sent callback delayed more than ATT
486 * :github:`20938` - ATT/L2CAP "deadlock"
690 * :github:`19604` - Bluetooth: ATT does not release all buffers on disconnect
|
| D | migration-guide-3.6.rst | 454 * ATT now has its own TX buffer pool.
455 If extra ATT buffers were configured using :kconfig:option:`CONFIG_BT_L2CAP_TX_BUF_COUNT`,
|
| D | release-notes-1.8.rst | 122 * Host: Added ATT and SMP packet tracking for flow control enforcement
|
| D | release-notes-2.4.rst | 693 * Fixed a regression introduced in 2.3 along the EATT feature, where the ATT
1420 * :github:`26278` - [v2.2] bt_att: Unhandled ATT code 0x1d
1463 * :github:`26071` - Bluetooth: host: ATT sent callback lost
1464 * :github:`26070` - Bluetooth: ATT request not processed
1490 * :github:`25964` - Bluetooth: <err> bt_att: ATT Timeout
|
| D | release-notes-4.0.rst | 190 * Added API :c:func:`bt_gatt_get_uatt_mtu` to get current Unenhanced ATT MTU of a given
196 * The host now disconnects from the peer upon ATT timeout.
|
| D | release-notes-2.5.rst | 964 * :github:`28685` - Bluetooth: Characteristic unsubscribe under indication load results in ATT time…
1243 * :github:`30624` - BLE : ATT Timeout occurred during multilink central connection
1571 * :github:`29098` - ATT timeout worker not canceled by destroy, and may operate on disposed object
|
| D | release-notes-3.3.rst | 2719 …:`53475` - The ATT_MTU value for EATT should be set as the minimum MTU of ATT Client and ATT Server
3094 * :github:`53247` - ATT timeout followed by a segmentation fault
3256 …:`52228` - Bluetooth: L2CAP: receive a K-frame with payload longer than MPS if Enhanced ATT enabled
|
| D | release-notes-1.12.rst | 769 * :github:`8083` - Bluetooth ATT trying to access invalid pointer after disconnect
|
| D | release-notes-2.2.rst | 1033 * :github:`21177` - Long ATT MTU reports wrong length field in write callback.
|
| D | release-notes-3.0.rst | 992 * :github:`41794` - Bluetooth: ATT calls GATT callbacks with NULL conn pointer during disconnect
|
| /Zephyr-latest/doc/connectivity/bluetooth/shell/audio/ |
| D | mcp.rst | 176 being too long to fit in the ATT packet. Increasing the ATT MTU may
|
| /Zephyr-latest/boards/st/stm32wb5mm_dk/doc/ |
| D | stm32wb5mm_dk.rst | 82 - Support EATT (enhanced ATT)
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/audio/ |
| D | bluetooth-le-audio-arch.rst | 13 {{{ GATT | GAP } | Low-level protocols (L2CAP, ATT, etc.)} | GAP | ISO}
1198 as ATT does not have a specific error code for missing OOB method or LE Secure Connections
1219 at least 64 on the unenhanced ATT bearer or at least one enhanced ATT bearer.
|
| /Zephyr-latest/boards/st/stm32wb5mmg/doc/ |
| D | stm32wb5mmg.rst | 64 - Support EATT (enhanced ATT)
|
| /Zephyr-latest/subsys/bluetooth/ |
| D | Kconfig.logging | 60 module-str = "Bluetooth Attribute Protocol (ATT)"
|
| /Zephyr-latest/doc/security/ |
| D | vulnerabilities.rst | 931 Disconnecting L2CAP channel right after invalid ATT request leads freeze
934 connection for Enhanced ATT, sending some invalid ATT request and
|
12
