User's Guide

Getting Started
EZ-Serial BLE Firmware Platform User Guide, Doc. No. 002-11259 Rev. *E 15
Figure 2-2. Text Command Mode Session with PuTTY
Table 2-3 describes the various protocol methods shown in the figure above.
Table 2-3. Text Mode Communication Example
Direction Content Detail
←RX
@E,003B,BOOT,E=0101011A,S=03030035,
P=0103,H=05,C=01,A=00A050421A63
system_boot (BOOT, ID=2/1) API event received:
app = 1.1.1 build 26
stack = 3.3.0 build 53
protocol = 1.3
hardware = CYBLE-2120XX-X0 module
boot cause = power-on/XRES
MAC address = 00:A0:50:42:1A:63
←RX
@E,000E,ASC,S=01,R=03
gap_adv_state_changed (ASC, ID=4/2) API event received:
state = 1 (active)
reason = 3 (CYSPP operation)
TX→
/ping
system_ping (/PING, ID=2/1)
API command sent to ping the local
module to verify proper communication
←RX
@R,001D,/PING,0000,R=00000003,F=32D1
system_ping (/PING, ID=2/1) API response received:
result = 0 (success)
runtime = 3 seconds
fraction = 13009/32768 seconds
TX→
gdn
gap_get_device_name (GDN, ID=4/16) API command sent to get
the configured device name
←RX
@R,001E,GDN,0000,N=EZ-Serial 42:1A:63
gap_get_device_name (GDN, ID=4/16) API response received:
result = 0 (success)
name = “EZ-Serial 42:1A:63”
←RX
@E,0035,C,C=04,A=00A050421650,
T=00,I=0006,L=0000,O=0064,B=00
gap_connected (C, ID=4/5) API event received:
conn_handle = 4
peer = 00:A0:50:42:16:50
addr_type = 0 (public)
interval = 6 (7.5ms)
slave_latency = 0
supervision_timeout = 0x64 (100 = 1 second)
bond = 0 (not bonded)
←RX
@E,001E,W,C=04,H=001F,T=00,
D=11223344
gatts_data_written (W, ID=5/2) API event received:
conn_handle = 4
attr_handle = 0x1F (31)
type = 0 (simple write)
data = 4 bytes
[11 22 33 44]
TX→
badcmd
Invalid API command sent to demonstrate text mode error event
←RX
@E,000B,ERR,0203
system_error (ERR, ID=2/2) API event received:
reason = 0x0203 (Unrecognized Command)
Refer to the reference material in Chapter 7 (API Protocol Reference) for details on each of these API methods and text-
mode syntax rules.