Tool/software: Code Composer Studio
First we use GATT_WriteCharValue () to directly write telegrams with a maximum of 20 bytes. That works fine.
We have a single function call per telegram and a single response from the stack.
We have a single function call per telegram and a single response from the stack.
Now we have to encrypt the communication and send larger blocks of 32, 48, 64 bytes over the GATT layer.
We try not to divide the transfer into a multiple-write function call, as I think this should be part of the BLE stack.
In revieve direction, the stack handles fragmented payload correctly.
In revieve direction, the stack handles fragmented payload correctly.
I think the GATT_WriteLongChar() or the GATT_WriteLongCharDesc() are the right functions, but I can not find an example of how to use that.
We use the ble stackversion ble_sdk_2_02_01_18 and ower project is based on the simple_central_cc2650 sample app.
By sniffing the exchange of the MTU I saw that the master supports 160 bytes and the client 158 bytes.
By sniffing the exchange of the MTU I saw that the master supports 160 bytes and the client 158 bytes.