JLinkARM.dll Open returned error 'Cannot connect to J-Link.' while connecting to nRF52840 DK v3.0.0

RE: JLinkARM.dll Open returned error 'Cannot connect to J-Link.' while connecting to nRF52840 DK v3.0.0

vectr — Wed, 18 Dec 2024 08:58:33 GMT

There something I did not mention earier, I updated java by running ansible script. It copied 99-jlink.rules from older JLink version.
I must have 99-link.rules updated manually by someone and I overwrite it when I was trying to perform update via ansible.

RE: JLinkARM.dll Open returned error 'Cannot connect to J-Link.' while connecting to nRF52840 DK v3.0.0

Håkon Alseth — Wed, 18 Dec 2024 08:28:46 GMT

Hi,

Glad to hear that you found the solution. Looks like that file was empty?

[quote user="vectr"]Thank you for your help and your time. Just out of curiosity: which line fixed the nrfjprog?[/quote]

If you run "lsusb" - you should get something like this:

...
Bus 001 Device 019: ID 1366:1050 SEGGER J-Link
...

And you should find the specific PID in the udev rules, with the corresponding mode being set.

Kind regards,

Håkon

RE: JLinkARM.dll Open returned error 'Cannot connect to J-Link.' while connecting to nRF52840 DK v3.0.0

vectr — Tue, 17 Dec 2024 15:30:25 GMT

It did not helped, but I compare all files in /etc/udev/rules.d between my PC and other with problem with -105.
I noticed difference between 99-jlink.rules files. I copied file and it solved my issue.
Here are result of diff command:

30a31,34
> # sudo udevadm info --attribute-walk /dev/bus/usb/<Bus>/<Device> (extract <Bus> and <Device> from "lsusb")
> # Reload udev rules after rules file change:
> # sudo udevadm control --reload-rules
> # sudo udevadm trigger
49a54,64
> # Make sure that J-Links are not captured by modem manager service
> # as this service would try detect J-Link as a modem and send AT commands via the VCOM component which might not be liked by the target...
> #
> ATTR{idProduct}"0101", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"0102", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"0103", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"0104", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"0105", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"0107", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"0108", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> #
106a122,154
> # 0x103x: J_LINK_SEGGER_DRV + J_LINK_WINUSB_DRV does not make any sense, therefore skipped
> # 0x1050: J_LINK_SEGGER_DRV + 2x CDC
> # 0x1051: J_LINK_SEGGER_DRV + 2x CDC + MSD
> # 0x1052: J_LINK_SEGGER_DRV + 2x CDC + RNDIS
> # 0x1053: J_LINK_SEGGER_DRV + 2x CDC + RNDIS + MSD
> # 0x1054: J_LINK_SEGGER_DRV + 3x CDC
> # 0x1055: J_LINK_SEGGER_DRV + 3x CDC + MSD
> # 0x1056: J_LINK_SEGGER_DRV + 3x CDC + RNDIS
> # 0x1057: J_LINK_SEGGER_DRV + 3x CDC + RNDIS + MSD
> # 0x1058: J_LINK_SEGGER_DRV + HID + 2x CDC
> # 0x1059: J_LINK_SEGGER_DRV + HID + 2x CDC + MSD
> # 0x105a: J_LINK_SEGGER_DRV + HID + 2x CDC + RNDIS
> # 0x105b: J_LINK_SEGGER_DRV + HID + 2x CDC + RNDIS + MSD
> # 0x105c: J_LINK_SEGGER_DRV + HID + 3x CDC
> # 0x105d: J_LINK_SEGGER_DRV + HID + 3x CDC + MSD
> # 0x105e: J_LINK_SEGGER_DRV + HID + 3x CDC + RNDIS
> # 0x105f: J_LINK_SEGGER_DRV + HID + 3x CDC + RNDIS + MSD
> # 0x1060: J_LINK_WINUSB_DRV + 2x CDC
> # 0x1061: J_LINK_WINUSB_DRV + 2x CDC + MSD
> # 0x1062: J_LINK_WINUSB_DRV + 2x CDC + RNDIS
> # 0x1063: J_LINK_WINUSB_DRV + 2x CDC + RNDIS + MSD
> # 0x1064: J_LINK_WINUSB_DRV + 3x CDC
> # 0x1065: J_LINK_WINUSB_DRV + 3x CDC + MSD
> # 0x1066: J_LINK_WINUSB_DRV + 3x CDC + RNDIS
> # 0x1067: J_LINK_WINUSB_DRV + 3x CDC + RNDIS + MSD
> # 0x1068: J_LINK_WINUSB_DRV + HID + 2x CDC
> # 0x1069: J_LINK_WINUSB_DRV + HID + 2x CDC + MSD
> # 0x106a: J_LINK_WINUSB_DRV + HID + 2x CDC + RNDIS
> # 0x106b: J_LINK_WINUSB_DRV + HID + 2x CDC + RNDIS + MSD
> # 0x106c: J_LINK_WINUSB_DRV + HID + 3x CDC
> # 0x106d: J_LINK_WINUSB_DRV + HID + 3x CDC + MSD
> # 0x106e: J_LINK_WINUSB_DRV + HID + 3x CDC + RNDIS
> # 0x106f: J_LINK_WINUSB_DRV + HID + 3x CDC + RNDIS + MSD
154a203,363
> ATTR{idProduct}"1050", ATTR{idVendor}"1366", MODE="666"
> ATTR{idProduct}"1051", ATTR{idVendor}"1366", MODE="666"
> ATTR{idProduct}"1052", ATTR{idVendor}"1366", MODE="666"
> ATTR{idProduct}"1053", ATTR{idVendor}"1366", MODE="666"
> ATTR{idProduct}"1054", ATTR{idVendor}"1366", MODE="666"
> ATTR{idProduct}"1055", ATTR{idVendor}"1366", MODE="666"
> ATTR{idProduct}"1056", ATTR{idVendor}"1366", MODE="666"
> ATTR{idProduct}"1057", ATTR{idVendor}"1366", MODE="666"
> ATTR{idProduct}"1058", ATTR{idVendor}"1366", MODE="666"
> ATTR{idProduct}"1059", ATTR{idVendor}"1366", MODE="666"
> ATTR{idProduct}"105a", ATTR{idVendor}"1366", MODE="666"
> ATTR{idProduct}"105b", ATTR{idVendor}"1366", MODE="666"
> ATTR{idProduct}"105c", ATTR{idVendor}"1366", MODE="666"
> ATTR{idProduct}"105d", ATTR{idVendor}"1366", MODE="666"
> ATTR{idProduct}"105e", ATTR{idVendor}"1366", MODE="666"
> ATTR{idProduct}"105f", ATTR{idVendor}"1366", MODE="666"
> ATTR{idProduct}"1060", ATTR{idVendor}"1366", MODE="666"
> ATTR{idProduct}"1061", ATTR{idVendor}"1366", MODE="666"
> ATTR{idProduct}"1062", ATTR{idVendor}"1366", MODE="666"
> ATTR{idProduct}"1063", ATTR{idVendor}"1366", MODE="666"
> ATTR{idProduct}"1064", ATTR{idVendor}"1366", MODE="666"
> ATTR{idProduct}"1065", ATTR{idVendor}"1366", MODE="666"
> ATTR{idProduct}"1066", ATTR{idVendor}"1366", MODE="666"
> ATTR{idProduct}"1067", ATTR{idVendor}"1366", MODE="666"
> ATTR{idProduct}"1068", ATTR{idVendor}"1366", MODE="666"
> ATTR{idProduct}"1069", ATTR{idVendor}"1366", MODE="666"
> ATTR{idProduct}"106a", ATTR{idVendor}"1366", MODE="666"
> ATTR{idProduct}"106b", ATTR{idVendor}"1366", MODE="666"
> ATTR{idProduct}"106c", ATTR{idVendor}"1366", MODE="666"
> ATTR{idProduct}"106d", ATTR{idVendor}"1366", MODE="666"
> ATTR{idProduct}"106e", ATTR{idVendor}"1366", MODE="666"
> ATTR{idProduct}"106f", ATTR{idVendor}"1366", MODE="666"
> #
> # Handle known CMSIS-DAP probes (taken from mbed website and OpenOCD):
> # VID 0x1366 (SEGGER)
> # PID 0x1008-100f, 0x1018-101f, 0x1028-102f, 0x1058-105f, 0x1068-106f (SEGGER J-Link)
> # We cover all of them via idProduct=10* and idVendor=1366
> #
> # VID 0xC251 (Keil)
> # PID 0xF001: (LPC-Link-II CMSIS_DAP)
> # PID 0xF002: (OpenSDA CMSIS_DAP Freedom Board)
> # PID 0x2722: (Keil ULINK2 CMSIS-DAP)
> # VID 0x0D28 (mbed)
> # PID 0x0204: MBED CMSIS-DAP
> #
> KERNEL"hidraw*", ATTRS{idProduct}"10*", ATTRS{idVendor}"1366", MODE="666"
> KERNEL"hidraw*", ATTRS{idProduct}"f001", ATTRS{idVendor}"c251", MODE="666"
> KERNEL"hidraw*", ATTRS{idProduct}"f002", ATTRS{idVendor}"c251", MODE="666"
> KERNEL"hidraw*", ATTRS{idProduct}"2722", ATTRS{idVendor}"c251", MODE="666"
> KERNEL"hidraw*", ATTRS{idProduct}"0204", ATTRS{idVendor}"c251", MODE="666"
> KERNEL"hidraw*", ATTRS{idProduct}"f001", ATTRS{idVendor}"0d28", MODE="666"
> KERNEL"hidraw*", ATTRS{idProduct}"f002", ATTRS{idVendor}"0d28", MODE="666"
> KERNEL"hidraw*", ATTRS{idProduct}"2722", ATTRS{idVendor}"0d28", MODE="666"
> KERNEL"hidraw*", ATTRS{idProduct}"0204", ATTRS{idVendor}"0d28", MODE="666"
> #
> # Make sure that J-Links are not captured by modem manager service
> # as this service would try detect J-Link as a modem and send AT commands via the VCOM component which might not be liked by the target...
> #
> ATTR{idProduct}"1001", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"1002", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"1003", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"1004", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"1005", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"1006", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"1007", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"1008", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"1009", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"100a", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"100b", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"100c", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"100d", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"100e", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"100f", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"1010", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"1011", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"1012", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"1013", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"1014", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"1015", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"1016", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"1017", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"1018", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"1019", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"101a", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"101b", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"101c", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"101d", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"101e", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"101f", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"1020", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"1021", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"1022", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"1023", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"1024", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"1025", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"1026", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"1027", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"1028", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"1029", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"102a", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"102b", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"102c", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"102d", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"102e", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"102f", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"1050", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"1051", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"1052", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"1053", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"1054", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"1055", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"1056", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"1057", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"1058", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"1059", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"105a", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"105b", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"105c", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"105d", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"105e", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"105f", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"1060", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"1061", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"1062", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"1063", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"1064", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"1065", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"1066", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"1067", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"1068", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"1069", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"106a", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"106b", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"106c", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"106d", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"106e", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"106f", ATTR{idVendor}"1366", ENV{ID_MM_DEVICE_IGNORE}="1"
> #
> # Handle known CMSIS-DAP probes (taken from mbed website and OpenOCD):
> # VID 0xC251 (Keil)
> # PID 0xF001: (LPC-Link-II CMSIS_DAP)
> # PID 0xF002: (OpenSDA CMSIS_DAP Freedom Board)
> # PID 0x2722: (Keil ULINK2 CMSIS-DAP)
> # VID 0x0D28 (mbed)
> # PID 0x0204: MBED CMSIS-DAP
> #
> ATTR{idProduct}"f001", ATTR{idVendor}"c251", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"f002", ATTR{idVendor}"c251", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"2722", ATTR{idVendor}"c251", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"0204", ATTR{idVendor}"c251", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"f001", ATTR{idVendor}"0d28", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"f002", ATTR{idVendor}"0d28", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"2722", ATTR{idVendor}"0d28", ENV{ID_MM_DEVICE_IGNORE}="1"
> ATTR{idProduct}"0204", ATTR{idVendor}"0d28", ENV{ID_MM_DEVICE_IGNORE}="1"
> #
> # Make sure that VCOM ports of J-Links can be opened with user rights
> # We simply say that all devices from SEGGER which are in the "tty" domain are enumerated with normal user  R/W
> #
> SUBSYSTEM"tty", ATTRS{idVendor}"1366", MODE="0666", GROUP="dialout"
> SUBSYSTEM"tty", ATTRS{idVendor}"c251", MODE="0666", GROUP="dialout"
> SUBSYSTEM"tty", ATTRS{idVendor}"0d28", MODE="0666", GROUP="dialout"

Thank you for your help and your time. Just out of curiosity: which line fixed the nrfjprog?

RE: JLinkARM.dll Open returned error 'Cannot connect to J-Link.' while connecting to nRF52840 DK v3.0.0

Håkon Alseth — Tue, 17 Dec 2024 14:23:24 GMT

Hi,

[quote user="vectr"]I might not have installed nrf-udev, I download it from github and behavior did not changed.[/quote]

You need to reboot to invoke new udev rules.

I'm running 24.04.1 myself, and just did a dist-upgrade and matched your nrfjprog/jlink versions:

nrfjprog --ids
1050272212

nrfjprog -v
nrfjprog version: 10.24.2 external
JLinkARM.dll version: 7.94e

Have not seen any issues like this on my side.

Have you tried different versions of jlink? I know that v7.96e is the latest that we bundle with nrf-command-line-tools, but you can update to a newer one for testing purposes: https://www.segger.com/downloads/jlink/

Kind regards,

Håkon

RE: JLinkARM.dll Open returned error 'Cannot connect to J-Link.' while connecting to nRF52840 DK v3.0.0

vectr — Tue, 17 Dec 2024 13:39:05 GMT

I might not have installed nrf-udev, I download it from github and behavior did not changed.

RE: JLinkARM.dll Open returned error 'Cannot connect to J-Link.' while connecting to nRF52840 DK v3.0.0

Håkon Alseth — Tue, 17 Dec 2024 10:19:15 GMT

Hi,

You haven't by any chance updated udev and removed the nrf-rules?

https://github.com/NordicSemiconductor/nrf-udev/tree/main

Kind regards,

Håkon

RE: JLinkARM.dll Open returned error 'Cannot connect to J-Link.' while connecting to nRF52840 DK v3.0.0

vectr — Mon, 16 Dec 2024 14:45:35 GMT

This script may not exit properly, I'm not sure. When I noticed issue with DK'ts I restored these changes.
This is how my script looks now:

from pynrfjprog import Hex, LowLevel
from pynrfjprog.APIError import APIError, NrfjprogdllErr

...

class JLinkManager:

   def __init__(

       self,
       product_chip_name: str,
       serial_number: int,
       name: str = None,
    ):

        self._device_family = DeviceFamily[self.device.name[:5]]
        self._api = LowLevel.API(self._device_family, log=log)

   def __enter__(
       self,
   ):
       self.open()
       return self

   def open(
       self,
   ):
   """Open connection to board."""
      try:
          self._api.open()
          self._api.connect_to_emu_with_snr(self.serial_number)
          return self._api.is_connected_to_emu()
      except APIError as error:
          raise CannotOpenError(f"[{self.name}] nrf APIError code: {error.err_code}.") from error

I don;t see zombie processes on computer with issue:
$ ps aux | grep -i jlink
ci 24981 0.0 0.0 9144 2304 pts/0 S+ 15:33 0:00 grep --color=auto -i jlink

RE: JLinkARM.dll Open returned error 'Cannot connect to J-Link.' while connecting to nRF52840 DK v3.0.0

Håkon Alseth — Mon, 16 Dec 2024 14:24:04 GMT

Hi,

[quote user="vectr"]On my PC both 1050253557 and 1050205707 don't show -105 error on my personal PC (I tested it by running command: nrfjprog -r -s 1050205707)[/quote]

Both boards, ie. *557 and *707 works on your personal computer. Meaning, the boards themselves are working.

[quote user=""]-> modifying my script for restarting/flashing/ nRF52840 device: I was trying to face -105 JLINKARM_DLL_TIME_OUT_ERRORI added
NRFJPROG_connect_to_device_inst() and NRFJPROG_halt_inst() as was presented here: https://docs.nordicsemi.com/bundle/ug_nrf_cltools/page/UG/cltools/nrf_nrfjprogdll_calling_sequence.html)[/quote]

Is this script not exited properly at one time? Try to run this:

ps aux | grep -i jlink

And check if there's any zombie processes.

Kind regards,

Håkon

RE: JLinkARM.dll Open returned error 'Cannot connect to J-Link.' while connecting to nRF52840 DK v3.0.0

vectr — Mon, 16 Dec 2024 14:15:35 GMT

On my PC both 1050253557 and 1050205707 don't show -105 error on my personal PC (I tested it by running command: nrfjprog -r -s 1050205707). Both have ubuntu 24, both have same nrfjprog and JLink version.
Cable replacement did not helped. I replace them with nRF52840 DK v2.1.0 and them works on same usb cable.
"current consumption" jumper - do you mean "nRF current measurement" connector (P22)? I don't have this jumper shoted.

RE: JLinkARM.dll Open returned error 'Cannot connect to J-Link.' while connecting to nRF52840 DK v3.0.0

Håkon Alseth — Mon, 16 Dec 2024 13:50:58 GMT

Hi,

Does the same kit behave similar on other PCs?

Have you tried switching out the USB cable for instance?

Checked that the "current consumption" jumper is present?

Kind regards,

Håkon