GATT#

The Generic Attribute Profile (GATT) builds on the Attribute Protocol (ATT) to expose services, characteristics, and descriptors, and to carry application data over an established link. The pages linked below cover GATT server and GATT client flows, MTU and ATT payload limits relative to the link, and SIG/custom profiles. Stack-wide Bluetooth Low Energy (BLE) feature context (GATT alongside GAP) is in BLE architecture; initialization and connection limits that affect concurrent GATT work are in BLE initialization and configuration.

Pages in This Section#


Page	Description
GATT server	Services and attributes, host- vs firmware-maintained database, notifications and indications
GATT client	Discovery, read/write, subscriptions, MTU-related flows, GATT across multiple connections
Profiles	SIG and custom GATT-based profiles
GATT usage scenarios	Step-by-step flows for common GATT-focused setups

Debugging (GATT)#

For systematic troubleshooting, status interpretation, and links to logging or error-handling practice, see Debugging and error handling.

APIs Used in This Section#

Official WiSeConnect BLE API (page-level references for GATT work):


Area	Reference
GATT server — database, ATT responses, notify/indicate	Server
GATT client — asynchronous procedures	Asynchronous Client
GATT client — synchronous procedures; MTU exchange response paths (as documented)	Synchronous Client
MTU exchange and related host paths (as documented)	ATT_MAINTAIN_IN_HOST
Register GATT callback functions	Register Callbacks
Callback typedefs and event-related types	Callbacks Declarations

In-guide: BLE API reference; stack init and limits: BLE initialization and configuration. SDK: Developing with WiSeConnect SDK, BLE API Reference guide — Overview.