123
SWRU271H–October 2010–Revised April 2019
Submit Documentation Feedback
Copyright © 2010–2019, Texas Instruments Incorporated
GATT/ATT API
Appendix D
SWRU271H–October 2010–Revised April 2019
GATT/ATT API
D.1 Overview
This section describes the API of the GATT and ATT layers. The sections are combined because the
procedure is to send GATT commands and receive ATT events in Section 5.5.3.1. The return values for
the commands in this section are in Section D.4. The possible return values are similar for these
commands, so refer to Section D.4.
D.2 Server Commands
bStatus_t GATT_Indication( uint16 connHandle, attHandleValueInd_t *pInd, uint8 authenticated,
uint8 taskId );
Indicates a characteristic value to a client and expect an acknowledgment.
Memory must be allocated or freed based on the results of this command. For
more information, see Section 7.7.
Parameters connHandle: connection to use
pInd: pointer to indication to be sent
authenticated: whether an authenticated link is required
taskId: task to be notified of acknowledgment
Corresponding Events If the return status is SUCCESS, the calling application task will receive a
GATT_MSG_EVENT message with type ATT_HANDLE_VALUE_CFM upon an
acknowledgment. It is only at this point that this subprocedure is considered complete.
bStatus_t GATT_Notification( uint16 connHandle, attHandleValueNoti_t *pNoti, uint8
authenticated )
Notifies a characteristic value to a client. Note that memory must be allocated /
freed based on the results of this command. For more information, see
Section 7.7.
Parameters connHandle: connection to use
pNoti: pointer to notification to be sent
authenticated: whether an authenticated link is required
Corresponding Events If the return status is SUCCESS, the notification has been successfully queued for
transmission.
To Next Page
Loading...
Need help?
General
