nRF52832 notification packet issue using SDK17.0.2

RE: nRF52832 notification packet issue using SDK17.0.2

Tosa — Fri, 28 Jan 2022 04:54:22 GMT

You're right. Instead of using an event loop flag to push more data to sd_ble_gatts_hvx() after getting BLE_GATTS_EVT_HVN_TX_COMPLETE, I just call sd_ble_gatts_hvx() right after. Not sure why this wasn't an issue in SDK11.0.0, but perhaps I could increase the throughput by doing this there too.

RE: nRF52832 notification packet issue using SDK17.0.2

Tosa — Thu, 27 Jan 2022 16:38:37 GMT

Yes, it is what I see in the application, but the nRF52840 dongle + Wireshark sniffer shows the same data. The data streamed by notifications from the nRF52832 peripheral/server to the Windows PC central/client.

Sniffer logs are attached. I don't see SN and NESN causing this issue. Also, kindly let me know if it is possible to use 2Mbps PHY in SDK11. If so, how do I set it? Thanks!

devzone.nordicsemi.com/.../cy5677-sdk17-repeated-packet-at-1390.pcapng

devzone.nordicsemi.com/.../usb_2D00_bt500-sdk17-repeated-packet-at-6270.pcapng

RE: nRF52832 notification packet issue using SDK17.0.2

Edvin — Thu, 27 Jan 2022 13:08:21 GMT

Hello,

These observations are based on what you see/receive in your application, and not from a sniffer trace, right?

It sounds like it has something to do with the way you determine when a packet is queued and not.

Do you send data from the central or from the peripheral?

Best regards,

Edvin