• State Verified Answer
  • Locked Locked
  • Replies 7 replies
  • Subscribers 74 subscribers
  • Views 4254 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 281009
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

nRF Connect Linux Desktop J-Link issues

swisst

Good day

I have Ubuntu 20.04.3 LTS installed on my laptop + fresh installation ( ~/.nrfconnect-apps was cleared and app reinstalled ) of nRF Connect 3.9.1

I use Bluetooth Low Energy application 3.0.0 and Programmer application 2.0.1, my tools are JLink debugger and nRF USB dongle, my target is nrf52840

1. Programmer issue

JLink is connected to target, target is powered and running. nrfjprog utility successfully flashes/erases target from command line

When I open Programmer app I am not able to select JLink ( no devices at all ) and I get log output as:

13:05:11.337 Failed to get the library versions: JLINKARM_DLL_COULD_NOT_BE_OPENED (Origin: "Failed to get module versions.")
13:05:11.427 Application data folder: /home/vvs/.config/nrfconnect/pc-nrfconnect-programmer
13:05:17.510 Error while probing devices, more details in the debug log: JLINKARM_DLL_COULD_NOT_BE_OPENED (Origin: "Error when running nrfdl_enumerate")
2. Bluetooth Low Energy issues
JLink is connected to target, target is powered and running. NRF USB dongle plugged and discovered as ttyACM device
When I open Bluetooth Low Energy app I am not able to select NRF USB dongle to use within application. I get this log output:
13:57:38.286 Failed to get the library versions: JLINKARM_DLL_COULD_NOT_BE_OPENED (Origin: "Failed to get module versions.")
13:57:38.463 Application data folder: /home/vvs/.config/nrfconnect/pc-nrfconnect-ble
13:57:44.536 Error while probing devices, more details in the debug log: JLINKARM_DLL_COULD_NOT_BE_OPENED (Origin: "Error when running nrfdl_enumerate")
As soon as JLink disconnected and Bluetooth Low Energy app relaunched it NRF USB dongle becomes available in select device section
Please advise hot to overcome this - or did I miss something ?
Thank you
 
  • 0

    Hello,

     

    Unfortunately, we have a known issue with latest versions of nRF connect for Desktop (3.8.0 and 3.9.0), where the workaround is to downgrade to 3.7.0 at this time, and install the corresponding application versions for this version.

    More details and howto do this is described here:

    https://devzone.nordicsemi.com/f/nordic-q-a/81700/how-to-downgrade-nrf-connect

     

    Could you try this and report back if you still run into any issues?

     

    Kind regards,

    Håkon

  • 0 in reply to Håkon Alseth

    Thank you for quick reply

    The manual via your link worked good for Bluetooth Low Energy application - it works as expected

    The only concern is that - Delete bond information is not active for selected adapter ( adapter was re-flashed on application startup, 1 device was bonded )

    Regarding Programmer application - the issue still exist but with other log message

    12:43:14.681 Application data folder: /home/vvs/.config/nrfconnect/pc-nrfconnect-programmer
    12:43:14.722 Using nrfjprog library 10.12.1, pc-nrfjprog-js 1.7.6
    12:43:23.940 Using nrfjprog to communicate with target
    12:43:23.944 Could not fetch memory size of target devkit: Error: Error occured when get library info. Errorcode: CouldNotOpenDevice (0x4) Lowlevel error: Unknown value (ffffff5e)

    2 last lines come after programmer device selected

  • 0

    Hi,

     

    swisst said:
    12:43:14.681 Application data folder: /home/vvs/.config/nrfconnect/pc-nrfconnect-programmer
    12:43:14.722 Using nrfjprog library 10.12.1, pc-nrfjprog-js 1.7.6
    12:43:23.940 Using nrfjprog to communicate with target
    12:43:23.944 Could not fetch memory size of target devkit: Error: Error occured when get library info. Errorcode: CouldNotOpenDevice (0x4) Lowlevel error: Unknown value (ffffff5e)

    Are you able to see a successful detection of the dongle, ie. that it's in bootloader mode?

    Here's some pictures on how it should look:

    https://devzone.nordicsemi.com/guides/short-range-guides/b/getting-started/posts/nrf52840-dongle-programming-tutorial

      

    Kind regards,

    Håkon

  • 0 in reply to Håkon Alseth

    Hi Håkon

    Thank you for reply. I believe you did not get my previous message correctly - anyway I'll try to explain from scratch.

    I use nRF USB dongle with Bluetooth Low Energy application. Regarding this part all issues were solved after I downgrade connect for Desktop to 3.7.1 ( with all apps ).

    Answer for your recent question: It is not my case but even so all works as expected after downgrade. nRF USB dongle is visible in both applications I use ( BLE and programmer ), it can be put into bootloader and re-flashed with both applications.

     

    I still have issues with the second use case: Programmer application + JLink + nrf52840 target. Even after downgrade and with attached target I can not make it work and get an error in log output ( specified above)

    swisst said:
    12:43:14.681 Application data folder: /home/vvs/.config/nrfconnect/pc-nrfconnect-programmer
    12:43:14.722 Using nrfjprog library 10.12.1, pc-nrfjprog-js 1.7.6
    12:43:23.940 Using nrfjprog to communicate with target
    12:43:23.944 Could not fetch memory size of target devkit: Error: Error occured when get library info. Errorcode: CouldNotOpenDevice (0x4) Lowlevel error: Unknown value (ffffff5e)

    Best regards

  • 0 in reply to swisst

    Hi,

     

    swisst said:

    I still have issues with the second use case: Programmer application + JLink + nrf52840 target. Even after downgrade and with attached target I can not make it work and get an error in log output ( specified above)

    My apologies for misunderstanding. Are you able to access the debugger + nrf directly using other tools?

    Like nrfjprog:

    nrfjprog --memrd 0 -f nrf52

     

    Kind regards,

    Håkon

Related
Terms of service