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

[vectr]

Hello, After doing several things on my Ubuntu 24 host (I don't what might cause problem):
-> Updating java OpenJDK to 17
-> running apt update & upgrade
-> 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)

I can't connect to nrf's 840 v3:

$ nrfjprog -v
nrfjprog version: 10.24.2 external
JLinkARM.dll version: 7.94e
$ nrfjprog -i
1050253557
1050205707
682357877
682924054
$ nrfjprog -s 682357877 --recover
Recovering device. This operation might take 30s.
Erasing user code and UICR flash areas.
$ nrfjprog -s 1050253557 --recover
[error] [ Client] - Encountered error -105: Command connect_to_emu_with_snr executed for 787 milliseconds with result -105
ERROR: Unable to connect to a debugger.
[error] [ Worker] - JLinkARM.dll Open returned error 'Cannot connect to J-Link.'
ERROR: The JLinkARM DLL timed out while communicating to the J-Link probe.
ERROR: If the error condition persists, run the same command again with
ERROR: argument -- log, contact Nordic Semiconductor and provide the generated
ERROR: log.log file to them.
NOTE: For additional output, try running again with logging enabled (--log).
NOTE: Any generated log error messages will be displayed.

Everything worked earlier. Can you help me?

[Håkon Alseth]

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

[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). 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. 

[Håkon Alseth]

Hi,

 

vectr said:

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 boards, ie. *557 and *707 works on your personal computer. Meaning, the boards themselves are working.

 

-> 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)

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

[vectr]

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

[Håkon Alseth]

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