• State Verified Answer
  • Replies 19 replies
  • Subscribers 88 subscribers
  • Views 1459 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 351386
Options

Visual Studio Code: Unable to find worker executable / Unable to flash target

radio200000

Hi all

Coming back to an nrf52840 project after some weeks, VScode nRF extension do not work anymore.

Trying to recover a board (nRF52840DK) gives error:

08:52:50] nrfutil-device recover --serial-number 001050261677 --json
[08:52:51] Error: One or more recover tasks failed:
* 1050261677: Unable to find worker executable: Custom { kind: NotFound, error: "Failed to find file plugin-probe-worker. Looked for file in <none>, <none>, /home/vsts/.cargo/registry/src/eu.files.nordicsemi.com-aeee3781a8ecf169/target/release/plugin-probe-worker and /home/developer/.vscode/extensions/nordic-semiconductor.nrf-connect-2025.9.754-linux-x64/platform/nrfutil/bin/plugin-probe-worker" } (Generic)

Trying to flash a binary to the target gives error:

Executing task: nRF Connect: Flash: <project-directory><project-name> (active)

Flashing <project-name> to nRF52840 DK
west flash -d /home/developer/work/<project-directory>/build --domain <project-name> --dev-id 1050261677

-- west flash: rebuilding
[0/10] Performing build step for '<project-name>'
ninja: no work to do.
[1/10] Performing build step for 'mcuboot'
ninja: no work to do.
[4/10] cd /home/developer/work/<project-directory>/build/_sysbuild && /home/developer/ncs/tool[7/9] cd /home/developer/work/<project-directory>/build/_sysbuild && /home/developer/ncs/toolc[8/9] cd /home/developer/work/<project-directory>/build/_sysbuild && /home/developer/ncs/toolchains/7cbc0036f4/usr/local/bin/cmake -E true
-- west flash: using runner nrfutil
-- runners.nrfutil: reset after flashing requested
FATAL ERROR: required program nrfutil not found; install it or add its location to PATH

Validating the toolchain gives no errors:

[09:09:41] =========== Toolchain validation report for nRF Connect SDK Toolchain v3.0.2 ===========
Package Using the nRF Connect SDK v3.0.2 at /home/developer/ncs/v3.0.2
No issues were detected with the toolchain.

Versions:

Visual Studio Code: 1.104.0

nRF Connect for VS Code Extension Pack: 2025.4.4

nRF Connect for VS Code: 2025.9.754

nRF DeviceTree: 2025.8.140

nRF Kconfig: 2025.9.123

nRF Terminal: 2025.8.103

Any idea what's wrong here?

Thanks!

--

Kind regards

  • 0 in reply to Vidar Berg

    Ok, did not do that before. Now 

    ./nrfutil device --version

    Gives similar output as in your example.

    But flashing via VSCode extension gives a new error:

    Executing task: nRF Connect: Flash: <project-name>/<project-name> (active)

    Flashing <project-name> to nRF52840 DK
    west flash -d /home/developer/work/<project-directory>/build --domain <project-name> --dev-id 1050261677

    -- west flash: rebuilding
    [0/10] Performing build step for '<project-name>'
    ninja: no work to do.
    [1/10] Performing build step for 'mcuboot'
    ninja: no work to do.
    [8/9] cd /home/developer/work/<project-directory>/build/_sysbuild && /home/developer/ncs/toolchains/7cbc0036f4/usr/local/bin/cmake -E true
    -- west flash: using runner nrfutil
    -- runners.nrfutil: reset after flashing requested
    -- runners.nrfutil: Flashing file: /home/developer/work/<project-directory>/build/merged.hex
    Error: One or more batch tasks failed:
    * 1050261677: Timed out waiting for response from worker. (Generic)

    FATAL ERROR: command exited with status 1: nrfutil --json device --x-ext-mem-config-file /home/developer/ncs/v3.0.2/zephyr/boards/nordic/nrf52840dk/support/nrf52840dk_qspi_nrfutil_config.json x-execute-batch --batch-path /home/developer/work/<project-directory>/build/generated_nrfutil_batch.json --serial-number 1050261677

    * The terminal process terminated with exit code: 1.
    * Terminal will be reused by tasks, press any key to close it.

  • 0 in reply to radio200000

    Team just pushed a new release (2025.9.789 -> 2025.9.798). I confirmed that this fixed the issue on my end as well.

    radio200000 said:
    Gives similar output as in your example.

    Are you able to successfully run "nrfutil device recover" from the terminal?

  • 0 in reply to Vidar Berg

    Unfortunately, that does not work either:

    ~/bin$ ./nrfutil device recover
    X Failed to recover 1050261677, Timed out waiting for response from worker. Error: One or more recover tasks failed:
    * 1050261677: Timed out waiting for response from worker. (Generic)

  • 0 in reply to radio200000

    I think we've been unlucky to have hit several seemingly unrelated issues. The latter appears more like a connectivity issue with your DK. Which version of Jlink is listed when you run nrfutil device --version?

  • 0 in reply to Vidar Berg

    ~/bin$ nrfutil device --version
    nrfutil-device 2.14.0 (fc03a3f 2025-09-16)
    commit-hash: fc03a3f4e33bdcc94452363f8b42a464de48166a
    commit-date: 2025-09-16
    host: x86_64-unknown-linux-gnu
    build-timestamp: 2025-09-16T10:17:08.723659415Z
    classification: nrf-external

    Detected SEGGER J-Link version: JLink_V8.18

    The device command version you are currently using was tested with a different J-Link version (JLink_V8.60) than the one you have installed (JLink_V8.18). 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.

Related
Terms of service