NRF Connect Desktop BLE BUSY

RE: NRF Connect Desktop BLE BUSY

WesC — Wed, 01 Jun 2022 18:45:11 GMT

They weren’t handling event “BLE_GATTS_EVT_SYS_ATTR_MISSING” in the firmware. It seems this is required for the desktop app, but wasn’t required with the nRF mobile app.

It’s working fine for me now on both the dongle and DK

RE: NRF Connect Desktop BLE BUSY

Sigurd — Fri, 13 May 2022 11:22:52 GMT

Hi,

Looks like the slave does not respond to this read request that is done by the nRF Connect desktop app. Maybe an issue with how this characteristic is configured.

Do they get any errors or events from the SoftDevice in their application when this happens?

RE: NRF Connect Desktop BLE BUSY

WesC — Tue, 10 May 2022 12:36:31 GMT

I have attached 2 files from wireshark. Mobile-sniff and desktop-sniffdevzone.nordicsemi.com/.../desktop_5F00_sniff.pcapng devzone.nordicsemi.com/.../mobile_5F00_sniff.pcapng

Mobile_sniff - is the sniffer file for the connection with the nRF Connect mobile app. This worked as expected. I was able to connect and execute commands as before.

Desktop_sniff – is the sniffer file for the connection with the nRF Connect desktop app. As before, I could connect, but the commands didn’t work with the desktop app. It returned the timeout error we have seen before.

Setup: I had the sniffer running on the nRF Dongle attached directly to the USB port on my PC. nRF Connect for Desktop was running off my nRF52DK, which was plugged into a USB port on my USB-C datahub. (In an earlier call we had it was shown it didn’t matter if I had the DK/dongle plugged into the direct port or the hub – either way we got the timeout error). Our device was in the middle

RE: NRF Connect Desktop BLE BUSY

Sigurd — Wed, 20 Apr 2022 11:09:50 GMT

Hi,

Sound strange that it works fine with the mobile app, and not on the desktop app.

Would it be possible to capture a sniffer trace? https://www.nordicsemi.com/Products/Development-tools/nRF-Sniffer-for-Bluetooth-LE

A sniffer trace that shows the working case with the mobile app, and another sniffer trace that shows the failing case with the desktop app.