Data Structures
struct	_evt_gap_pairing_cmplt

struct	_evt_gap_pass_key_req

struct	_evt_gap_author_req

struct	_evt_gap_device_found

struct	_evt_gap_procedure_complete

struct	_evt_gap_addr_not_resolved_IDB05A1

struct	_evt_gap_reconnection_addr_IDB04A1

Macros
#define	EVT_BLUE_GAP_LIMITED_DISCOVERABLE (0x0400)

#define	EVT_BLUE_GAP_PAIRING_CMPLT (0x0401)

#define	EVT_BLUE_GAP_PASS_KEY_REQUEST (0x0402)

#define	EVT_BLUE_GAP_AUTHORIZATION_REQUEST (0x0403)

#define	EVT_BLUE_GAP_SLAVE_SECURITY_INITIATED (0X0404)

#define	EVT_BLUE_GAP_BOND_LOST (0X0405)

#define	EVT_BLUE_GAP_DEVICE_FOUND (0x0406)

#define	EVT_BLUE_GAP_PROCEDURE_COMPLETE (0x0407)

#define	EVT_BLUE_GAP_ADDR_NOT_RESOLVED_IDB05A1 (0x0408)

#define	EVT_BLUE_GAP_RECONNECTION_ADDRESS_IDB04A1 (0x0408)

Typedefs
typedef __packed struct _evt_gap_pairing_cmplt	evt_gap_pairing_cmplt

typedef __packed struct _evt_gap_pass_key_req	evt_gap_pass_key_req

typedef __packed struct _evt_gap_author_req	evt_gap_author_req

typedef __packed struct _evt_gap_device_found	evt_gap_device_found

typedef __packed struct _evt_gap_procedure_complete	evt_gap_procedure_complete

typedef __packed struct _evt_gap_addr_not_resolved_IDB05A1	evt_gap_addr_not_resolved_IDB05A1

typedef __packed struct _evt_gap_reconnection_addr_IDB04A1	evt_gap_reconnection_addr_IDB04A1

Detailed Description

Macro Definition Documentation

◆ EVT_BLUE_GAP_ADDR_NOT_RESOLVED_IDB05A1

#define EVT_BLUE_GAP_ADDR_NOT_RESOLVED_IDB05A1 (0x0408)

This event is sent only by a privacy enabled Peripheral. The event is sent to the upper layers when the peripheral is not able to resolve the private address of the peer device after connecting to it.

◆ EVT_BLUE_GAP_AUTHORIZATION_REQUEST

#define EVT_BLUE_GAP_AUTHORIZATION_REQUEST (0x0403)

This event is generated by the Security manager to the application when the application has set that authorization is required for reading/writing of attributes. This event will be generated as soon as the pairing is complete. When this event is received, aci_gap_authorization_response() command should be used by the application. See _evt_gap_author_req.

◆ EVT_BLUE_GAP_BOND_LOST

#define EVT_BLUE_GAP_BOND_LOST (0X0405)

This event is generated on the slave when a aci_gap_slave_security_request() is called to reestablish the bond with a master but the master has lost the bond. When this event is received, the upper layer has to issue the command aci_gap_allow_rebond() in order to allow the slave to continue the pairing process with the master. On the master this event is raised when aci_gap_send_pairing_request() is called to reestablish a bond with a slave but the slave has lost the bond. In order to create a new bond the master has to launch aci_gap_send_pairing_request() with force_rebond set to 1. No parameters for this event

◆ EVT_BLUE_GAP_DEVICE_FOUND

#define EVT_BLUE_GAP_DEVICE_FOUND (0x0406)

The event is given by the GAP layer to the upper layers when a device is discovered during scanning as a consequence of one of the GAP procedures started by the upper layers. See _evt_gap_device_found.

◆ EVT_BLUE_GAP_LIMITED_DISCOVERABLE

#define EVT_BLUE_GAP_LIMITED_DISCOVERABLE (0x0400)

This event is generated by the controller when the limited discoverable mode ends due to timeout (180 seconds). No parameters in the event.

◆ EVT_BLUE_GAP_PAIRING_CMPLT

#define EVT_BLUE_GAP_PAIRING_CMPLT (0x0401)

This event is generated when the pairing process has completed successfully or a pairing procedure timeout has occurred or the pairing has failed. This is to notify the application that we have paired with a remote device so that it can take further actions or to notify that a timeout has occurred so that the upper layer can decide to disconnect the link. See _evt_gap_pairing_cmplt.

◆ EVT_BLUE_GAP_PASS_KEY_REQUEST

#define EVT_BLUE_GAP_PASS_KEY_REQUEST (0x0402)

This event is generated by the Security manager to the application when a pass key is required for pairing. When this event is received, the application has to respond with the aci_gap_pass_key_response() command. See _evt_gap_pass_key_req.

◆ EVT_BLUE_GAP_PROCEDURE_COMPLETE

#define EVT_BLUE_GAP_PROCEDURE_COMPLETE (0x0407)

This event is sent by the GAP to the upper layers when a procedure previously started has been terminated by the upper layer or has completed for any other reason. See _evt_gap_procedure_complete.

◆ EVT_BLUE_GAP_RECONNECTION_ADDRESS_IDB04A1

#define EVT_BLUE_GAP_RECONNECTION_ADDRESS_IDB04A1 (0x0408)

This event is raised when the reconnection address is generated during the general connection establishment procedure. The same address is set into the peer device also as a part of the general connection establishment procedure. In order to make use of the reconnection address the next time while connecting to the bonded peripheral, the application needs to use this reconnection address as its own address as well as the peer address to which it wants to connect. See aci_gap_start_general_conn_establish_proc() and aci_gap_start_auto_conn_establish_proc().