• State Suggested Answer
  • Replies 19 replies
  • Answers 3 answers
  • Subscribers 70 subscribers
  • Views 4456 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 252594
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nRF connect for desktop BLE & DTM apps opens with a blank window

eyalasko

Hi,

Like many posts before I'm facing blank white screen when trying to run nRFCOnnect for desktop (3.4.1) BLE app (2.4.0)

Tried to:

  • Restart PC
  • Uninstall-reinstall 3.4.1
  • Uninstall-reinstall 3.4.0
  • Uninstall-install latest nrf command line tools-reinstall (link)
  • Use nRF52840 (PCA10056) dongle
  • Use nRF52832 (PCA10031) dongle
  • Use another fresh nRF52840 dongle

all to no avail....

Same blank screen occurs on all other NRFConnect's apps: DTM, RSSI viewer, Programmer but NOT with the toolchain manager... implying it stems from (probably) the same root cause (jlink driver? graphic library?)

Any advise ?

Parents
  • 0

    I am having the exact same issue, however, I had been using the BLE app for 3 weeks and have changed nothing. Now, all of a sudden today, I have the blank with screen. I have no other apps running. I.E. nothing claiming the COM ports. I have uninstalled and reinstalled the app, reboot, etc. 

    Are there any other ideas?

    I have:

    BLE tool v4.0.4

    nRF Connect for Desktop v4.1.2

    thanks

  • 0 in reply to scottesimon

    I am running Ubuntu 22.04 and use nRF Connect for Desktop v4.1.2

    My BLE tool v4.0.4 window blanks only after selecting the adapter/USB device (both nRF52840 DK and nRF52 DK, adapter programming / image download through JLink still works). It is similar to the problem described here

    Other nRF Connect applications (e.g. RSSI viewer) work fine.

    Reinstalling nrf command line tools as suggested and even downgrading JLink do not help in my case. 

    I double checked my udev rules and read/write permission to serial ports, ttyACM / CDC)

    It had been working until yesterday, I never had the "blank window" issue before. Ctrl-R does not help, it will just repeat the crash. From my /var/log/syslog:

    systemd[1]: tmp-.mount_nrfconf256ro.mount: Deactivated successfully.

    ...
    kernel: [ 78.648080] nrfconnect-blue[1821]: segfault at 0 ip 00007fca09eb542b sp 00007fca05dfcba8 error 4 in libstdc++.so.6.0.30[7fca09e7d000+111000]
    kernel: [ 78.648121] Code: 0f 1f 80 00 00 00 00 31 d2 e9 14 ff ff ff 90 49 89 f0 48 8b 0f 48 8b 77 08 48 89 fa b8 fe ff ff ff 48 29 ce 0f 84 8a 00 00 00 <0f> b6 01 83 f8 7f 0f 86 89 00 00 00 3d c1 00 00 00 76 72 3d df 00

  • 0 in reply to Jakob

    I'm on Kubuntu 22.04 and same is happening to me after an update. nRF connect for desktop and the ble standalone are fully up to date but after selecting a device in ble standalone the window goes blank white and ctrl+r just causes it to close.

  • 0 in reply to Jakob

    I was able to reproduce the issue on a second system. It worked until i performed an apt upgrade. So it must be related to any of the packages listed below

    I downgraded  libstdc++6  to an older version and my application works again

  • 0 in reply to Jakob

    If not too complicated, can you share how you downgraded libstdc++6 ?
    I have the same blank screen since today (was working perfectly yesterday), I'd like to confirm that this is the same issue.
    Thanks !

  • 0 in reply to MCA

    I don't have a linux computer today, but it used to be something similar to this

    sudo apt install pkg_name=version

    You may want to uninstall the current version you have installed

    sudo apt remove pkg_name

    Regards

    Runar

  • 0 in reply to runsiv

    I was not able to do it that way, since the earlier version libstdc++6=12.1.0-1ubuntu1~22.04 seems not to be available any more on the update server (but only 12.3.0, with which the conflict seems to occur). I still got an earlier version for my distro and architecture. I placed the file in  /usr/lib  and re-linked  libstdc++.so.6  to that file.

    That was my quick workaround - mainly to prove that my problem has to do with libstdc++6 12.3.0. It is certainly not recommended, also for security reasons!

Reply
  • 0 in reply to runsiv

    I was not able to do it that way, since the earlier version libstdc++6=12.1.0-1ubuntu1~22.04 seems not to be available any more on the update server (but only 12.3.0, with which the conflict seems to occur). I still got an earlier version for my distro and architecture. I placed the file in  /usr/lib  and re-linked  libstdc++.so.6  to that file.

    That was my quick workaround - mainly to prove that my problem has to do with libstdc++6 12.3.0. It is certainly not recommended, also for security reasons!

Children
Related