• State Verified Answer
  • Locked Locked
  • Replies 16 replies
  • Subscribers 67 subscribers
  • Views 3834 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)

  • 0 in reply to Marte Myrvold

    As a test I installed the software on a Windows PC.  While Power Profiler's log files show that the device is picked up the device in Linux (device ID DB2BFA1BC4C2) it seems that the device is not picked up in Windows. Here is the Windows log file:

    2022-04-23T14:55:30.291Z DEBUG Application data folder: C:\Users\Ernst\AppData\Roaming\nrfconnect\pc-nrfconnect-ppk
2022-04-23T14:55:30.468Z INFO Using nrf-device-lib-js version: 0.4.5
2022-04-23T14:55:30.469Z INFO Using nrf-device-lib version: 0.11.0
2022-04-23T14:55:30.469Z INFO Using nrfjprog DLL version: 10.15.1
2022-04-23T14:55:30.469Z INFO Using JLink version: JLink_V7.58b
2022-04-23T14:55:30.474Z VERBOSE [nrfdl][trace](16:55:30.419) DeviceLister::enumerate: Checking future_status of enumerate_task_status
2022-04-23T14:55:30.474Z VERBOSE [nrfdl][trace](16:55:30.419) DeviceLister::enumerate: Waiting for enumerate task to complete
2022-04-23T14:55:30.475Z VERBOSE [nrfdl][trace](16:55:30.420) DeviceLister::enumerate::enumerate_task: Start
2022-04-23T14:55:30.476Z VERBOSE [nrfdl][trace](16:55:30.420) DeviceLister::enumerate::enumerate_task: Device_pool is empty
2022-04-23T14:55:30.477Z VERBOSE [nrfdl][trace](16:55:30.420) DeviceLister::enumerate::enumerate_task: Before async_lister->enumarate
2022-04-23T14:55:30.478Z DEBUG [nrfdl][debug](16:55:30.421) Container ID has no value for USB.
2022-04-23T14:55:30.479Z DEBUG [nrfdl][debug](16:55:30.421) Container ID has no value for USB.
2022-04-23T14:55:30.480Z DEBUG [nrfdl][debug](16:55:30.421) Container ID has no value for USB.
2022-04-23T14:55:30.480Z DEBUG [nrfdl][debug](16:55:30.421) Container ID has no value for USB.
2022-04-23T14:55:30.481Z DEBUG [nrfdl][debug](16:55:30.421) Container ID has no value for USB.
2022-04-23T14:55:30.482Z DEBUG [nrfdl][debug](16:55:30.421) Container ID has no value for USB.
2022-04-23T14:55:30.483Z VERBOSE [nrfdl][trace](16:55:30.421) DeviceLister::enumerate::enumerate_task: After async_lister->enumarate
2022-04-23T14:55:30.484Z VERBOSE [nrfdl][trace](16:55:30.421) DeviceLister::enumerate: Enumerating with sync lister
2022-04-23T14:55:30.484Z VERBOSE [nrfdl][trace](16:55:30.421) SerialPortLister::enumerate
2022-04-23T14:55:30.485Z VERBOSE [nrfdl][trace](16:55:30.421) DeviceLister::enumerate: Enumerating with sync lister
2022-04-23T14:55:30.486Z VERBOSE [nrfdl][trace](16:55:30.421) JLinkLister::enumerate
2022-04-23T14:55:30.487Z DEBUG [nrfdl][debug](16:55:30.421) [->] NRFDL::UniversalPlatform::JLinkHW::enumerate
2022-04-23T14:55:30.487Z DEBUG [nrfdl][debug](16:55:30.421) [HighLevel][TID:4728] get_connected_probes
2022-04-23T14:55:30.488Z DEBUG [nrfdl][debug](16:55:30.423) nrfjprog_function return value: 0
2022-04-23T14:55:30.488Z DEBUG [nrfdl][debug](16:55:30.423) [<-] NRFDL::UniversalPlatform::JLinkHW::enumerate [took 1ms]
2022-04-23T14:55:30.489Z VERBOSE [nrfdl][trace](16:55:30.423) DeviceLister::enumerate: Enumerating with sync lister
2022-04-23T14:55:30.490Z VERBOSE [nrfdl][trace](16:55:30.423) BrokenLister::enumerate
2022-04-23T14:55:30.490Z VERBOSE [nrfdl][trace](16:55:30.423) DeviceLister::enumerate: Completed waiting for enumerate task
2022-04-23T14:55:30.491Z VERBOSE [nrfdl][trace](16:55:30.423) DeviceLister::enumerate: done
2022-04-23T14:55:30.516Z DEBUG App pc-nrfconnect-ppk v3.4.3 official
2022-04-23T14:55:30.516Z DEBUG App path: C:\Users\Ernst\.nrfconnect-apps\node_modules\pc-nrfconnect-ppk
2022-04-23T14:55:30.516Z DEBUG nRFConnect 3.11.0, required by the app is (^3.9.2)
2022-04-23T14:55:30.516Z DEBUG nRFConnect path: C:\Users\Ernst\AppData\Local\Programs\nrfconnect\resources\app.asar
2022-04-23T14:55:30.516Z DEBUG HomeDir: C:\Users\Ernst
2022-04-23T14:55:30.516Z DEBUG TmpDir: C:\Users\Ernst\AppData\Local\Temp
2022-04-23T14:55:31.948Z DEBUG iface: Wireless Network Connection
2022-04-23T14:55:31.948Z DEBUG IP4: 192.168.0.105
2022-04-23T14:55:31.948Z DEBUG IP6: fe80::2c63:d487:a7ba:acb5
2022-04-23T14:55:31.948Z DEBUG MAC: 00:0f:b5:f6:27:55
2022-04-23T14:55:31.949Z DEBUG Client Id: 08c3f66a4cf192bfeb4efc211237bbab1dfdc30d
2022-04-23T14:55:31.950Z DEBUG Google Analytics for category pc-nrfconnect-ppk has initialized

  • 0 in reply to cactix

    Hi,

    From your first log it seems like the Power Profiler app is able to find and enumerate your device, so it is strange that it does not show up in the list of devices. Did you make sure to connect the PPK2 to your computer and turn it on before starting the Power Profiler app? I have also experienced sometimes that devices do not show up in the device list immediately, but closing the list and reopening it will make them appear.

    Best regards,

    Marte

  • 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

Related