• State Verified Answer
  • Locked Locked
  • Replies 4 replies
  • Subscribers 25 subscribers
  • Views 161 views
  • Users 0 members are here
Attachments (3) Download All
Nordic Case Info
  • Case ID: 287794
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

NRF Connect Desktop BLE BUSY

user90130

I have a customer that has been using the nRF Connect Mobile app on his iPhone to test his device and its works perfectly and he can do all the functionality he wants including DFU.  When he uses the nRF Connect Desktop he gets an APP_ERROR_BUSY(0x11) when trying to enable the notifications or write to a custom characteristic.

The Desktop BLE version is 3.0.1.  I have attached a screenshot of the error and the log file from the transaction.  Please let me know your thoughts on this issue

Parents
  • 0

    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.

  • 0 in reply to user15146

    I have attached 2 files from wireshark.  Mobile-sniff and desktop-sniff

    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

  • 0 in reply to user90130

    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?

Reply
  • 0 in reply to user90130

    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?

Children
No Data
Related
Terms of service