Telink TLSR8232 BLE SDK Developer Handbook
AN-19112700-E1
103
Ver.1.0.0
3.4.3.5 Read Request, Read Response
Please refer to
Core_v5.0
(Vol 3/Part F/3.4.4.3 and 3.4.4.4
) for details about “Read
Request
” and “Read Response”.
The “Read Request” command sent by Master specifies certain attHandle. After the
request is received, Slave will respond to Master with the Attribute Value of the specified
Attribute via the “Read Response” command (If the callback function r is set, this function
will be executed), as shown below.
Figure 3-39 Read Request/Read Response
3.4.3.6 Read Blob Request, Read Blob Response
Please refer to
Core_v5.0
(Vol 3/Part F/3.4.4.5 and 3.4.4.6) for details about
“Read Blob
Request
” and “Read Blob Response”.
If some Slave Attribute corresponds to Attribute Value with length exceeding MTU_SIZE
(It’s set as 23 in current SDK), Master needs to read the Attribute Value via the “Read
Blob Request
” command, so that the Attribute Value can be sent in packets. This
command specifies the attHandle and ValueOffset. After the request is received, Slave
will find corresponding Attribute, and respond to Master with the Attribute Value via the
“Read Blob Response” command according to the specified ValueOffset. (If the callback
function r is set, this function will be executed.)
As shown below, when Master needs the HID report map of Slave (report map length
largely exceeds 23), first Master sends “Read Request”, then Slave responds to Master
with part of the report map data
via “Read response”; Master sends “Read Blob
Request
”, and then Slave responds to Master with data via “Read Blob Response”.
Figure 3-40 Read Blob Request/Read Blob Response