Texas Instruments CC2540

www.ti.com Client Commands
127
SWRU271H–October 2010–Revised April 2019
Submit Documentation Feedback
Copyright © 2010–2019, Texas Instruments Incorporated
GATT/ATT API
bStatus_t GATT_ReadUsingCharUUID ( uint16 connHandle, attReadByTypeReq_t *pReq, uint8
taskId )
Used to read a Characteristic Value from a server when the client only knows the
characteristic UUID and does not know the handle of the characteristic.
Parameters connHandle: connection to use
pReq: pointer to request to be sent
taskId: task to be notified of response
Notes If the return status is SUCCESS, the calling application task receives an OSAL
GATT_MSG_EVENT message with type ATT_READ_BY_TYPE_RSP or
ATT_ERROR_RSP (if an error occurred on the server). This sub-procedure is complete
when either ATT_READ_BY_TYPE_RSP (with SUCCESS or bleTimeout status) or the
calling application task receives the ATT_ERROR_RSP (with SUCCESS status).
bStatus_t GATT_ReadLongCharValue ( uint16 connHandle, attReadBlobReq_t *pReq, uint8
taskId )
Used to read a Characteristic Value from a server when the client knows the
Characteristic Value Handle and the length of the Characteristic Value is longer
than can be sent in a single Read Response Attribute Protocol message.
Parameters connHandle: connection to use
pReq: pointer to request to be sent
taskId: task to be notified of response
Notes If the return status is SUCCESS, the calling application task receives multiple
GATT_MSG_EVENT messages with type ATT_READ_BLOB_RSP or
ATT_ERROR_RSP (if an error occurred on the server). This sub-procedure is complete
when either ATT_READ_BLOB_RSP (with bleProcedureComplete or bleTimeout status)
or the calling application task receives the ATT_ERROR_RSP (with SUCCESS status).
bStatus_t GATT_ReadMultiCharValues ( uint16 connHandle, attReadMultiReq_t *pReq, uint8
taskId )
Used to read multiple Characteristic Values from a server when the client knows
the Characteristic Value Handles.
Parameters connHandle: connection to use
pReq: pointer to request to be sent
taskId: task to be notified of response
Notes If the return status from this function is SUCCESS, the calling application task receives
an OSAL GATT_MSG_EVENT message with type ATT_READ_MULTI_RSP or
ATT_ERROR_RSP (if an error occurred on the server). This sub-procedure is complete
when either ATT_READ_MULTI_RSP (with SUCCESS or bleTimeout status) or the
calling application task receives the ATT_ERROR_RSP (with SUCCESS status).