• State Verified Answer
  • Locked Locked
  • Replies 3 replies
  • Subscribers 88 subscribers
  • Views 1005 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 281222
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 unable to find 52840 dongle when JLink connected

Allen

Hello,

I have nRF Connect Desktop v3.9.1 for MacOS installed. I am trying to run the "Bluetooth Low Energy" utility using a nRF52840 dongle.

If the only device connected is the dongle, the nrf connect plugins can find the device.

If a JLink is plugged in, with a powered on nRF52832 device attached, none of the devices are populated in the BLE device list. (if the JLink is attached but the device is powered off, it works)

BTW: I am using a JTrace with the mass storage functionality disabled.

Thanks

  • 0

    Hi,

    I have reported this internally to the nRF Connect for Desktop developers, and they are looking into it.

    A temporary workaround is to downgrade to v3.7 of nRF Connect for Desktop and install app versions compatible with 3.7:

    1. Download the latest 3.7 version of nRF Connect for Desktop from https://www.nordicsemi.com/Products/Development-tools/nRF-Connect-for-desktop/Download?lang=en#infotabs (for macOS this is 3.7.2, for Windows and Linux 3.7.1, because 3.7.2 was not needed and not released for these).
    2. After starting nRF Connect for Desktop 3.7 a prompt will come up about the 3.8 upgrade. Click “No” on this.
    3. In the Settings, click on “Add source”, enter the URL http://developer.nordicsemi.com/.pc-tools/nrfconnect-apps/3.7-apps/apps.json and click “Add”.
    4. Back in the list of all apps, all apps should show up twice now, one with “official” below them and one with “3.7 compatible apps” below them. If you want to hide the incompatible versions, click on “Filter” and deselect “Official”.
    5. Install the apps you need in the old versions and use them.

    Best regards,

    Marte

  • +1

    Hi,

    The developers have been unable to reproduce the issue so far, using J-Trace PRO Cortex-M v2.0 and nRF52 DK (pca10040) v1.2.1, connected on debug in. Could you give some information on what versions you are using? Does this happen all the time when the dongle and JLink+nRF52832 are connected, or are there certain steps to reproduce it?

    Best regards,

    Marte

  • +1 in reply to Marte Myrvold

    Hello Marte,

    The next day, I am not able to reproduce the error either. I had rebooted and tested again before reporting the issue. Not sure what changed. (I hate that) Will close this for now.

Related