Failed to flash with nRF Connect

RE: Failed to flash with nRF Connect

a.da — Mon, 17 Mar 2025 00:01:29 GMT

Hi Carles ,

I have confirmed that the issue has been resolved with the revised file.

Thank you for your support.

Kind regards,

a.da

RE: Failed to flash with nRF Connect

a.da — Mon, 17 Mar 2025 00:01:11 GMT

Yes, nRF5340DK.

RE: Failed to flash with nRF Connect

Carles — Sat, 15 Mar 2025 17:29:06 GMT

That is almost definitely a false positive, provided those files came from the toolchain installed via VS Code or nrfutil.

RE: Failed to flash with nRF Connect

Carles — Fri, 14 Mar 2025 18:09:41 GMT

Hey a.da ,

I finally figured out what the issue is. Turns out that VS Code filters out the `ProgramFiles(x86)` env var, so I instead rewrote the logic to use the registry instead of env vars, and to only execute when you are actually using the jlink runner. This fix will be in NCS 3.0.0.

In the meantime, this is the PR:

github.com/.../87136

RE: Failed to flash with nRF Connect

Carles — Fri, 14 Mar 2025 09:02:58 GMT

Thanks for the info. I assume you are building for the nRF5340 DK, correct?

RE: Failed to flash with nRF Connect

a.da — Thu, 13 Mar 2025 23:51:18 GMT

Carles

Hi,

I just pressed the Flash button in VS Code, but is there anything suspicious about the operation?

The contents of the "board.cmake" file are as follows. It's the same as the file included in sdk-zephyr.
Since I only flashed the sample program to the DK, there are no custom files of my own.

# SPDX-License-Identifier: Apache-2.0

if(CONFIG_BOARD_NRF5340DK_NRF5340_CPUAPP_NS)
  set(TFM_PUBLIC_KEY_FORMAT "full")
endif()

if(CONFIG_BOARD_NRF5340DK_NRF5340_CPUAPP OR CONFIG_BOARD_NRF5340DK_NRF5340_CPUAPP_NS)
board_runner_args(jlink "--device=nrf5340_xxaa_app" "--speed=4000")
endif()

if(CONFIG_TFM_FLASH_MERGED_BINARY)
  set_property(TARGET runners_yaml_props_target PROPERTY hex_file tfm_merged.hex)
endif()

if(CONFIG_BOARD_NRF5340DK_NRF5340_CPUNET)
board_runner_args(jlink "--device=nrf5340_xxaa_net" "--speed=4000")
endif()

include(${ZEPHYR_BASE}/boards/common/nrfjprog.board.cmake)
include(${ZEPHYR_BASE}/boards/common/nrfutil.board.cmake)
include(${ZEPHYR_BASE}/boards/common/jlink.board.cmake)

Kind regards,

a.da

RE: Failed to flash with nRF Connect

Carles — Thu, 13 Mar 2025 15:44:22 GMT

a.da Why are you flashing with the jlink backend though? Could you show me the contents of your `board.cmake` file please?

or were you trying to debug instead?

RE: Failed to flash with nRF Connect

a.da — Wed, 12 Mar 2025 23:50:38 GMT

Hi Einar, thanks for your reply.

Thanks to the workaround, Flash was successful. I look forward to the follow-up.

[quote userid="7377" url="~/f/nordic-q-a/119738/failed-to-flash-with-nrf-connect/526869"]Regarding the false positivies, which security software is reporting it?[/quote]

It is a McAfee.
About Main Software:
Version: 1.26.217
Release: 16.0 R126
About Antivirus Component:
Build: 1.126.268.0
Content Version: 2077.0

It was detected by real-time scanning during the build process.
By adding it to the "Exclude Files" list, the build was able to complete successfully.

Kind regards,

a.da

Addition:

It seems that the false detection is due to an update in the security software.
Not only the SDK Toolchain v3.0.0-preview1, but also the same file in v2.9.0 is now being flagged.

RE: Failed to flash with nRF Connect

Einar Thorsrud — Wed, 12 Mar 2025 09:27:42 GMT

Hi,

Thank you for reporting the issue. We are looking into it. A suggested workaround for now is to replace line 32 in zephyr/scripts/west_commands/runners/jlink.py so that it looks like this:

    for root in [os.environ.get("ProgramFiles", ""), os.environ.get("ProgramFiles(x86)", ""), str(Path.home())]:

Regarding the false positivies, which security software is reporting it?