EasyManua.ls Logo

TELINK SEMICONDUCTOR TLSR8232 - Find Information Request, Find Information Response

Default Icon
211 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
Telink TLSR8232 BLE SDK Developer Handbook
AN-19112700-E1 102 Ver.1.0.0
Figure 3-37 Read by Type Request/Read by Type Response
As shown above, Master reads the Attribute with attType of 0x2A00, i.e. the Attribute with
Attribute Handle of 00 03 in Slave.
const u8 my_devName [] = {'t', 'S', 'e', 'l', 'f', 'i'};
#define GATT_UUID_DEVICE_NAME 0x2a00
const u16 my_devNameUUID = GATT_UUID_DEVICE_NAME;
{0,2,sizeof (my_devName), sizeof (my_devName),(u8*)(&my_devNameUUID),
(u8*)(my_devName),
0},
In the “Read by Type response”, attData length is 8, the first two bytes are current
attHandle “0003”, followed by 6-byte Attribute Value.
3.4.3.4 Find Information Request, Find Information Response
Please refer to Core_v5.0 (Vol 3/Part F/3.4.3.1 and 3.4.3.2) for details aboutFind
information request” and “Find information response”.
The “Find information request” command sent by Master specifies starting and ending
attHandle. After the request is received, Slave will respond to Master with Attribute
UUIDs according to the specified starting and ending attHandle via the Find information
response”. As shown below, Master requests for information of three Attributes with
attHandle of 0x0016~0x0018, and Slave responds with corresponding UUIDs.
Figure 3-38 Find Information Request/Find Information Response

Table of Contents