• State Verified Answer
  • +1 person also asked this people also asked this
  • Replies 9 replies
  • Subscribers 75 subscribers
  • Views 7361 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 119084
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nrf connect 1.1 - white/empty window (PC version)

Moritz

Hi,

I just installed nrf connect 1.1 on my Dev-PC (many versions of J-Link and nrfjprog) everything works fine. The visualization of Secure-DFU-Upload-Speed is really nice!

But on 2 PCs of my colleague, we only get a white/empty window when starting Nrf Connect 1.1.

The directory "C:\Users<username>\AppData\Roaming\nrfconnect" gets created and the files seam to be the same than on my machine, but there is no log file. The latest nrf5x command line tools are also installed.

Any ideas what might be happening?

Opening the debugging console shows this. The truncated path goes to ../bindings.js"

V1.1_2.jpg

image description

Parents
  • 0

    Judging by the console message, this seems to be a different problem. If it was related to missing VC++ redistributable files, the application would have failed to do module loading, as shown in the screenshots above.

    It is able to get past the module loading step, and the application starts rendering, but then it fails with "DevTools was disconnected from the page". This typically means that the application tried to run some native code, which crashed. This is unfortunately a bit hard to debug.

    When the application starts, one of the first things it does is to look for connected devices. You could try to unplug all devkits before starting the application to see if it makes any difference. Also, check if something is printed to the log file in C:\Users<username>\AppData\Roaming\nrfconnect.

Reply
  • 0

    Judging by the console message, this seems to be a different problem. If it was related to missing VC++ redistributable files, the application would have failed to do module loading, as shown in the screenshots above.

    It is able to get past the module loading step, and the application starts rendering, but then it fails with "DevTools was disconnected from the page". This typically means that the application tried to run some native code, which crashed. This is unfortunately a bit hard to debug.

    When the application starts, one of the first things it does is to look for connected devices. You could try to unplug all devkits before starting the application to see if it makes any difference. Also, check if something is printed to the log file in C:\Users<username>\AppData\Roaming\nrfconnect.

Children
Related
Terms of service