nrf connect desktop app blank screen

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!


Parents Reply Children
  • Thanks for the update. 

    Are you able to run BLE app with verbose logging on and share the log? You will find the option in the about tab in the BLE app

    Regards

    Runar

  • That's what im able to collect with a copy paste. After 2 seconds the blank screen appears:

    4:45.152    Updated list of uuids with data from github.com/.../v1
    14:24:52.672    Selected device with s/n 001050312843
    14:24:53.385    Device setup completed
    14:24:53.386    Note: Adapters with Segger JLink debug probe requires MSD to be disabled to function properly on MacOS and Linux. Please visit www.nordicsemi.com/nRFConnectOSXfix for further instructions.
    14:24:53.386    Getting information from J-Link debugger...
    14:24:53.386    Found device type: unknown. J-Link firmware: J-Link OB-nRF5340-NordicSemi compiled Nov 7 2022 16:22:01.
    14:24:54.095    Connectivity firmware version: 4.1.4. SoftDevice API version: 5.
    14:24:54.097    Opening adapter connected to /dev/ttyACM0

    --------------------

    -------------------

    At some point i was able to get also the following log, but in that case no blank screen appeared, but application still did not go through.

    4:27:36.634    [nrfdl][error](14:27:36.518) NRFDLException(10): Device with ID=1 is not existing in device pool.
    14:27:36.634    Device programming completed.
    14:27:36.634    Device setup completed
    14:27:36.634    Note: Adapters with Segger JLink debug probe requires MSD to be disabled to function properly on MacOS and Linux. Please visit www.nordicsemi.com/nRFConnectOSXfix for further instructions.
    14:27:36.634    Getting information from J-Link debugger...
    14:27:36.634    Found device type: unknown. J-Link firmware: J-Link OB-nRF5340-NordicSemi compiled Nov 7 2022 16:22:01.
    14:27:36.634    [nrfdl][error](14:27:36.622) NRFDLException(10): Device with ID=1 is not existing in device pool.

  • Thanks, do the blank screen happen just after selecting device, or does it happen before?

    Regards

    Runar

  • Thanks

    Could you try to open the app an then disconnect and reconnect the device and then select it and post the logs?

    Regards

    Runar

Related