Cannot program the board

[Plakkies]

I am using vscode on linux, I started by programming the blinky sample onto the devkit, without issue. I then moved on to the gnss sample in a separate project, this worked too without issue. Trying to work out how to do debug I found that I could not program the board anymore. A restart and reboot later and the problem persists. I have also tried the first project which was working correctly. The error below is from this project and im juts trying to do a reset. The same error is produced when I try flash it as well. I have not modified the board at all.

 Using the nRF Connect SDK v3.1.0 at /home/plakkies/workspace

No issues were detected with the toolchain.

[12:43:02] flash -d /home/plakkies/workspace/blinky_pwm/build --domain blinky_pwm --dev-id 1051282951

[12:43:19] Failure (code 1).

[12:44:19] nrfutil-device reset --serial-number 001051282951 --json

[12:44:33] Error: One or more reset tasks failed:

* 1051282951: Timed out waiting for response from worker. (Generic)

[Plakkies]

I get the same error when trying the celular monitor as well. 

[Øyvind]

Hello, 

How did you install the environment in linux i.e. VS Code extension, SDK and Toolchain?

Plakkies said:

I get the same error when trying the celular monitor as well. 

What errors do you see? Can you please provide the log file, and more on the steps you took so that I can try to reproduce?

In command line, what output do you get when running nrfutil device list? Have you removed any headers from the DK e.g. nrf current measurement header?

Kind regards,
Øyvind

[Plakkies]

OK, It was not the firmware, I downgraded SEGGER J-Link to v8.6 and here is the log file again after I tried programming the asset tracker again:
2025-09-29T06:51:45.293Z INFO Initialising the bundled nrfutil device
2025-09-29T06:51:45.293Z DEBUG Started watching devices
2025-09-29T06:52:40.713Z INFO Successfully installed nrfutil core version: 8.0.0
2025-09-29T06:53:31.990Z INFO Successfully installed nrfutil device version: 2.13.2
2025-09-29T06:53:32.007Z INFO Using the bundled core version for nrfutil device: 8.0.0
2025-09-29T06:53:32.034Z DEBUG Selected device: nRF9151 DK
2025-09-29T06:53:32.053Z DEBUG Changed step: Info
2025-09-29T06:53:32.104Z INFO Using nrfutil device version: 2.13.2
2025-09-29T06:53:32.104Z INFO Using nrf-device-lib version: 0.19.0
2025-09-29T06:53:32.104Z INFO Using nrf-probe version: 0.45.0
2025-09-29T06:53:32.104Z INFO Using SEGGER J-Link version: JLink_V8.72
2025-09-29T06:53:32.105Z INFO Your version of SEGGER J-Link (8.72) is newer than the one this app was tested with (8.60). The tested version is not required, and your J-Link version will most likely work fine. If you get issues related to J-Link with your devices, use the tested version.
2025-09-29T06:56:01.849Z DEBUG Changed step: Rename
2025-09-29T06:56:24.823Z DEBUG Changed step: Program
2025-09-29T06:56:44.313Z ERROR Failed to initialize worker: Timed out waiting for response from worker.
2025-09-29T06:56:48.490Z ERROR Trace channel disconnected unexpectedly.
2025-09-29T06:56:48.493Z ERROR Worker terminated by signal 9.
2025-09-29T06:56:48.493Z ERROR Error output of terminated worker: 
2025-09-29T07:11:17.524Z ERROR Failed to initialize worker: Timed out waiting for response from worker.
2025-09-29T07:11:21.712Z ERROR Trace channel disconnected unexpectedly.
2025-09-29T07:11:21.714Z ERROR Worker terminated by signal 9.
2025-09-29T07:11:21.715Z ERROR Error output of terminated worker: 

It seems the only real error I'm getting is the timeout.

[Øyvind]

Hello, I've tried installing SEGGER J-Link (8.72) and reproducing your issue, but with no success. 

Plakkies said:

, It was not the firmware, I downgraded SEGGER J-Link to v8.6 and here is the log file again after I tried programming the asset tracker again:

From what application are you collecting your logs? We will need more verbose logging in order to pinpoint the issue.

What output do you get if you run both the following commands from command line: 

nrfutil device --version 

and 

nrfutil device reset --json-pretty 

Kind regards,
Øyvind

[Øyvind]

Are you using our VS Code extension? If so, can you please provide the output from nRF Connect:Generate Support information?

[Plakkies]

Below you will find the output of those two. After seeing this I tried again to program and use the cellular monitor and a few other things. All of it works now. This makes no sense as I have not made changes for two days. Im just very glad it works now and c an carry on with the Dev Academy course. Thank you very much for all the help.

plakkies@plakkies-XPS:~$ nrfutil device --version
nrfutil-device 2.14.1 (ca1b1f9 2025-09-26)
commit-hash: ca1b1f900e3f0b8d6d09d7ff4518226f6f61dc9d
commit-date: 2025-09-26
host: x86_64-unknown-linux-gnu
build-timestamp: 2025-09-26T14:17:34.962554530Z
classification: nrf-external

Detected SEGGER J-Link version: JLink_V8.60

The device command version you are currently using was tested with a different J-Link version (JLink_V8.66) than the one you have installed (JLink_V8.60). The tested version is not required, and your J-Link version will most likely work fine. If you get issues related to J-Link with your devices, use the tested version.
plakkies@plakkies-XPS:~$ nrfutil device reset --json-pretty 
{
  "type": "task_begin",
  "data": {
    "task": {
      "id": "eb99f1138ee841559dc06053aca62e04",
      "description": "Reset 1051282951",
      "name": "reset",
      "data": {
        "serialNumber": "001051282951"
      }
    }
  }
}
{
  "type": "task_progress",
  "data": {
    "task": {
      "id": "eb99f1138ee841559dc06053aca62e04",
      "description": "Reset 1051282951",
      "name": "reset",
      "data": {
        "serialNumber": "001051282951"
      }
    },
    "progress": {
      "progressPercentage": 0,
      "name": "reset",
      "description": "Connecting to probe",
      "step": 1,
      "amountOfSteps": 2,
      "state": "progress",
      "duration": 0,
      "error_code": null,
      "message": null,
      "result": "success"
    }
  }
}
{
  "type": "task_progress",
  "data": {
    "task": {
      "id": "eb99f1138ee841559dc06053aca62e04",
      "description": "Reset 1051282951",
      "name": "reset",
      "data": {
        "serialNumber": "001051282951"
      }
    },
    "progress": {
      "progressPercentage": 100,
      "name": "reset",
      "description": "Connecting to probe",
      "step": 1,
      "amountOfSteps": 2,
      "state": "progress",
      "duration": 66,
      "error_code": null,
      "message": null,
      "result": "success"
    }
  }
}
{
  "type": "task_progress",
  "data": {
    "task": {
      "id": "eb99f1138ee841559dc06053aca62e04",
      "description": "Reset 1051282951",
      "name": "reset",
      "data": {
        "serialNumber": "001051282951"
      }
    },
    "progress": {
      "progressPercentage": 0,
      "name": "reset",
      "description": "Reset",
      "step": 2,
      "amountOfSteps": 2,
      "state": "progress",
      "duration": 66,
      "error_code": null,
      "message": null,
      "result": "success"
    }
  }
}
{
  "type": "task_progress",
  "data": {
    "task": {
      "id": "eb99f1138ee841559dc06053aca62e04",
      "description": "Reset 1051282951",
      "name": "reset",
      "data": {
        "serialNumber": "001051282951"
      }
    },
    "progress": {
      "progressPercentage": 100,
      "name": "reset",
      "description": "Reset",
      "step": 2,
      "amountOfSteps": 2,
      "state": "progress",
      "duration": 212,
      "error_code": null,
      "message": null,
      "result": "success"
    }
  }
}
{
  "type": "task_end",
  "data": {
    "task": {
      "id": "eb99f1138ee841559dc06053aca62e04",
      "description": "Reset 1051282951",
      "name": "reset",
      "data": {
        "serialNumber": "001051282951"
      }
    },
    "message": "Reset was applied to 1051282951",
    "result": "success",
    "error": null
  }
}

[Øyvind]

Very strange behavior, but glad to hear that you are able to continue! Let us know if you start seeing strange behavior again

[Plakkies]

Thank you again