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

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

Georgi Valkov — Mon, 24 Oct 2022 11:04:48 GMT

Just toggle SW10. This is sufficient whenever I want to restart GDB server to program/debug the other CPU. In the old version of Programmer, this was also sufficient: when I disconnect and reconnect Programmer, it used to recognise the other CPU. Not I need to restart Programmer every time I toggle the switch. The Eject button should release the jTAG interface so that when a new device is selected, the correct CPU is recognised.

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

Marte Myrvold — Mon, 24 Oct 2022 08:51:19 GMT

Hi,

Are you turning the DK off in between, or simply toggling the SW10/SW5 switch?

Best regards,

Marte

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

Georgi Valkov — Fri, 21 Oct 2022 14:42:23 GMT

Hi Marte!

I am curently using nRF Connect for Desktop v3.12.0 and Programmer v3.0.4 (latest). The following issue is still present: If the switch is in position nRF91, the nRF9160 CPU is detected by Programmer. Then if I press the eject button, toggle the switch to nRF52 and select the nRF9160dk board again, Programmer still shows the nRF9160 CPU instead of nRF52840. When will this regression finally be fixed?

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

CarlK — Tue, 18 Jan 2022 04:17:14 GMT

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.

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

Marte Myrvold — Mon, 10 Jan 2022 13:05:47 GMT

Hi,

We have released nRF Connect for Desktop v3.9.2 and v3.9.3, both with multiple bug fixes.

Best regards,

Marte

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

Georgi Valkov — Thu, 16 Dec 2021 09:36:30 GMT

Reproduced every time on Windows 10, Windows 11 and macOS. Any updates from Nordic?

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

Georgi Valkov — Tue, 07 Dec 2021 17:37:01 GMT

It's the same issue.

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

Marte Myrvold — Tue, 07 Dec 2021 09:24:45 GMT

Hi,

Our developers are working on this. Are you seeing the same issues as previously, or are the issues different?

Best regards,

Marte

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

Georgi Valkov — Fri, 03 Dec 2021 02:10:17 GMT

I updated my laptop (macOS) to v3.9.1 of nRF Connect for Desktop and Programmer v2.0.1. They are still broken. Any plans for a real fix from Nordic?

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

Marte Myrvold — Wed, 10 Nov 2021 12:01:48 GMT

Hi,

We have just released v3.9.0 of nRF Connect for Desktop, which includes fixes to make enumeration more robust and increase the timeout when enumeration takes a long time. The version is not on the download page yet, but you can update to it directly in the app, and you can find the release and release notes here nRF Connect for Desktop releases.

The developers have also found that the JLink version that is bundled with the latest version of nRF Command Line Tools causes errors in nRF Connect for Desktop. They are working on a fix for this as well, but a temporary workaround is to downgrade JLink to a known working version, v6.88a, from https://www.segger.com/downloads/jlink.

Best regards,

Marte

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

Marte Myrvold — Wed, 10 Nov 2021 12:00:49 GMT

Hi,

Thank you for providing the steps, and for clarifying that you are still having these issues in nRF Connect for Desktop v3.9.0. I have reported this to our developers.

The developers have found that the JLink version that is bundled with the latest version of nRF Command Line Tools causes errors in nRF Connect for Desktop. They are working on a fix for this as well, but a temporary workaround is to downgrade JLink to a known working version, v6.88a, from https://www.segger.com/downloads/jlink.

Best regards,

Marte

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

Georgi Valkov — Wed, 10 Nov 2021 08:42:21 GMT

Step by step in screenshots on a fresh Windows 11 install with JLink_Windows_V756d_x86_64

Install nRF Connect 3.8.0, connect Thingy:91 and nRF9160dk, install and then try to open Programmer

Restart nRF Connect 3.8.0 and open programmer, Unknown is shown, it should not be. Is this COM1? This computer has a COM port on the mainboard. If yes, it should at least indicate that this is COM1. The old version of Programmer had a much better user interface, because a toolbar on the right side is more productive, it happens to be closer to the mouse and there is a rule that a good interfaces reduces the amount you need to move the mouse to perform tasks.

Select nRF9160 DK, the switch is in position nRF52840

Press the Eject button, switch to nRF9160 and try to reconnect. Programmer still shows nRF52840.

Restart Programmer, it froze on a white screen

Restart Programmer again. It does not detect any devices

Update to nRF Connect 3.9.0

Then the issue where switch changes are not detected remains.

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

Georgi Valkov — Tue, 09 Nov 2021 18:05:09 GMT

[quote userid="92402" url="~/f/nordic-q-a/81380/programmer-2-0-is-broken-in-nrf-connect-for-desktop-v3-8-0/337934#337934"]Could you please share what steps you are performing to reproduce this issue?[/quote]

Sure:

Start Programmer, and erase a CPU on nRF9160dk
Disconnect Programmer
Move the switch the other CPU
Connect Programmer again it shows the first CPU

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

dth — Tue, 09 Nov 2021 01:01:41 GMT

I also have issues with the programmer 2.0.0. When I plug in a nrf52840 dongle (in bootloader mode) it appears in the device list, but is labelled "unknown". If I select it, I get "Error when fetching device versions: readFwInfo error" in the console of the programmer.

Downgrading manually to 1.4.11 fixes the problem.

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

Marte Myrvold — Mon, 08 Nov 2021 13:38:35 GMT

Hi,

Our apps and other releases are all tested before they are released. However, some bugs were not discovered for this release. Our developers are doing their best to fix this, and hopefully this will not be an issue in the future.

[quote user="Georgi Valkov"]I reproduce the issue every time[/quote]

Could you please share what steps you are performing to reproduce this issue?

Best regards,

Marte

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

Marte Myrvold — Mon, 08 Nov 2021 12:49:55 GMT

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

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

Georgi Valkov — Sun, 07 Nov 2021 13:58:02 GMT

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.

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

jk1 — Fri, 05 Nov 2021 10:03:12 GMT

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.

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

Marte Myrvold — Fri, 05 Nov 2021 07:33:34 GMT

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

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

Georgi Valkov — Thu, 04 Nov 2021 22:18:19 GMT

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.

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

Georgi Valkov — Thu, 04 Nov 2021 22:13:50 GMT

Thanks, Marte! It is very good knowing that there is an official downgrade option, considering the quality and reliability of the nRF Connect SDK tools from Nordic has been very low with obvious bugs and issues that are easy to notice even on the first run or which break the build process completely. Hence my recommendation to Nordic: I see you have great ideas, but please make your tools reliable and stop releasing broken tools!

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

Marte Myrvold — Thu, 04 Nov 2021 14:52:56 GMT

Hi,

Our developers have found that having a JLink device, such as JLink Lite or JLink Plus debuggers, connected to your computer without the device being connected to anything (DK/SoC), will cause this issue. This will be fixed in a new release of nRF Connect for Desktop. I will notify you when this is released. Until then, their solution is to disconnect all JLink devices that are not connected to anything.

Best regards,

Marte

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

Marte Myrvold — Thu, 04 Nov 2021 09:40:22 GMT

Hi,

In the meantime, a temporary workaround is to downgrade to 3.7 and install app versions compatible with 3.7:

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).
After starting nRF Connect for Desktop 3.7 a prompt will come up about the 3.8 upgrade. Click “No” on this.
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”.
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”.
Install the apps you need in the old versions and use them.

I will let you know when the issue is fixed, or if I have any other updates.

Best regards,

Marte

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

Marte Myrvold — Thu, 04 Nov 2021 08:03:06 GMT

Hi,

I have reported this internally to the developers, and they are working on it.

Best regards,

Marte

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

Ben — Thu, 04 Nov 2021 02:55:25 GMT

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.