www.ti.com
Generic Access Profile (GAP)
31
SWRU271H–October 2010–Revised April 2019
Submit Documentation Feedback
Copyright © 2010–2019, Texas Instruments Incorporated
The Bluetooth Low Energy Protocol Stack
5.2.1.5 Connection Termination
The master or slave can terminate a connection for any reason. When either device initiates termination,
the other must respond by acknowledging the termination indication before both devices disconnect.
5.2.2 GAP Abstraction
The application and profiles can call GAP API functions to perform BLE-related functions such as
advertising or connecting. Most of the GAP functionality is handled by the GAPRole Task. For more
information on this abstraction hierarchy, see Figure 5-4.
Figure 5-4. GAP Abstraction
Configure the GAPRole module and use its APIs to interface with the GAP layer. Section 5.2.3 describes
the functions and parameters not handled or configured through the GAPRole task. These functions and
parameters must be modified directly through the GAP layer.
5.2.3 Configuring the GAP Layer
The GAP layer functionality is defined mostly in library code. You can find the function headers in gap.h.
Most of these functions are used by the GAPRole task and do not need to be called directly. Appendix A
defines the GAP API. You may want to modify several parameters before starting the GAPRole task.
These parameters can be set or retrieved through the GAP_SetParamValue() and GAP_GetParamValue()
functions. These parameters include advertising and scanning intervals, windows, and so forth (see B and
C [GAPRole xxx API). A configuration of the GAP layer in SimpleBLEPeripheral_init() folows.
To Next Page
Loading...
Need help?
General
