Seriarization (UART) Read blob Failure

[H.O]

Hi, I send application data using Read blob PDU from nRF52832. nRF52832 firmware is connectivity of  Serialization of nRF5_SDK_17.0.2 for UART interface.

After connection, application data is sent using Read blob response. the Unit of transmission is 22byte for application data.

nRF52832 sent broken data at offset 0x0042. And, nRF52832 could not send application data at offset 0x0058.

Why? 

nRF52832 Serialization UART command sequence is below.

SEQ: SD_BLE_CFG_SET (BLE_COMMON_CFG_VS_UUID)
TX : 08 00 00 69 01 00 00 00 01 02
RX : 06 00 01 69 00 00 00 00

SEQ: SD_BLE_ENABLE
TX : 02 00 00 60
RX : 06 00 01 60 00 00 00 00

SEQ: SD_BLE_GAP_ADDR_SET
TX : 0a 00 00 6c 01 00 11 22 33 44 55 66
RX : 06 00 01 6c 00 00 00 00

SEQ: SD_BLE_UUID_VS_ADD
TX : 14 00 00 62 01 67 07 60 a4 84 5d 26 ae 12 41 64 ce 61 28 e5 a6 01
RX : 08 00 01 62 00 00 00 00 01 02

SEQ: SD_BLE_UUID_VS_ADD
TX : 14 00 00 62 01 cd e4 71 b6 c2 2a e6 9e 44 41 8d 88 45 68 78 f3 01
RX : 08 00 01 62 00 00 00 00 01 03

SEQ: SD_BLE_GATTS_SERVICE_ADD
TX : 08 00 00 a8 01 01 a4 84 02 01
RX : 09 00 01 a8 00 00 00 00 01 0e 00

SEQ: SD_BLE_GATTS_CHARACTERISTIC_ADD
TX : 26 00 00 aa 00 00 01 3e 01 00 00 00 00 00 00 00 01 11 11 02 00 01 01 a4 84 02 01 11 11 1d 00 00 00 02 02 00 01 04 00 01
RX : 0f 00 01 aa 00 00 00 00 01 10 00 00 00 11 00 00 00

SEQ: SD_BLE_GATTS_CHARACTERISTIC_ADD
TX : 26 00 00 aa 00 00 01 3e 01 00 00 00 00 00 00 00 01 11 11 02 00 01 01 b6 c2 03 01 11 11 1d 00 00 00 02 02 00 01 04 00 01
RX : 0f 00 01 aa 00 00 00 00 01 14 00 00 00 15 00 00 00

SEQ: SD_BLE_GAP_ADV_SET_CONFIGURE
TX : 38 00 00 72 01 ff 01 01 00 00 00 10 00 01 02 01 06 0c ff 42 04 43 4e 54 31 01 89 54 42 00 02 00 00 00 00 00 01 01 01 00 00 2c 01 00 00 50 46 00 01 00 00 00 00 00 00 01 00 00
RX : 08 00 01 72 00 00 00 00 01 00

SEQ: SD_BLE_GAP_ADV_START
TX : 04 00 00 73 00 00
RX : 06 00 01 73 00 00 00 00

SEQ: BLE_GAP_EVT_CONNECTED

RX : 34 00 02 10 00 03 00 00 d1 d2 d3 d3 d2 d1 01 10 00 10 00 00 00 00 01 00 01 00 00 00 10 00 01 02 01 06 0c ff 42 04 43 4e 54 31 01 89 54 42 00 02 00 00 00 00 00 01

SEQ: BLE_GATTS_EVT_RW_AUTHORIZE_REQUEST
RX : 0d 00 02 51 00 03 00 01 10 00 a4 84 02 00 00
TX : 24 00 00 b0 03 00 01 01 00 00 01 00 00 16 00 01 00 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f 10 11 12 13 14 15
RX : 06 00 01 b0 00 00 00 00

SEQ: BLE_GATTS_EVT_RW_AUTHORIZE_REQUEST
RX : 0d 00 02 51 00 03 00 01 10 00 a4 84 02 16 00
TX : 24 00 00 b0 03 00 01 01 00 00 01 16 00 16 00 01 16 17 18 19 1a 1b 1c 1d 1e 1f 20 21 22 23 24 25 26 27 28 29 2a 2b
RX : 06 00 01 b0 00 00 00 00

SEQ: BLE_GATTS_EVT_RW_AUTHORIZE_REQUEST
RX : 0d 00 02 51 00 03 00 01 10 00 a4 84 02 2c 00
TX : 24 00 00 b0 03 00 01 01 00 00 01 2c 00 16 00 01 2c 2d 2e 2f 30 31 32 33 34 35 36 37 38 39 3a 3b 3c 3d 3e 3f 40 41
RX : 06 00 01 b0 00 00 00 00

SEQ: BLE_GATTS_EVT_RW_AUTHORIZE_REQUEST
RX : 0d 00 02 51 00 03 00 01 10 00 a4 84 02 42 00
TX : 24 00 00 b0 03 00 01 01 00 00 01 42 00 16 00 01 42 43 44 45 46 47 48 49 4a 4b 4c 4d 4e 4f 50 51 52 53 54 55 56 57　<- Peer device can receive this application but a part of this data is broken.
RX : 06 00 01 b0 00 00 00 00

SEQ: BLE_GATTS_EVT_RW_AUTHORIZE_REQUEST
RX : 0d 00 02 51 00 03 00 01 10 00 a4 84 02 58 00
TX : 24 00 00 b0 03 00 01 01 00 00 01 58 00 16 00 01 58 59 5a 5b 5c 5d 5e 5f 60 61 62 63 64 65 66 67 68 69 6a 6b 6c 6d  <- Peer device cannot receive this application data.

B.R.

[Sigurd]

Hi,

nRF52832 Serialization UART command sequence is below.

It's a bit difficult to understand what's happening with only this command sequence. Could you capture a sniffer trace?

https://www.nordicsemi.com/Products/Development-tools/nRF-Sniffer-for-Bluetooth-LE

[H.O]

I have BPA low energy of Teledyne. Can you find the below?

Peripheral (Slave) device is nRF52832. 

 

[Sigurd]

Hi,

Could you zip and upload the sniffer file as well?

[H.O]

Hi, thank you for your reply.

I uploaded the below file.

nRF52832_ReadBlob_Failure.zip

[Sigurd]

Hi,

As far as I can see from the log, after the ATT_READ_BLOB_REQ with offset 88, sent from the master, the slave just stopped responding, and the link seem to have been lost. Likely it run into some issue in the application. You would have to debug the nRF52 application to see why it failed.