NRF 52832/833 NRF CONNECT SDK FACING ISSUE TO GET DATA FROM PERIPHRAL DEVICE AFTER SUCCESSFUL CONNECTION ESTABLISHMENT.

RE: NRF 52832/833 NRF CONNECT SDK FACING ISSUE TO GET DATA FROM PERIPHRAL DEVICE AFTER SUCCESSFUL CONNECTION ESTABLISHMENT.

Einar Thorsrud — Wed, 21 May 2025 11:59:01 GMT

Hi,

I see. The sniffer trace indicate that notifications are enabled, but are not transmitted from the peripheral. Wihtout debugging or understanding how the peripheral works, I am not able to say why that is. There is unfortunately not much else I can say at this point.

RE: NRF 52832/833 NRF CONNECT SDK FACING ISSUE TO GET DATA FROM PERIPHRAL DEVICE AFTER SUCCESSFUL CONNECTION ESTABLISHMENT.

Embel_Tech — Wed, 21 May 2025 11:20:06 GMT

I wanted to clarify that I currently don't have the provision to debug the peripheral device. However, I can confirm that I’ve used the same peripheral with both the nRF5 SDK and the nRF Connect SDK.

Please let me know if there's anything specific you'd like me to check or try from my end.

RE: NRF 52832/833 NRF CONNECT SDK FACING ISSUE TO GET DATA FROM PERIPHRAL DEVICE AFTER SUCCESSFUL CONNECTION ESTABLISHMENT.

Einar Thorsrud — Wed, 21 May 2025 10:25:39 GMT

Hi,

Looking at the file "LOG 27 FEB 25 - CONNECTION ESTABLISHED , GOT DATA.pcapng" I see that the central writes to the CCCD (#33), and the peripheral starts sending notifications. This is also the case in "central nrf52832 using nrf connect sdk log 17 may 25.pcapng" (#57, with the reply in #60). But there are no notifications.

I may be missing something, but based on this it seems like the issue is that the peripheral is not transmitting notifications for some reason. Are you testing with the same peripheral device? Do you have logging on the peripheral, or ability to debug it so you can see what this looks like from that end? Why is it not transmitting any notifications even though that has been enabled in the CCCD?

RE: NRF 52832/833 NRF CONNECT SDK FACING ISSUE TO GET DATA FROM PERIPHRAL DEVICE AFTER SUCCESSFUL CONNECTION ESTABLISHMENT.

Embel_Tech — Wed, 21 May 2025 05:41:49 GMT

We have identified that the data received is null, meaning the received data length is zero. To help illustrate the difference, I have attached BLE sniffer logs from two different SDKs for your reference:

BLE Sniffer Log using nRF5 SDK 15.0.0: Data is being received successfully.

devzone.nordicsemi.com/.../LOG-27-FEB-25-_2D00_-CONNECTION-ESTABLISHED-_2C00_-GOT-DATA.pcapng
BLE Sniffer Log using nRF Connect SDK: Data is being received as null (length zero).

devzone.nordicsemi.com/.../central-nrf52832-using-nrf-connect-sdk-log-17-may-25.pcapng

This discrepancy suggests a potential issue with the configuration or handling of BLE data in the nRF Connect SDK.

Please review the attached logs and let me know if any additional information is required.

RE: NRF 52832/833 NRF CONNECT SDK FACING ISSUE TO GET DATA FROM PERIPHRAL DEVICE AFTER SUCCESSFUL CONNECTION ESTABLISHMENT.

Einar Thorsrud — Mon, 19 May 2025 12:16:56 GMT

Hi Suvarna,

What exactly do you mean by "the data received is null"? Do you receive length zero, or an array of a certain size where the data is all zero, or something else? Can you share a sniffer trace so we see if the data is actually sent on air? That will which side the issue is on. If the issue is on the GATT client (the one performign the read), the next is to look into your code handlign that.

Br,

Einar