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
  • Hi all, 

    I'm also having problems with the latest version of Programmer and Connect Desktop V3.9.3. I'm developing on Windows 7 Pro.

    I have my own hardware and am using a slightly modified version of the Open Bootloader over USB. The problem is also evident with an unmodified nRF52840 Dongle.

    The problem for me is that when I trigger the bootloader on my hardware (or on the Dongle), the device is found by windows and drivers are installed to mount the device as a port device "Open DFU Bootloader (Interface 0) (COMx)".

    The Programmer on nRF Connect V3.9.3 does not see any devices - EVER. 

    I have taken the advice of this thread and rolled back to nRF Connect V3.7.1 (incidentally the App sources URL is incorrect .. it should be https:// instead of http://) as well as JLink V6.88a and am happy to report that the programmer can now find devices.

    I look forward to a new release of the programmer that works properly. In the meantime, I will be taking a cautious approach to upgrades in the future.

    Regards,

    Carl.

Reply
  • Hi all, 

    I'm also having problems with the latest version of Programmer and Connect Desktop V3.9.3. I'm developing on Windows 7 Pro.

    I have my own hardware and am using a slightly modified version of the Open Bootloader over USB. The problem is also evident with an unmodified nRF52840 Dongle.

    The problem for me is that when I trigger the bootloader on my hardware (or on the Dongle), the device is found by windows and drivers are installed to mount the device as a port device "Open DFU Bootloader (Interface 0) (COMx)".

    The Programmer on nRF Connect V3.9.3 does not see any devices - EVER. 

    I have taken the advice of this thread and rolled back to nRF Connect V3.7.1 (incidentally the App sources URL is incorrect .. it should be https:// instead of http://) as well as JLink V6.88a and am happy to report that the programmer can now find devices.

    I look forward to a new release of the programmer that works properly. In the meantime, I will be taking a cautious approach to upgrades in the future.

    Regards,

    Carl.

Children
No Data
Related