GAP#

The Generic Access Profile (GAP) defines how Bluetooth Low Energy (BLE) devices discover each other, advertise, scan, establish links, and manage connection parameters and PHY on the connection. The pages linked below cover GAP roles (peripheral, central, broadcaster, observer), extended and periodic advertising, LE privacy, and data length extension (DLE). Stack-wide context—supported roles, operating modes, PHY overview, and connection or advertising limits—is in BLE architecture and BLE initialization and configuration.

Pages in This Section#


Page	Description
Peripheral role	Legacy and extended advertising, connection procedures from the peripheral, connection parameters, power save while connected
Central role	Scanning, connection initiation, GAP-side multiple connections, central power considerations
Broadcaster role	Non-connectable advertising and beacon-style use cases
Observer role	Receiving advertising and periodic advertising sync (observer path)
Extended advertising	Extended advertising sets, periodic advertising procedures (advanced detail)
Data length extension	DLE, link-layer payload size vs ATT MTU
LE Privacy	Resolvable private addresses and privacy-related GAP behavior
GAP usage scenarios	Step-by-step flows for common GAP-focused setups

Debugging (GAP)#

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 GAP work):


Area	Reference
GAP — procedures, parameters, PHY on connection	GAP
Register GAP / SMP / 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.