• State Verified Answer
  • Replies 7 replies
  • Subscribers 65 subscribers
  • Views 1337 views
  • Users 0 members are here
Attachments (2) Download All
Nordic Case Info
  • Case ID: 297791
Options

nRF Connect For Desktop Bluetooth LE App No Longer Works Properly

Deav

Setup, Windows 10 PC,  nRF Connect for Desktop 3.12.0, BLE App v4.0.0
The windows nRF Connect for Desktop BLE Application on Windows 10 no longer works properly.  I've managed to get it to connect to a nRF52840DK eventually by doing the following:

1. Connect nRF82840DK to PC
2.  Disable segger mass storage device in device manager
3.  Cycle the power on the nRF52840DK
4.  Run nrfjprog --recover from the command line tools
5.  Open nRF Connect for desktop
6.  Open the BLE app (v4.0.0)
7.  Select the DK
8.  App says 'firmware must be programmed' even though it was previously programmed with this
9.  The BLE app now works as usual, except:
10.  After using for a short time, I get the error "Disconnected from device B8:1F:5E:FF:F9:02, reason: BLE_HCI_STATUS_CODE_LMP_RESPONSE_TIMEOUT"
11.  Every time I connect the DK, I get the message that the firmware needs to be programmed.

Previous to this, it wouldn't work at all, it would say it had programmed the firmware, then would give error messages saying invalid response from device.

Prior to these problems appearing everything worked normally.  This problem has occurred simultaneously on a number of PCs in our office.

I have attached logs of where it works but times out and where the firmware programming fails, meaning I need to perform nrfjprog --recover

2022-11-01T11_34_49.508Z-log - Working But Times Out.txt

2022-11-01T11_42_06.763Z-log - Firmware Not Programming.txt

  • 0

    Hi

    What version of the nRF52840 DK do you have? Can you try updating the BLE app to v4.0.1 which is the latest one? I'm not able to reproduce this issue on my end with an nRF52840 DK v1.0.0, where it was sufficient to program the DK once. Can you also provide some details on what you do when you experience these timeouts? What exactly do you mean by "using" it? Does it not matter what you do, or do you specifically have to connect to a device, scan, or advertise to trig this?

    Best regards,

    Simon

  • 0 in reply to Simonr

    Thanks for your reply.

    The nRF52840 DK i am using has the following on the label: 3.0.0 2022.34.  This issue also occurs on other boards we have, such as nRF51DK V1.2.3 2017/33. 

    I have deinstalled nRF connect and the BLE app, redownloaded from the website and installed everything again.  The BLE app still shows as 4.0.0.  The downloader that installs the BLE app and nRF connect shows 4.0.1 however.

    The timeout occurs after connection to a device when reading, so I could be manually reading a characteristic or using notify.

    The BLE app also says: 

    "12:50:26.820 Using JLink version: JLink_V7.66a
    12:50:26.851 Installed JLink version does not match the provided version (V7.58b)"

    but the installer clearly installs 7.66a



  • 0 in reply to Simonr

    I've just tried installing everything on a brand new PC and get the same results, including the BLE App showing the version 4.0.0.

    I also tried the RSSI viewer with a nRF52840 dongle programmed with nRF sniffer software and it recognised it as having the correct firmware!

    2022-11-02T13:30:50.405Z INFO Validating firmware for device with s/n F2E2F24B6C0AE959
    2022-11-02T13:30:50.459Z INFO Opening device with s/n F2E2F24B6C0AE959
    2022-11-02T13:30:50.475Z INFO Serial port is closed
    2022-11-02T13:30:50.483Z INFO COM185 is open


  • 0

    Hi

    I also use v7.66a of J-Link and see this message that the J-Link version doesn't match. Also v4.0.0 seems to be used in the standalone version indeed. I will report this. I'm still not able to recreate any of the issues you're seeing on my end though. Can you try opening a command line interface and run the nrfjprog --recover call with the nRF Command Line Tools to make sure it's in a clean state and not for example blocked by APPROTECT before flashing the BLE application onto it.

    Best regards,

    Simon

  • 0 in reply to Simonr

    On the new PC, after --recover the app is working as I managed to do previously, but it still quickly disconnects with the error message BLE_HCI_STATUS_CODE_LMP_RESPONSE_TIMEOUT, which is the main problem.  The device I am connecting to has an RSSI of around -40 and maintains solid connection with other systems

    # nRFConnect System Report - 2022-11-02T14-31-53.062Z

    - System: Dell Inc. XPS 15 9500
    - BIOS: Dell Inc. DELL - 20170001
    - CPU: 1 x Intel CoreTm i9-10885H 2.4 GHz 16 cores (8 physical)
    - Memory: 16.6 GB free of 31.8 GB total
    - Filesystem: C: (NTFS) 935 GB 79.1% used

    - OS: Microsoft Windows 10 Pro (10.0.19043) Windows x64

    - Versions
    - kernel: 10.0.19043
    - git: 2.32.0.windows.2
    - node: 14.16.0
    - python: 3.9.13
    - python3: 3.9.13
    - nrf-device-lib-js: 0.4.4
    - nrf-device-lib: 0.10.3
    - nrfjprog DLL: 10.15.1
    - JLink: JLink_V7.66a

    - Connected devices:
    - F2E2F24B6C0AE959 : COM185



Related