nrf connect desktop app blank screen

[gorazd]

I have read the related issues, none of them provided a solution for me. There was one answer which suggested to downgraded libstdc++6 as a solution without giving any specific instructions on how to do that, what version etc.

So, the 'Bluetooth low energy app' is suddenly starting with blank screen after trying to flash the firmware at the start. Other apps work fine (e.g. power profiler).

I am on Ubuntu 22.04.2 LTS 64bit using nrfconnect-4.1.2-x86_64.AppImage, nrf-command-line-tools_10.23.0_amd64.deb

I would like to use the app to perform dfu upgrades. I also tried that with nrfutil (nrfutil 7.1.0 (c86ddc2 2022-11-29)):

nrfutil device program --firmware dfu_mtk_v0.11.3_7b555.zip --serial-number 1050312843

gorazd@gorazd-Victus-by-HP-Laptop-16-e0xxx:~/Programs/nrf-rust/firmware$ nrfutil device program --firmware dfu_mtk_v0.11.3_7b555.zip --serial-number 1050312843
[00:00:02] ------   0% [2/3 1050312843] Failed, [jlink] INTERNAL_ERROR
Error: One or more program tasks failed

Enter your choice: : 0
  [------------------------------------]    0%
Traceback (most recent call last):
  File "nordicsemi/__main__.py", line 1555, in <module>
  File "click/core.py", line 1137, in __call__
  File "click/core.py", line 1062, in main
  File "click/core.py", line 1668, in invoke
  File "click/core.py", line 1668, in invoke
  File "click/core.py", line 1404, in invoke
  File "click/core.py", line 763, in invoke
  File "nordicsemi/__main__.py", line 1215, in ble
  File "nordicsemi/dfu/dfu.py", line 115, in dfu_send_images
  File "nordicsemi/dfu/dfu.py", line 88, in _dfu_send_image
  File "nordicsemi/dfu/dfu_transport_ble.py", line 474, in open
  File "nordicsemi/dfu/dfu_transport_ble.py", line 103, in open
  File "pc_ble_driver_py/ble_driver.py", line 106, in wrapper
pc_ble_driver_py.exceptions.NordicSemiException: Failed to open. Error code: NRF_ERROR_TIMEOUT
[75261] Failed to execute script '__main__' due to unhandled exception!

[runsiv]

Hi, 

I have asked the developers regarding question 1

Regarding question 2. Do you have https://github.com/NordicSemiconductor/nrf-udev installed?

Regards

Runar

[gorazd]

hi,

number 2 i found the solution on forum (port flag should be explicitly given, snr is not enough):

nrfutil dfu ble -pkg dfu_edh_0.11.4_for_testing_purpose.zip -ic NRF52 -n DfuMTK -p /dev/ttyACM0 -f

Problem 1 still persists.

[gorazd]

Fullscreen 2023-08-22T07_20_31.797Z-log.txt Download

2023-08-22T07:20:32.124Z DEBUG Application data folder: /home/gorazd/.config/nrfconnect-bluetooth-low-energy/bundle
2023-08-22T07:20:32.200Z INFO Using nrf-device-lib-js version: 0.4.4
2023-08-22T07:20:32.200Z INFO Using nrf-device-lib version: 0.10.3
2023-08-22T07:20:32.200Z INFO Using nrfjprog DLL version: 10.15.1
2023-08-22T07:20:32.200Z INFO Using JLink version: JLink_V7.86e
2023-08-22T07:20:32.207Z DEBUG App pc-nrfconnect-ble v4.0.4 official
2023-08-22T07:20:32.207Z DEBUG App path: /tmp/.mount_nrfcon2XsxeX/resources/app.asar/resources/bundle/
2023-08-22T07:20:32.207Z DEBUG nRFConnect 4.0.4, required by the app is (^3.8.0)
2023-08-22T07:20:32.207Z DEBUG nRFConnect path: /tmp/.mount_nrfcon2XsxeX/resources/app.asar
2023-08-22T07:20:32.207Z DEBUG HomeDir: /home/gorazd
2023-08-22T07:20:32.207Z DEBUG TmpDir: /tmp
2023-08-22T07:20:32.229Z INFO Installed JLink version does not match the provided version (V7.66a)
2023-08-22T07:20:32.232Z INFO Updated list of uuids with data from https://github.com/NordicSemiconductor/bluetooth-numbers-database/tree/master/v1

2023-08-22T07_22_59.745Z-log.txt

Procedure:


* Open nrf connect app

* start Nrf connect for Deskto BLE...

* Recover and disable protection on nrf52 dev board:

gorazd@gorazd-Victus-by-HP-Laptop-16-e0xxx:~$ nrfjprog --recover
Recovering device. This operation might take 30s.
Erasing user code and UICR flash areas.
Writing image to disable ap protect.
gorazd@gorazd-Victus-by-HP-Laptop-16-e0xxx:~$ nrfjprog --memwr 0x10001200 --val 0xfffffffe
Parsing parameters.
Writing.
gorazd@gorazd-Victus-by-HP-Laptop-16-e0xxx:~$


* ABOUT -> verbose logging -> restart with verbose logging


* unplug and plug back in nrf52 dev board into usb port


* Select Device -> NRF52DK -> Device must be prorammed, do you want t proceed? Yes

* BLANK SCREEN

[runsiv]

Sorry I forgot to post my replay earlier. Thanks for the logs, I'm awaiting feedback from the developers and will update as soon as they get back to me

Regards

Runar

[runsiv]

Hi, 

The supported version with the app should be

JLink_V7.66a. The developer has also tested with JLink_V7.80c. Can you try if this works for you?

Regards

Runar

[Aleks]

I have the same problem ,with the white-screen suddenly popping up after at least one year of usage on Ubuntu 22.04.3 LTS and this is the output I get from the nRF Connect BLE application:

10:33:01.092 Using JLink version: JLink_V7.80c

10:33:01.121 Installed JLink version does not match the provided version (V7.66a)

So the application starts and it is possible to select the nRF connect device in the device drop-down list, but get a white-screen as soon as this is chosen. In my dmesg I can see this:

[ 1811.420595] nrfconnect-blue[5370]: segfault at 0 ip 00007fdebf28842b sp 00007fdeb99faba8 error 4 in libstdc++.so.6.0.30[7fdebf250000+111000]
[ 1811.420615] nrfconnect-blue[5386]: segfault at 0 ip 00007fdebf28842b sp 00007fdeb4bba658 error 4

[ 1811.420626] 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
[ 1811.420636] in libstdc++.so.6.0.30[7fdebf250000+111000]
[ 1811.420646] 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

So it still feels kind of related to the libstdc++ version. Any new suggestions?

BR,

Aleks

[runsiv]

Hi 

The best suggest I can provide is to downgrade libstdc++ to an older tag. The developers has identified the cause of the issue however it does not look like there will be any way to fix it in the near future which does not require downgrading libstc++ 

I would recommend trying the solution posted here, 

Regards

Runar

[Aleks]

Thanks for the quick response, would be great if you could specify which  libstdc++ version to downgrade to. This was also asked for in the solution post you provided here, but no further info there.

BR,

Aleks

[runsiv]

Hi, 

I don't have access to a Linux desktop today I can't verify this fix on my end. however I heard from a coworker that downgrading it by a tag worked from him, so https://ubuntu.pkgs.org/22.04/ubuntu-main-arm64/libstdc++6_12-20220319-1ubuntu1_arm64.deb.html this version can be worth trying

Regards

Runar