• State Not Answered
  • Replies 18 replies
  • Subscribers 76 subscribers
  • Views 3065 views
  • Users 0 members are here
Attachments (1) Download All
Nordic Case Info
  • Case ID: 315839
Options

NRF Connect for desktop install fail - blank screen and error windows

Chiprobot

I am trying to install NRF Connect onto a brand new Windows 11 PC (all WIN11 updates made) to program both the PDA10056 and PDA10059 DK's

I installed Segger 5.20a Embedded Software plus the J-Link software plus the NRF SDK and managed to get the blink program compiled and sent to the PDA10056 (Works flawlessly)

To program the PDA10059 Dongle I have tried to install the NRF connect for desktop, a selection screen pops up however when I try to install services they fail with errors (see below) or just give a blank screen with rotating blue swirly thing.

I have checked at the location above and the file does exist there.

I have also uninstalled j-link and segger embedded , then tried reinstalling nrf connect, however same error messages.

I have also tried installing Microsoft Visual Code manually (which works), however nrf connect still fails.

Do you have any ideas on how to proceed ?.

Thanks in anticipation.

Parents Reply Children
  • 0 in reply to Einar Thorsrud

    Update:-

    Has there been any change on the NRF download servers since this posting ?

    The reason I ask is because I have since tried making a manual install of the Connect SDK .

    https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/installation/installing.html

    After installing chocolatey and west I checked the NRF Connect app again and lo-and-behold everything started downloading from your servers!!!

    Don't know if its an issue with a reset of your nrf Connect Download package (licenses) your end or my end now.

    Current Situation :-

    NRF Connect Serial Terminal Installs and works.

    NRF Connect Programmer Installs and works.

    Toolchain Manager installs (however Visual Basic does not pick up my two DK's in the "Connected devices")

    With the PCA 10056 DK (when I issue the command line "nrfjprog -i" in the terminal window it does respond with a serial code of the jlink device so I know the jlink is present and sitting on the "Bus".

    I have tried an uninstall and reinstall (also deleting the app data folder) and also a different version, no change.

    Is there an additional thing you have to do to enable "connected devices"  in VCode ?.

    With the PCA10059 (not sure how to test this from the visual basic command line, however I know it links working with the NRF Connect Programmer/Serial terminal, tested with blink example).

    At least its a step forward, just the "Connected devices" in Visual Studio Code have to sync. in, somehow.

  • 0 in reply to Chiprobot

    Hi,

    Chiprobot said:
    After installing chocolatey and west I checked the NRF Connect app again and lo-and-behold everything started downloading from your servers!!!

    You should not need to install that manually as west and most other dependencies is part of the toolchain distribution, so the fact that this helps indicates an issue of some sorts with you environment or configuration.

    Chiprobot said:
    Has there been any change on the NRF download servers since this posting ?

    There have not been any changes recently that I am aware of, nor any increase in reports of people having problems with downloading from our servers.

    Chiprobot said:
    Is there an additional thing you have to do to enable "connected devices"  in VCode ?.

    It should work out of the box if everything is set up correctly (which should be handled automatically by the toolchain manager), so this could be linked to the toolchain issues it seems you are seeing for some reason. But it could be interesting if you can check which device provider you have selected as shown in this post? If you have the latest versions of the tools, you should normally select "nrfutil", but it would be interesting to know if either of the options work in your case.

  • 0 in reply to Einar Thorsrud
    Einar Thorsrud said:
    But it could be interesting if you can check which device provider you have selected as shown in this post? If you have the latest versions of the tools, you should normally select "nrfutil", but it would be interesting to know if either of the options work in your case.

    Bingo..... the Device Provider had defaulted to "nrfutil" !!!.... when I changed to "nrfjprog" (that is the second selection in its dropdown list) and refreshed the VB's connected devices ......the PDA10056 signed in and is detected correctly.

    I was expecting the PDA10059 dongle to show up there also, alas it is not, should it appear there? or do I have to drop hex files and soft devices to it using the NRF Connect Programmer.

  • 0 in reply to Chiprobot

    Hi,

    Thanks for confirming that switching to nrfjprog helps. Does nrfutil work if you download nrfutil from here, add it in your path and install the device command as explained on the download page?

    Regarding the nRF52840 dongle (pca10059), that will not show up as it does not have an onboard debugger. So you need to use nRf Command Programmer, which will program it via USB DFU.

    Edit: I confirmed that nrfutil is bundled with the VS Code plugin, but it would be good if you could get the stand-alone version and try "nrfutil device list" to see if it lists you DK? Also, can you generate the support information by clicking here and share that?

  • 0 in reply to Einar Thorsrud

    It does manually install ok .... and path set to find it in system variables, however VB code does not pick up the nrfutil utility.

    Command line does find both the PCA10056 and PCA10059

Related
Terms of service