s140 pc-ble-driver 4.0.0 freezes when receiving too many data

[jpo38]

I have a nRF52840-PCA10059 dongle.

I have a PCA10040 dev boeard on which I programmed the ble_app_hrs_freertos_pca10040_s132 example after I modified HEART_RATE_MEAS_INTERVAL and BATTERY_LEVEL_MEAS_INTERVAL variables (lines 100 and 95 of main.c) with value 10 (10ms for 100Hz).

If I connect this fast "Nordic_HRM" using nRF Connect (it programmed my dongle with API v3 SoftDevice, I can connect and get notifications from the device.

If I connect this fast "Nordic_HRM" using heart_rate_collector_v3 or heart_rate_collector_v6 example programs (compiled from https://github.com/NordicSemiconductor/pc-ble-driver/tree/v4.0.0), then I only get a few notifications and then the app freezes.

When it's frozen, using a debugger I can see that UartBoost::readHandler is not called anymore. If I press Enter (supposed to toggle notifications OFF), I see written

"Setting HRM CCCD"

I see:

UartBoost::readHandler receives: c0 10 0 0 f0 c0 c0 d6 6e 0 bc 1 9c 11 0 0 0 61 3e c0
SerializationTransport::readHandler receives: 1 9c 11 0 0 0

But "Received write response." never shows up. Looks like the soft device freezed and does not send my anything.

When using heart_rate_collector_v2 with a old nRF51 dongle, I observe no freezing.

When using heart_rate_collector_v3, I kept the SoftDevice programmed by "nRF Connect". Also tried with connectivity_4.0.0_usb_with_s132_3.1.0.hex, same behaviour observed.

When using heart_rate_collector_v6, I used connectivity_4.0.0_usb_with_s140_6.1.0.hex.

"Nordic HRM" unmodified device (low sampling rate) does not freeze.

Any ides what could cause this? What does nRF Connect make differently than heart_rate_collector sample?

[Jørgen Holmefjord]

I'm having some issues with reading the sniffer logs. Did you use the new nRF Sniffer v2? Which Wireshark version do you use?

[jpo38]

Hello,

I used old v1_2, followed this user guide: https://os.mbed.com/media/uploads/nemovn/ble-sniffer_win_1.2_user_guide.pdf

Did not understand how to use newer versions. "Get started" page being empty (https://www.nordicsemi.com/Software-and-Tools/Development-Tools/nRF-Sniffer/Get-Started#infotabs)....so I used the old one.

So this uses Wireshark v1.10.1.

Hoping you can finally read the logs, let me know.

Kind regards,

Jean Porcherot

[Jørgen Holmefjord]

I recommend using v2 and follow the User Guide that can be found on the DocLib.

[jpo38]

OK, I can do that. But is that needed for you to continue investigating my problem? Can you open and analyze the logs I sent with Wireshark 1.10.1 or do I need to use v2 and generate them again?

This issue starts to be a real problem for us as or devices (many working at 100Hz) can't be used anymore...

Kind regards,

Jean Porcherot

[jpo38]

I installed that today, please let me know if I should re-generate the wireshark logs using v2 or if you were able to analyse the ones I sent with v1.

By the way, I did some more testing today:

- Actually, "nRF Connect" also stops receiving notifications at some point (even if it takes more time for it to end up in such a situation, a few seconds).

- With API2, even after long minutes, there is no problem.

So apparently, the problem can only be reproduced with API3 or API6, and is prensent both with "nRF Connect" and with "pc-ble-driver HRM collector sample program"

Jean