Programmer 2.0 is broken in nRF Connect for Desktop v3.8.0

Programmer 2.0 is broken in nRF Connect for Desktop v3.8.0

Very often it does not detect connected devices, even if I disconnect and reconnect the nRF9160DK which is also used as a programmer. When I click the SELECT DEVICE button I see a link to find Nordic devices, even though I have both nRF9160dk and Thingy:91 attached over USB. Reconnecting the devices does not help. Sometimes with no devices connected, I see Unknown as a listed device. The Programmer also stops responding often on a white screen, at the same time, nRF Connect for Desktop v3.8.0 and the Toolchain Manager v0.10.0 may also freeze on a white screen. Restarting the tools sometimes helps, sometimes it doesn't and I have to do it several times, disconnecting the USB cables until it eventually works. Once a device is selected and erased, if I click the Eject button, then program the device using Segger Embedded Studio, then stop the debugging session, switch the key on the board which toggles between nRF9160 and nRF52840, then connect the Programmer again, it shows the previously selected CPU. I need to restart all tools until the correct CPU is shown. The broken behaviour is consistent between Windows 10 21H1 and macOS Big Sur 11.6.1. With the previous version of Programmer, which had the controls on the right side, I have never experienced any of these issues.

Parents
  • I am having a similar issue. Everything was working fine prior to updating to nRF Connect for Desktop v3.8.0 and Programmer 2.0.

    Now having updated the programmer when I select the connected device from the drop down, all the buttons on the left are still greyed out.

    I am using a ublox BMD-341-EVAL board (containing a nRF52840) that currently has Wirepas firmware on it. nRF connect is on Windows 10.

    LOG:

    13:48:06.821 Using @nordicsemiconductor/nrf-device-lib-js to communicate with target via JLink
    13:48:06.821 JLink OB firmware version J-Link OB-SAM3U128-V2-NordicSemi compiled Feb 2 2021 16:47:20
    13:48:06.823 Device family
    13:48:06.824 Device version
    13:48:06.825 Board version PCA10040
    When I click on "open log file" it returns an error, saying the specified path does not exist.
Reply
  • I am having a similar issue. Everything was working fine prior to updating to nRF Connect for Desktop v3.8.0 and Programmer 2.0.

    Now having updated the programmer when I select the connected device from the drop down, all the buttons on the left are still greyed out.

    I am using a ublox BMD-341-EVAL board (containing a nRF52840) that currently has Wirepas firmware on it. nRF connect is on Windows 10.

    LOG:

    13:48:06.821 Using @nordicsemiconductor/nrf-device-lib-js to communicate with target via JLink
    13:48:06.821 JLink OB firmware version J-Link OB-SAM3U128-V2-NordicSemi compiled Feb 2 2021 16:47:20
    13:48:06.823 Device family
    13:48:06.824 Device version
    13:48:06.825 Board version PCA10040
    When I click on "open log file" it returns an error, saying the specified path does not exist.
Children
No Data
Related