Skip to main content

Module client

Module client 

Source
Expand description

NimBLE GATT client: connection, discovery, read/write, and received notifications, as client operations on the BleDriver.

Every ble_gattc_* operation is initiate-now, complete-later: you start it, and NimBLE invokes a callback when it finishes. We route all of those per-operation callbacks through one shared gattc_subscribe hook, correlated by conn_handle (GATT serializes one transaction per connection). Received notifications/indications (GattcEvent::Notify) arrive on the connection’s GAP callback and are demuxed here.

Structs§

GattcChr
A remote characteristic discovered on a peer (safe view of ble_gatt_chr).
GattcService
A remote service discovered on a peer (safe view of ble_gatt_svc).

Enums§

GattcEvent
A GATT-client event, delivered on the host task to the single gattc_subscribe hook.