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.

  • I used a j-Trace 7 months ago. I no longer have access to any Segger hardware, apart from what comes on nRF9160DK which alone is sufficient to reproduce all issues on both Windows and Mac.

  • Hi,

    Thank you for the feedback, I will forward it to the developers.

    Do you have any other programs using JLink devices open?

    Since you are still experiencing this issue with only the nRF9160 DK connected, your issue might be caused by something else. Our developers found that there was also an issue with enumeration timeout, but this has been very hard to reproduce as it does not happen often. They are working on solutions for this as well, and there will be a temporary fix in the next release. However, it is difficult to gather information about this when they are not able to reproduce it, so it would be very helpful to get information from customers experiencing these issues. I have some files that can be used to gather more extensive logs about this, but they are not public. If you would be willing to help and get some logs, please let me know and I can make this ticket private to share the files with you. It would be greatly appreciated!

    Best regards,

    Marte

  • Our manufacturing line is down somehow as a result to this, and now I have to try to explain to someone in Chinese how to downgrade and figure out what else is broken as a result.  Please get this fix released and test your stuff better. It immediately happened on my setup here too.  So maybe next time just try to run your apps first.

  • Marie, I reproduce the issue every time on two Windows 10 computers, as well as a MacBook Pro 2019 running macOS 11.6.1. I had no issues before updating. If it would help, I can offer your engineers access to my computers, and assist them to debug and fix the issue. That would be 100€/hour. Visual Studio 2019 and Xcode are available. The only related software I have installed is JLink_Windows_V756d_x86_64. I usually keep the Segger drivers updated.

    Here's my advise to your team: remember to test extensively and follow good practices. It is makes the difference between a crash or incorrect behaviour, which is 100% consistent and reproducible and points directly to the cause, and random issues which depend on users' environment.

    I can tell you from my experience that not taking time to test, often results in lost projects, and millions of lost in revenue. jk1's post is a good example.

  • Hi,

    I apologize for the issues caused by this. All our apps and releases are tested before they are released, but sometimes not all bugs are not found during testing. I have forwarded the feedback from customers regarding this release to the developers, and hopefully this will not be an issue in the future. 

    Best regards,

    Marte

Related