• State Verified Answer
  • Locked Locked
  • Replies 16 replies
  • Subscribers 67 subscribers
  • Views 3849 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 287874
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

JLINKARM_DLL_COULD_NOT_BE_OPENED

cactix

OS: Ununtu 20.3 LTS - Kernel: 5.4.0-109-generic

Software: Power Profiler launched through nRF Connect for Desktop v3.11.0

Hardware: Power Profiler Kit II

Problem: Cannot connect to PPK2

When I open Power Profiler I get an error: Failed to get the library versions: JLINKARM_DLL_COULD_NOT_BE_OPENED (Origin: "Failed to get module versions.")

Linux itself picks up the device as follows:

[ 3461.245809] usb 1-4: new full-speed USB device number 5 using xhci_hcd
[ 3461.581567] usb 1-4: New USB device found, idVendor=1915, idProduct=c00a, bcdDevice= 1.00
[ 3461.581571] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3461.581574] usb 1-4: Product: PPK2
[ 3461.581576] usb 1-4: Manufacturer: Nordic Semiconductor
[ 3461.581578] usb 1-4: SerialNumber: DB2BFA1BC4C2
[ 3461.617423] cdc_acm 1-4:1.1: ttyACM0: USB ACM device
[ 3461.619424] usbcore: registered new interface driver cdc_acm
[ 3461.619425] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters

systemd gives the following coredump:

PID: 35689 (nrfconnect)
UID: 0 (root)
GID: 0 (root)
Signal: 5 (TRAP)
Timestamp: Tue 2022-04-19 19:01:00 SAST (24h ago)
Command Line: /tmp/.mount_nrfconbY3LnQ/nrfconnect
Executable: /tmp/.mount_nrfconbY3LnQ/nrfconnect
Control Group: /user.slice/user-1000.slice/[email protected]/apps.slice/apps-org.gnome.Terminal.slice/vte-spawn-a0ba016c-0170-4e85-ab33-ccd9e42da6eb.scope
Unit: [email protected]
User Unit: vte-spawn-a0ba016c-0170-4e85-ab33-ccd9e42da6eb.scope
Slice: user-1000.slice
Owner UID: 1000 (ernst)
Boot ID: 98fd9a43018e441e963214193a048de0
Machine ID: 09143d0261be487380a9ec9bf41d5922
Hostname: ernst
Storage: /var/lib/systemd/coredump/core.nrfconnect.0.98fd9a43018e441e963214193a048de0.35689.1650387660000000000000.lz4
Message: Process 35689 (nrfconnect) of user 0 dumped core.

Stack trace of thread 35689:
#0 0x000055645b12ace3 n/a (/tmp/.mount_nrfconbY3LnQ/nrfconnect + 0x4685ce3)
#1 0x0000556458895f98 n/a (/tmp/.mount_nrfconbY3LnQ/nrfconnect + 0x1df0f98)
#2 0x000055645963294c n/a (/tmp/.mount_nrfconbY3LnQ/nrfconnect + 0x2b8d94c)
#3 0x00005564596312e3 n/a (/tmp/.mount_nrfconbY3LnQ/nrfconnect + 0x2b8c2e3)
#4 0x0000556459631432 n/a (/tmp/.mount_nrfconbY3LnQ/nrfconnect + 0x2b8c432)
#5 0x0000556458892f0e n/a (/tmp/.mount_nrfconbY3LnQ/nrfconnect + 0x1dedf0e)
#6 0x00007f92505530b3 __libc_start_main (libc.so.6 + 0x240b3)
#7 0x000055645858a96a n/a (/tmp/.mount_nrfconbY3LnQ/nrfconnect + 0x1ae596a)

Parents
  • 0

    Hi,

    What version of nfjprog and JLink do you have installed? You can find this by running 'nrfjprog --version'. If you do not have nrfjprog v10.15.4 and JLink v7.58b please try installing or updating to these versions and see if this solves the issue.

    Best regards,

    Marte

  • 0 in reply to Marte Myrvold

    Thanks, I had nrfjprog installed, but the command nrfjprog -- version showed:

    nrfjprog --version
    ERROR: JLinkARM DLL load failed. Try again. If it keeps failing, please
    ERROR: reinstall latest JLinkARM from Segger webpage.
    NOTE: For additional output, try running again with logging enabled (--log).
    NOTE: Any generated log error messages will be displayed.

    I installed JLink v7.58b and now it starts without errors and Power Profiler shows:

    21:09:17.274    Using nrf-device-lib-js version: 0.4.5
    21:09:17.274    Using nrf-device-lib version: 0.11.0
    21:09:17.274    Using nrfjprog DLL version: 10.15.1
    21:09:17.274    Using JLink version: JLink_V7.58b

    When I however click on "SELECT DEVICE" the PPK2 is not listed.  The screen displays "Connect a Nordic development kit to your computer".  Linux did pickup the PPK2 when I connected the device as follows:

    [ 3709.425093] usb 1-4: USB disconnect, device number 6
    [ 3715.999059] usb 1-4: new full-speed USB device number 7 using xhci_hcd
    [ 3716.327105] usb 1-4: New USB device found, idVendor=1915, idProduct=c00a, bcdDevice= 1.00
    [ 3716.327109] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [ 3716.327111] usb 1-4: Product: PPK2
    [ 3716.327113] usb 1-4: Manufacturer: Nordic Semiconductor
    [ 3716.327115] usb 1-4: SerialNumber: DB2BFA1BC4C2
    [ 3716.345998] cdc_acm 1-4:1.1: ttyACM0: USB ACM device

  • 0 in reply to Marte Myrvold

    Yes, the device is connected before I load Power Profiler (and that is a requirement if verbose logging is enabled as Power Profiler restarts).  I even tried restarting the computer with the device connected. 

    I tried all the USB ports and even tried a powered USB hub. In all cases the device shows in both Linux and in the Power Profiler's verbose log file, but not under "Select Device".

    The device is band new.  Could it be a hardware problem? Your help is appreciated as I need to get this fixed ASAP.

  • 0 in reply to cactix

    Okey, as a sanity check I completed the Installation on a clean Windows Install.  I downloaded nrfconnect-setup-3.11.0-ia32.exe.  I automatically downloaded and installed JLink_V7.58b.  I noticed it did not install the command line tools.  After installing Power Profiler it works.  I don't understand why it does not work in Linux, as it picks up the device in the logs files, but I will debug.  At least the device seems to be working although I did not take any readings.

  • 0 in reply to cactix

    Hi,

    Good to hear that it works in Windows and ruling out the PPK2 itself as the issue. I have forwarded your logs from Linux to the developers, and I am waiting on a reply. I will let you know when I hear back from them.

    Best regards,

    Marte

  • 0 in reply to Marte Myrvold

    That fixed the issue! Thanks!

    I use a lot of udev settings. It could be that my settings clashed with the PPK2 until the PPK2 udev settings were explicitly specified.

Reply Children
Related