JLINKARM_DLL_COULD_NOT_BE_OPENED

RE: JLINKARM_DLL_COULD_NOT_BE_OPENED

cactix — Wed, 27 Dec 2023 13:56:02 GMT

Do the following to install:

Test if the device is found under Linux:

Execute:

sudo dmesg |tail -n 10

It should give an output similar to this:

[ 1831.263435] usb 1-4: USB disconnect, device number 2
[ 1847.709868] usb 1-4: new full-speed USB device number 4 using xhci_hcd
[ 1848.038989] usb 1-4: New USB device found, idVendor=1915, idProduct=c00a, bcdDevice= 1.00
[ 1848.038994] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1848.038996] usb 1-4: Product: PPK2
[ 1848.038997] usb 1-4: Manufacturer: Nordic Semiconductor
[ 1848.038999] usb 1-4: SerialNumber: DB2BFA1BC4C2
[ 1848.067804] cdc_acm 1-4:1.1: ttyACM0: USB ACM device
[ 1848.067823] usbcore: registered new interface driver cdc_acm
[ 1848.067824] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters

Download:
1) The AppImage for nrf Connect for Desktop for Linux

https://www.nordicsemi.com/Products/Development-tools/nRF-Connect-for-desktop/Download#infotabs

2) JLink v7.88j 64-bit (Note you must use this version as of 2023/12/27)

https://www.segger.com/downloads/jlink/

3) nrf-udev
https://github.com/NordicSemiconductor/nrf-udev/releases

Install:
1) sudo dpkg -i JLink_Linux_V788j_x86_64.deb
2) sudo dpkg -i nrf-udev_1.0.1-all.deb
2) Execute the nrf Connect AppImage (nrfconnect-4.3.0-x86_64.appimage - for December 2023)
3) Install Power Profiler

RE: JLINKARM_DLL_COULD_NOT_BE_OPENED

danielsyguides — Wed, 27 Dec 2023 05:18:17 GMT

[deleted]

RE: JLINKARM_DLL_COULD_NOT_BE_OPENED

billie34 — Mon, 16 Jan 2023 03:34:38 GMT

My Ubuntu 20.04 computer has Segar Systemview installed. But when I attempt to launch SystemView in my terminal, an error message appears.

Could not open J-Link shared library. Exiting now.

I followed the below link to solve the issue but I am unable to find /lib64/libudev.so.1 in my pc. I have also tried to install the latest version of JLink, but the installation failed with error. word wipe

RE: JLINKARM_DLL_COULD_NOT_BE_OPENED

cactix — Wed, 27 Apr 2022 14:48:05 GMT

For others having difficulties, the install instructions that should work for most Linux installations are as follows:

Download:
1) nrf Connect for Desktop
www.nordicsemi.com/.../Download

2) JLink v7.58b
www.segger.com/.../

3) nrf-udev
github.com/.../releases

Install:
1) sudo dpkg -i JLink_Linux_V758b_x86_64.deb
2) sudo dpkg -i nrf-udev_1.0.1-all.deb
2) Execute the nrf Connect AppImage (nrfconnect-3.11.0-x86_64.appimage - for April 2022)
3) Install Power Profiler

RE: JLINKARM_DLL_COULD_NOT_BE_OPENED

cactix — Wed, 27 Apr 2022 14:38:57 GMT

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.

RE: JLINKARM_DLL_COULD_NOT_BE_OPENED

Marte Myrvold — Wed, 27 Apr 2022 13:34:03 GMT

Hi,

Can you try installing the nrf-udev package and see if it solves your issue?

https://github.com/NordicSemiconductor/pc-nrfconnect-launcher#linux-only

https://github.com/NordicSemiconductor/nrf-udev/releases

Best regards,

Marte

RE: JLINKARM_DLL_COULD_NOT_BE_OPENED

Marte Myrvold — Wed, 27 Apr 2022 06:13:45 GMT

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

RE: JLINKARM_DLL_COULD_NOT_BE_OPENED

cactix — Tue, 26 Apr 2022 12:40:08 GMT

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.

RE: JLINKARM_DLL_COULD_NOT_BE_OPENED

cactix — Tue, 26 Apr 2022 12:20:00 GMT

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.

RE: JLINKARM_DLL_COULD_NOT_BE_OPENED

Marte Myrvold — Tue, 26 Apr 2022 10:55:58 GMT

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

RE: JLINKARM_DLL_COULD_NOT_BE_OPENED

cactix — Sat, 23 Apr 2022 15:03:52 GMT

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

RE: JLINKARM_DLL_COULD_NOT_BE_OPENED

cactix — Fri, 22 Apr 2022 15:50:25 GMT

RE: JLINKARM_DLL_COULD_NOT_BE_OPENED

cactix — Fri, 22 Apr 2022 15:48:53 GMT

2022-04-22T15:47:28.922Z DEBUG Application data folder: /home/ernst/.config/nrfconnect/pc-nrfconnect-ppk
2022-04-22T15:47:29.293Z DEBUG iface: wlxd8eb9715f4de
2022-04-22T15:47:29.293Z DEBUG IP4: 192.168.0.175
2022-04-22T15:47:29.294Z DEBUG IP6: fe80::6d13:88d5:40f9:e8e2
2022-04-22T15:47:29.294Z DEBUG MAC: d8:eb:97:15:f4:de
2022-04-22T15:47:29.296Z DEBUG Client Id: d4d6150c6ee12f569fda873000e7baea2bd7f2f1
2022-04-22T15:47:29.298Z DEBUG Google Analytics for category pc-nrfconnect-ppk has initialized
2022-04-22T15:47:29.376Z INFO Using nrf-device-lib-js version: 0.4.5
2022-04-22T15:47:29.376Z INFO Using nrf-device-lib version: 0.11.0
2022-04-22T15:47:29.376Z INFO Using nrfjprog DLL version: 10.15.1
2022-04-22T15:47:29.376Z INFO Using JLink version: JLink_V7.58b
2022-04-22T15:47:29.380Z VERBOSE [nrfdl][trace](17:47:28.926) [NRFJPROG] [SeggerBackend] [Debug] Segger Backend closed.
2022-04-22T15:47:29.381Z VERBOSE [nrfdl][trace](17:47:28.926) [NRFJPROG] [nRFXX] [Debug] nRF family DLL closed
2022-04-22T15:47:29.382Z VERBOSE [nrfdl][trace](17:47:29.027) DeviceLister::enumerate: Checking future_status of enumerate_task_status
2022-04-22T15:47:29.382Z VERBOSE [nrfdl][trace](17:47:29.027) DeviceLister::enumerate: Waiting for enumerate task to complete
2022-04-22T15:47:29.383Z VERBOSE [nrfdl][trace](17:47:29.027) DeviceLister::enumerate::enumerate_task: Start
2022-04-22T15:47:29.384Z VERBOSE [nrfdl][trace](17:47:29.027) DeviceLister::enumerate::enumerate_task: Device_pool is empty
2022-04-22T15:47:29.384Z VERBOSE [nrfdl][trace](17:47:29.027) DeviceLister::enumerate::enumerate_task: Before async_lister->enumarate
2022-04-22T15:47:29.385Z VERBOSE [nrfdl][trace](17:47:29.027) USBPlatformAPI::enumerate: Starting iteration 0
2022-04-22T15:47:29.385Z VERBOSE [nrfdl][trace](17:47:29.027) USBPlatformAPI::enumerate: Doing copyDeviceToUsb of device #0
2022-04-22T15:47:29.386Z DEBUG [nrfdl][debug](17:47:29.028) NRFDLException(6): Unable to open USB device. Error code: -3. idProduct=3, idVendor=7531
2022-04-22T15:47:29.387Z VERBOSE [nrfdl][trace](17:47:29.028) USBPlatformAPI::enumerate: new device is not registered, skipping to next entry in list!
2022-04-22T15:47:29.387Z VERBOSE [nrfdl][trace](17:47:29.028) USBPlatformAPI::enumerate: Starting iteration 1
2022-04-22T15:47:29.388Z VERBOSE [nrfdl][trace](17:47:29.028) USBPlatformAPI::enumerate: Doing copyDeviceToUsb of device #1
2022-04-22T15:47:29.388Z DEBUG [nrfdl][debug](17:47:29.028) NRFDLException(6): Unable to open USB device. Error code: -3. idProduct=50484, idVendor=1133
2022-04-22T15:47:29.389Z VERBOSE [nrfdl][trace](17:47:29.028) USBPlatformAPI::enumerate: new device is not registered, skipping to next entry in list!
2022-04-22T15:47:29.389Z VERBOSE [nrfdl][trace](17:47:29.028) USBPlatformAPI::enumerate: Starting iteration 2
2022-04-22T15:47:29.390Z VERBOSE [nrfdl][trace](17:47:29.028) USBPlatformAPI::enumerate: Doing copyDeviceToUsb of device #2
2022-04-22T15:47:29.390Z DEBUG [nrfdl][debug](17:47:29.028) NRFDLException(6): Unable to open USB device. Error code: -3. idProduct=2, idVendor=7531
2022-04-22T15:47:29.391Z VERBOSE [nrfdl][trace](17:47:29.028) USBPlatformAPI::enumerate: new device is not registered, skipping to next entry in list!
2022-04-22T15:47:29.391Z VERBOSE [nrfdl][trace](17:47:29.028) USBPlatformAPI::enumerate: Starting iteration 3
2022-04-22T15:47:29.392Z VERBOSE [nrfdl][trace](17:47:29.028) USBPlatformAPI::enumerate: Doing copyDeviceToUsb of device #3
2022-04-22T15:47:29.392Z DEBUG [nrfdl][debug](17:47:29.028) NRFDLException(6): Unable to open USB device. Error code: -3. idProduct=2067, idVendor=8457
2022-04-22T15:47:29.393Z VERBOSE [nrfdl][trace](17:47:29.028) USBPlatformAPI::enumerate: new device is not registered, skipping to next entry in list!
2022-04-22T15:47:29.393Z VERBOSE [nrfdl][trace](17:47:29.028) USBPlatformAPI::enumerate: Starting iteration 4
2022-04-22T15:47:29.394Z VERBOSE [nrfdl][trace](17:47:29.028) USBPlatformAPI::enumerate: Doing copyDeviceToUsb of device #4
2022-04-22T15:47:29.395Z DEBUG [nrfdl][debug](17:47:29.028) NRFDLException(6): Unable to open USB device. Error code: -3. idProduct=3, idVendor=7531
2022-04-22T15:47:29.395Z VERBOSE [nrfdl][trace](17:47:29.028) USBPlatformAPI::enumerate: new device is not registered, skipping to next entry in list!
2022-04-22T15:47:29.396Z VERBOSE [nrfdl][trace](17:47:29.028) USBPlatformAPI::enumerate: Starting iteration 5
2022-04-22T15:47:29.396Z VERBOSE [nrfdl][trace](17:47:29.028) USBPlatformAPI::enumerate: Doing copyDeviceToUsb of device #5
2022-04-22T15:47:29.397Z DEBUG [nrfdl][debug](17:47:29.028) NRFDLException(6): Unable to open USB device. Error code: -3. idProduct=20, idVendor=3468
2022-04-22T15:47:29.397Z VERBOSE [nrfdl][trace](17:47:29.028) USBPlatformAPI::enumerate: new device is not registered, skipping to next entry in list!
2022-04-22T15:47:29.398Z VERBOSE [nrfdl][trace](17:47:29.028) USBPlatformAPI::enumerate: Starting iteration 6
2022-04-22T15:47:29.398Z VERBOSE [nrfdl][trace](17:47:29.028) USBPlatformAPI::enumerate: Doing copyDeviceToUsb of device #6
2022-04-22T15:47:29.399Z DEBUG [nrfdl][debug](17:47:29.028) NRFDLException(6): Unable to open USB device. Error code: -3. idProduct=49162, idVendor=6421
2022-04-22T15:47:29.399Z VERBOSE [nrfdl][trace](17:47:29.028) USBPlatformAPI::enumerate: new device is not registered, skipping to next entry in list!
2022-04-22T15:47:29.400Z VERBOSE [nrfdl][trace](17:47:29.028) USBPlatformAPI::enumerate: Starting iteration 7
2022-04-22T15:47:29.400Z VERBOSE [nrfdl][trace](17:47:29.028) USBPlatformAPI::enumerate: Doing copyDeviceToUsb of device #7
2022-04-22T15:47:29.401Z DEBUG [nrfdl][debug](17:47:29.028) NRFDLException(6): Unable to open USB device. Error code: -3. idProduct=25165, idVendor=8436
2022-04-22T15:47:29.401Z VERBOSE [nrfdl][trace](17:47:29.028) USBPlatformAPI::enumerate: new device is not registered, skipping to next entry in list!
2022-04-22T15:47:29.402Z VERBOSE [nrfdl][trace](17:47:29.028) USBPlatformAPI::enumerate: Starting iteration 8
2022-04-22T15:47:29.403Z VERBOSE [nrfdl][trace](17:47:29.028) USBPlatformAPI::enumerate: Doing copyDeviceToUsb of device #8
2022-04-22T15:47:29.403Z DEBUG [nrfdl][debug](17:47:29.028) NRFDLException(6): Unable to open USB device. Error code: -3. idProduct=10259, idVendor=8457
2022-04-22T15:47:29.404Z VERBOSE [nrfdl][trace](17:47:29.028) USBPlatformAPI::enumerate: new device is not registered, skipping to next entry in list!
2022-04-22T15:47:29.404Z VERBOSE [nrfdl][trace](17:47:29.028) USBPlatformAPI::enumerate: Starting iteration 9
2022-04-22T15:47:29.405Z VERBOSE [nrfdl][trace](17:47:29.028) USBPlatformAPI::enumerate: Doing copyDeviceToUsb of device #9
2022-04-22T15:47:29.405Z DEBUG [nrfdl][debug](17:47:29.028) NRFDLException(6): Unable to open USB device. Error code: -3. idProduct=2, idVendor=7531
2022-04-22T15:47:29.406Z VERBOSE [nrfdl][trace](17:47:29.028) USBPlatformAPI::enumerate: new device is not registered, skipping to next entry in list!
2022-04-22T15:47:29.406Z VERBOSE [nrfdl][trace](17:47:29.028) USBPlatformAPI::enumerate: Found 0 devices
2022-04-22T15:47:29.407Z VERBOSE [nrfdl][trace](17:47:29.028) DeviceLister::enumerate::enumerate_task: After async_lister->enumarate
2022-04-22T15:47:29.408Z VERBOSE [nrfdl][trace](17:47:29.028) DeviceLister::enumerate: Enumerating with sync lister
2022-04-22T15:47:29.409Z VERBOSE [nrfdl][trace](17:47:29.028) SerialPortLister::enumerate
2022-04-22T15:47:29.410Z DEBUG [nrfdl][debug](17:47:29.028) Linux serialport enumerate.
2022-04-22T15:47:29.411Z VERBOSE [nrfdl][trace](17:47:29.034) DeviceLister::enumerate: Enumerating with sync lister
2022-04-22T15:47:29.412Z VERBOSE [nrfdl][trace](17:47:29.034) JLinkLister::enumerate
2022-04-22T15:47:29.412Z DEBUG [nrfdl][debug](17:47:29.034) [->] enumerate
2022-04-22T15:47:29.413Z DEBUG [nrfdl][debug](17:47:29.034) [HighLevel][TID:139646854645504] get_connected_probes
2022-04-22T15:47:29.413Z DEBUG [nrfdl][debug](17:47:29.035) nrfjprog_function return value: 0
2022-04-22T15:47:29.414Z DEBUG [nrfdl][debug](17:47:29.035) [<-] enumerate [took 0ms]
2022-04-22T15:47:29.415Z VERBOSE [nrfdl][trace](17:47:29.035) DeviceLister::enumerate: Enumerating with sync lister
2022-04-22T15:47:29.415Z VERBOSE [nrfdl][trace](17:47:29.035) BrokenLister::enumerate
2022-04-22T15:47:29.416Z VERBOSE [nrfdl][trace](17:47:29.035) DeviceLister::enumerate: Found device with serial number: DB2BFA1BC4C2
2022-04-22T15:47:29.416Z VERBOSE [nrfdl][trace](17:47:29.035) DeviceLister::enumerate: Completed waiting for enumerate task
2022-04-22T15:47:29.417Z VERBOSE [nrfdl][trace](17:47:29.035) DeviceLister::enumerate: done
2022-04-22T15:47:29.433Z DEBUG App pc-nrfconnect-ppk v3.4.3 official
2022-04-22T15:47:29.433Z DEBUG App path: /home/ernst/.nrfconnect-apps/node_modules/pc-nrfconnect-ppk
2022-04-22T15:47:29.434Z DEBUG nRFConnect 3.11.0, required by the app is (^3.9.2)
2022-04-22T15:47:29.434Z DEBUG nRFConnect path: /tmp/.mount_nrfcontJCjF0/resources/app.asar
2022-04-22T15:47:29.434Z DEBUG HomeDir: /home/ernst
2022-04-22T15:47:29.434Z DEBUG TmpDir: /tmp

RE: JLINKARM_DLL_COULD_NOT_BE_OPENED

Marte Myrvold — Fri, 22 Apr 2022 07:53:59 GMT

Hi,

Can you gather logs from Power Profiler with verbose logging enabled?

Make sure PPK2 is connected to your computer
In Power Profiler go to the 'About' tab and enable verbose logging
Select 'Restart with verbose logging'
After the app restarts click on 'open log file' at the bottom of the terminal.
Either save the log file somewhere and upload it here with Insert -> Image/video/file, or copy the contents of the log file and go to Insert -> Code then paste the log there.

Best regards,

Marte

RE: JLINKARM_DLL_COULD_NOT_BE_OPENED

cactix — Thu, 21 Apr 2022 19:16:42 GMT

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

RE: JLINKARM_DLL_COULD_NOT_BE_OPENED

Marte Myrvold — Thu, 21 Apr 2022 10:54:44 GMT

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