Programmer v2.3.1

RE: Programmer v2.3.1

Simonr — Thu, 10 Feb 2022 14:02:21 GMT

It seems like you verified one of your answers. After doing so I won't get updates of when you upload new replies. Did you solve your issue and don't need further assistance or was this an accident and I should reopen it?

As for the problem with the computer, thank you for confirming, then it shouldn't be necessary to test nrfjprog with the Dongles, as they seem to work correctly on other computers. Then I don't have too much to suggest other than uninstalling nRFConnect altogether. And make sure you make sure the folder in C:\Users\___\AppData\Roaming\nrfconnect is empty or non-existent before reinstalling. I have also asked internally and can update you if I get any more suggestions.

Best regards,

Simon

RE: Programmer v2.3.1

DPJONES — Thu, 10 Feb 2022 10:23:01 GMT

Hi Simon

Sorry I don't understand how to connect via the debugger could you please explain in more detail as this is the first time we have have used Nordic.

I have tried connection to the hubs and also directly to the computer.

Regarding computers the one we have been using is the main R&D tool in the office we have many other compilers and emulators by other Manufactures already working on it without incident.

I suspect the problem lies with the device driver and nrf Connect.

Kind Regards

David

RE: Programmer v2.3.1

Simonr — Thu, 10 Feb 2022 09:36:48 GMT

Sorry, the Dongle will need to be connected via a debugger (the one on the DK for example in order to communicate with the command line since it doesn't have a debugger onboard.

Either way since it's a problem with multiple Dongles I would think this is on the computer/nRFConnect app side rather than with the Dongles. Are you using a USB hub or do you connect the Dongles directly to the computer? We've also had some reports with issues when connecting to USB hubs.

Do you by chance have another computer available that you could use with nRFConnect and try to connect to?

Best regards,

Simon

RE: Programmer v2.3.1

DPJONES — Wed, 09 Feb 2022 15:19:36 GMT

Hi Simon

I have used the command line tool please see attached.

We really need to get to the bottom of this as we have brought a few to test, with the view of changing existing BLE suppliers to Nordic.

Kind Regards

David

RE: Programmer v2.3.1

Simonr — Wed, 09 Feb 2022 14:22:24 GMT

Since the development kit works fine, I guess that's not the issue. The reason for these errors is the Programmer app and nRFConnect app aren't compatible. This should be covered in steps 3-5 if you want to test this (outdated) workaround anyway.

One thing you can try, so that we can isolate this issue to either the nRFConnect app itself or not, is if you use the nRFCommand line tools and write nrfjprog --eraseall or similar when the Dongle is connected to your computer and see what the response is.

Best regards,

Simon

RE: Programmer v2.3.1

DPJONES — Wed, 09 Feb 2022 09:08:54 GMT

Hi Simon

I followed all of the instructions but all I get when I try to run the programmer (please see attached)

Kind Regards

David

RE: Programmer v2.3.1

DPJONES — Wed, 09 Feb 2022 08:53:10 GMT

Hi Simon

Since the Jlink update the computer no longer slows down when using the nRF52840DK and also this Dev board works fine.

I will try the workaround and let you know

Kind Regards

David

RE: Programmer v2.3.1

Simonr — Wed, 09 Feb 2022 08:00:23 GMT

Okay, can you explain what exactly you mean by the computer slowing down when using the DK? And does the DK work as intended or not?

There was a similar error in older nRFConnect versions (v3.8.0) with the same readFWinfo error, but we haven't seen this issue with the latest versions, but I guess you can try the workaround(s) described here: https://devzone.nordicsemi.com/f/nordic-q-a/81989/error-when-fetching-device-versions-readfwinfo-error/340278#340278

Best regards,

Simon

RE: Programmer v2.3.1

DPJONES — Tue, 08 Feb 2022 13:04:57 GMT

Hi Simon

I have now updated the Jlink the problem was Segger's default directory is C:/Program Files, but nRF Connect for Desktops default directory is C:/Program Files(x86).

Unfortunately though the problem still exists.

Kind Regards

David

RE: Programmer v2.3.1

DPJONES — Tue, 08 Feb 2022 10:06:17 GMT

Hi Simon

My Computer is very new AMD Ryzen 9 3900X, I have just downloaded the latest version of JLINK V7.6 installed fine, started up Programmer and still the log shows JLink version: JLink_V6.88a.

V7.6 is in C:\Program Files\SEGGER\JLink but programmer seems to be looking elsewhere.

Kind Regards

David

RE: Programmer v2.3.1

Simonr — Tue, 08 Feb 2022 08:57:40 GMT

I see this suggestion wasn't added in my last reply, but you have a rather old J-Link version installed according to the programmer app, can you try downloading the latest version to see if that helps? Does the DK work as expected with the nRFConnect apps on your computer? It sounds strange that it should slow your computer that much, is your computer by chance very old? Can you also describe how the Dongle is behaving when plugged in, is it pulsing red or behaving differently somehow?

Best regards,

Simon

RE: Programmer v2.3.1

DPJONES — Mon, 07 Feb 2022 15:34:03 GMT

Hi Simon

Thanks for getting back Went through every thing you said including completely deleting nFr Connect and reinstalling the problem still remains the same, I don't know if this has anything to do with it but I have been using the nRF52840DK (not at the same time as the dongle) when the board is running it slows my computer by a factor of 10.

Kind Regards

David

RE: Programmer v2.3.1

Simonr — Mon, 07 Feb 2022 09:59:14 GMT

Just to make sure, what version of the nRF Connect for Desktop app do you have? There was an issue similar to this in v3.8.0 of the Desktop app, so try updating it to the latest version (v3.10.0) if you haven't already.

A few other things you can try is to make sure all J-Link devices (and the Dongles) are disconnected from your computer before launching nRF Connect. Then launch the Programmer app and connect the Dongle to your computer.

If all else fails something might have gone awry when you first downloaded nRF Connect for desktop, try to uninstall nRF Connect altogether. Then make sure the folder C:\Users\___\AppData\Roaming\nrfconnect is empty or deleted before reinstalling nRF Connect for Desktop.

Best regards,

Simon

RE: Programmer v2.3.1

DPJONES — Fri, 04 Feb 2022 12:53:29 GMT

Hi Simon

Thank you for getting back so promptly, unfortunately I have done all the things you have mentioned several times, also we have brought 3 of the dongles and they all have the same problem please see attached screen shots

Its seeing the device?

Regards

David

RE: Programmer v2.3.1

DPJONES — Fri, 04 Feb 2022 12:48:55 GMT

Hi Simon

Thank you for getting back so promptly, unfortunately I have done all the things you have mentioned several times, also we have brought 3 of the

RE: Programmer v2.3.1

Simonr — Fri, 04 Feb 2022 12:23:02 GMT

Hi David

I just tested this on my end and did not have any issues. Are you sure you've set the Dongle into the default bootloader mode that is needed to program the device with new software? In the SELECT DEVICE tab you should see a device named "Open DFU Bootloader" and the Dongle should be pulsing red. In order to get it into this state, press the side mounted button while it is plugged into the computer. You can check out our Dongle Programming tutorial for more details on using the Dongle.

Best regards,

Simon