User's Guide
Table Of Contents
- 1. Introduction
- 2. Getting Started
- 3. Operational Examples
- 3.1 System Setup Examples
- 3.2 Cable Replacement Examples with CYSPP
- 3.3 Remote Control Examples with CYCommand
- 3.4 GAP Peripheral Examples
- 3.5 GAP Central Examples
- 3.6 GATT Server Examples
- 3.7 GATT Client Examples
- 3.8 Security and Encryption Examples
- 3.9 Beacon Examples
- 3.10 Performance Testing Examples
- 3.11 Device Firmware Update Examples
- 4. Application Design Examples
- 5. Host API Library
- 6. Troubleshooting
- 7. API Protocol Reference
- 8. GPIO Reference
- 9. Cypress GATT Profile Reference
- 10. Configuration Example Reference
- Revision History
API Protocol Reference
EZ-Serial BLE Firmware Platform User Guide, Doc. No. 002-11259 Rev. *E 205
7.3.7.6 smp_passkey_entry_requested (PKE, ID=7/6)
Remote peer requested passkey entry during pairing.
This event indicates that a remote device has generated and displayed a passkey which must be entered locally and sent
back for comparison. If this occurs, you must reply with the smp_send_passkeyreq_response (/PE, ID=7/6) API
command. If the pairing process completes successfully, EZ-Serial will generate the smp_pairing_result (PR, ID=7/3) API
event with a success result code (0).
Binary Header:
Type
Length
Group
ID
Notes
80
01
07
06
None.
Text Info:
Text Name
Event Length
Notes
PKE
0x0009
None.
Event Parameters:
Data Type
Name
Text
Description
uint8
conn_handle
C
Connection handle
Related Commands:
• smp_send_passkeyreq_response (/PE, ID=7/6)
Related Events:
• smp_pairing_requested (P, ID=7/2)
• smp_pairing_result (PR, ID=7/3)
• smp_passkey_display_requested (PKD, ID=7/5)
7.3.8 L2CAP Group (ID=8)
L2CAP methods relate to the Logical Link Control and Adaptation Protocol layer of the Bluetooth stack. These methods
are used for working directly with low-level data transfer between two connected devices.
NOTE: L2CAP communication features within EZ-Serial are only available on devices with 256k of flash
memory. The API methods described in this section will not function on devices with only 128k of flash.
Events within this group are listed below:
• l2cap_connection_requested (LCR, ID=8/1)
• l2cap_connection_response (LC, ID=8/2)
• l2cap_data_received (LD, ID=8/3)
• l2cap_disconnected (LDIS, ID=8/4)
• l2cap_rx_credits_low (LRCL, ID=8/5)
• l2cap_tx_credits_received (LTCR, ID=8/6)
• l2cap_command_rejected (LREJ, ID=8/7)
Commands within this group are documented in Section 7.2.8, L2CAP Group (ID=8).
7.3.8.1 l2cap_connection_requested (LCR, ID=8/1)
Received an L2CAP connection request.
NOTE: L2CAP communication features within EZ-Serial are only available on devices with 256K of
flash memory. The behavior described in this section will not function on devices with only 128K of
flash.
Binary Header:
Type
Length
Group
ID
Notes
80
0B
08
01
None.