nrfconnect vscode extension problems with "Add Build Configuration" wizard and "Actions" view

RE: nrfconnect vscode extension problems with "Add Build Configuration" wizard and "Actions" view

dejans — Tue, 26 Nov 2024 13:52:54 GMT

Hi,

[quote user="Betta Sharma"]I have a feeling that my NCS installation may be incomplete or inadequate.[/quote]

How did you install NCS on your computer?

[quote user="Betta Sharma"]

I am facing same issues. Add Build Configuration is greyed out and I can't seem to activate it. My code builds correctly in CLI with:

west build -p always -b nrf52840dk/nrf52840 samples\fund_less3_exer1

However, I can't run this from the terminal mode of VS code extension as west command is not recognized.

[/quote]

You could try to install appropriate NCS version from the Toolchain Manager, open VS Code from the Toolchain Manager and then try to use Add Build Command and Terminal. Does this make any difference?

Best regards,
Dejan

RE: nrfconnect vscode extension problems with "Add Build Configuration" wizard and "Actions" view

Betta Sharma — Mon, 25 Nov 2024 18:07:33 GMT

Microsoft Windows [Version 10.0.19045.5011]

Version: 1.95.3 (user setup)
Commit: f1a4fb101478ce6ec82fe9627c43efbf9e98c813
Date: 2024-11-13T14:50:04.152Z
Electron: 32.2.1
ElectronBuildId: 10427718
Chromium: 128.0.6613.186
Node.js: 20.18.0
V8: 12.8.374.38-electron.0
OS: Windows_NT x64 10.0.19045

I have this file:

C:\ncs\toolchains\ce3b5ff664\cmake\NcsToolchainConfig.cmake that contains:

# SPDX-License-Identifier: Apache-2.0

# This file provides Zephyr sdk config version package functionality.
#

# Those are Zephyr variables used.
get_filename_component(NCS_TOOLCHAIN_PATH ${CMAKE_CURRENT_LIST_DIR}/../ ABSOLUTE)
if(${CMAKE_HOST_SYSTEM_NAME} STREQUAL Windows)
set(NCS_TOOLCHAIN_EXECUTABLE_SUFFIX ".exe")
set(NCS_TOOLCHAIN_BIN_PATH ${NCS_TOOLCHAIN_PATH}/opt/bin)

# This will be deprecated, relying on it may fail for NCS 2.0+
set(NCS_GNUARMEMB_TOOLCHAIN_PATH ${NCS_TOOLCHAIN_PATH}/opt)

set(NCS_TOOLCHAIN_ENV_PATH "${NCS_TOOLCHAIN_BIN_PATH};${NCS_TOOLCHAIN_BIN_PATH}/Scripts;${NCS_TOOLCHAIN_PATH}/mingw64/bin")
set(NCS_TOOLCHAIN_PYTHONPATH "${NCS_TOOLCHAIN_BIN_PATH}/;${NCS_TOOLCHAIN_BIN_PATH}/Lib;${NCS_TOOLCHAIN_BIN_PATH}/Lib/site-packages")
set(NCS_TOOLCHAIN_PYTHON ${NCS_TOOLCHAIN_BIN_PATH}/python.exe)
set(NCS_TOOLCHAIN_WEST ${NCS_TOOLCHAIN_BIN_PATH}/Scripts/west.exe)
set(NCS_TOOLCHAIN_GIT ${NCS_TOOLCHAIN_PATH}/bin/git.exe)
else()
set(NCS_TOOLCHAIN_EXECUTABLE_SUFFIX "")
if(${CMAKE_HOST_SYSTEM_NAME} STREQUAL Linux)
set(NCS_TOOLCHAIN_BIN_PATH ${NCS_TOOLCHAIN_PATH}/usr/local/bin)
set(NCS_TOOLCHAIN_ENV_PATH "${NCS_TOOLCHAIN_BIN_PATH};${NCS_TOOLCHAIN_PATH}/bin")
else()
set(NCS_TOOLCHAIN_BIN_PATH ${NCS_TOOLCHAIN_PATH}/bin)
set(NCS_TOOLCHAIN_ENV_PATH ${NCS_TOOLCHAIN_BIN_PATH})
endif()
set(NCS_TOOLCHAIN_WEST ${NCS_TOOLCHAIN_BIN_PATH}/west)
set(NCS_TOOLCHAIN_PYTHON ${NCS_TOOLCHAIN_BIN_PATH}/python3)

# This will be deprecated, relying on it may fail for NCS 2.0+
set(NCS_GNUARMEMB_TOOLCHAIN_PATH ${NCS_TOOLCHAIN_PATH})

set(NCS_TOOLCHAIN_GIT ${NCS_TOOLCHAIN_BIN_PATH}/git)
endif()

set(NCS_TOOLCHAIN_CMAKE ${NCS_TOOLCHAIN_BIN_PATH}/cmake${NCS_TOOLCHAIN_EXECUTABLE_SUFFIX})
set(NCS_TOOLCHAIN_NINJA ${NCS_TOOLCHAIN_BIN_PATH}/ninja${NCS_TOOLCHAIN_EXECUTABLE_SUFFIX})
set(NCS_TOOLCHAIN_DTC ${NCS_TOOLCHAIN_BIN_PATH}/dtc${NCS_TOOLCHAIN_EXECUTABLE_SUFFIX})
set(NCS_TOOLCHAIN_GPERF ${NCS_TOOLCHAIN_BIN_PATH}/gperf${NCS_TOOLCHAIN_EXECUTABLE_SUFFIX})
set(NCS_TOOLCHAIN_PROTOC ${NCS_TOOLCHAIN_PATH}/opt/nanopb/generator-bin/protoc${NCS_TOOLCHAIN_EXECUTABLE_SUFFIX})

set(NCS_TOOLCHAIN_VARIANT zephyr)
set(NCS_ZEPHYR_SDK_INSTALL_DIR ${NCS_TOOLCHAIN_PATH}/opt/zephyr-sdk)

# Those are CMake package parameters.
set(NcsToolchain_FOUND True)

if("${CMAKE_SCRIPT_MODE_FILE}" STREQUAL "${CMAKE_CURRENT_LIST_FILE}")
if(${CMAKE_HOST_SYSTEM_NAME} STREQUAL Windows)
set(TMP_TOOLCHAIN_PATH_FILE "${CMAKE_CURRENT_LIST_DIR}/NcsToolchainPath.txt")
else()
set(TMP_TOOLCHAIN_PATH_FILE "/tmp/NcsToolchainPath.txt")
endif()
file(WRITE ${TMP_TOOLCHAIN_PATH_FILE} ${CMAKE_CURRENT_LIST_DIR})
execute_process(COMMAND ${CMAKE_COMMAND} -E md5sum ${TMP_TOOLCHAIN_PATH_FILE}
OUTPUT_VARIABLE MD5_SUM
)
string(SUBSTRING ${MD5_SUM} 0 32 MD5_SUM)
if(${CMAKE_HOST_SYSTEM_NAME} STREQUAL Windows)
execute_process(COMMAND ${CMAKE_COMMAND} -E write_regv
"HKEY_CURRENT_USER\\Software\\Kitware\\CMake\\Packages\\NcsToolchain\\;${MD5_SUM}" "${CMAKE_CURRENT_LIST_DIR}"
)
else()
file(WRITE $ENV{HOME}/.cmake/packages/NcsToolchain/${MD5_SUM} ${CMAKE_CURRENT_LIST_DIR})
endif()
file(REMOVE ${TMP_TOOLCHAIN_PATH_FILE})
endif()

Comparing it my ZEPHYR CLI build process:

(.venv) C:\Users\BSHARMA\Downloads\zephyrproject\zephyr>west build -p always -b nrf52840dk/nrf52840 samples\fund_less3_exer1
-- west build: making build dir C:\Users\BSHARMA\Downloads\zephyrproject\zephyr\build pristine
-- west build: generating a build system
Loading Zephyr default modules (Zephyr base).
-- Application: C:/Users/BSHARMA/Downloads/zephyrproject/zephyr/samples/fund_less3_exer1
-- CMake version: 3.30.5
-- Found Python3: C:/Users/BSHARMA/Downloads/zephyrproject/.venv/Scripts/python.exe (found suitable version "3.11.9", minimum required is "3.10") found components: Interpreter
-- Cache files will be written to: C:/Users/BSHARMA/Downloads/zephyrproject/zephyr/.cache
-- Zephyr version: 3.7.99 (C:/Users/BSHARMA/Downloads/zephyrproject/zephyr)
-- Found west (found suitable version "1.2.0", minimum required is "0.14.0")
-- Board: nrf52840dk, qualifiers: nrf52840
-- ZEPHYR_TOOLCHAIN_VARIANT not set, trying to locate Zephyr SDK
-- Found host-tools: zephyr 0.16.8 (C:/Users/BSHARMA/Downloads/zephyrproject/zephyr-sdk-0.16.8)
-- Found toolchain: zephyr 0.16.8 (C:/Users/BSHARMA/Downloads/zephyrproject/zephyr-sdk-0.16.8)
-- Found Dtc: C:/ProgramData/chocolatey/bin/dtc.exe (found suitable version "1.5.0", minimum required is "1.4.6")
-- Found BOARD.dts: C:/Users/BSHARMA/Downloads/zephyrproject/zephyr/boards/nordic/nrf52840dk/nrf52840dk_nrf52840.dts
-- Generated zephyr.dts: C:/Users/BSHARMA/Downloads/zephyrproject/zephyr/build/zephyr/zephyr.dts
-- Generated pickled edt: C:/Users/BSHARMA/Downloads/zephyrproject/zephyr/build/zephyr/edt.pickle
-- Generated zephyr.dts: C:/Users/BSHARMA/Downloads/zephyrproject/zephyr/build/zephyr/zephyr.dts
-- Generated devicetree_generated.h: C:/Users/BSHARMA/Downloads/zephyrproject/zephyr/build/zephyr/include/generated/zephyr/devicetree_generated.h
-- Including generated dts.cmake file: C:/Users/BSHARMA/Downloads/zephyrproject/zephyr/build/zephyr/dts.cmake
Parsing C:/Users/BSHARMA/Downloads/zephyrproject/zephyr/Kconfig
Loaded configuration 'C:/Users/BSHARMA/Downloads/zephyrproject/zephyr/boards/nordic/nrf52840dk/nrf52840dk_nrf52840_defconfig'
Merged configuration 'C:/Users/BSHARMA/Downloads/zephyrproject/zephyr/samples/fund_less3_exer1/prj.conf'
Configuration saved to 'C:/Users/BSHARMA/Downloads/zephyrproject/zephyr/build/zephyr/.config'
Kconfig header saved to 'C:/Users/BSHARMA/Downloads/zephyrproject/zephyr/build/zephyr/include/generated/zephyr/autoconf.h'
-- Found GnuLd: c:/users/bsharma/downloads/zephyrproject/zephyr-sdk-0.16.8/arm-zephyr-eabi/arm-zephyr-eabi/bin/ld.bfd.exe (found version "2.38")
-- The C compiler identification is GNU 12.2.0
-- The CXX compiler identification is GNU 12.2.0
-- The ASM compiler identification is GNU
-- Found assembler: C:/Users/BSHARMA/Downloads/zephyrproject/zephyr-sdk-0.16.8/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc.exe
-- Configuring done (22.6s)
-- Generating done (2.8s)
-- Build files have been written to: C:/Users/BSHARMA/Downloads/zephyrproject/zephyr/build
←[92m-- west build: building application
[1/133] Generating include/generated/zephyr/version.h
-- Zephyr version: 3.7.99 (C:/Users/BSHARMA/Downloads/zephyrproject/zephyr), build: v3.7.0-4790-g6f64f7755796
[133/133] Linking C executable zephyr\zephyr.elf
Memory region Used Size Region Size %age Used
FLASH: 18684 B 1 MB 1.78%
RAM: 5696 B 256 KB 2.17%
IDT_LIST: 0 GB 32 KB 0.00%
Generating files from C:/Users/BSHARMA/Downloads/zephyrproject/zephyr/build/zephyr/zephyr.elf for board: nrf52840dk

I see that that NCS is not doing most of the functions needed by Zephyr build process. To start with, Zephyr works in a virtual environment (.venv). I don't see any reference to that in NCS process. I have a feeling that my NCS installation may be incomplete or inadequate.

RE: nrfconnect vscode extension problems with "Add Build Configuration" wizard and "Actions" view

dejans — Mon, 25 Nov 2024 12:34:16 GMT

Hi Betta Sharma,

Which operating system do you use?

Which VS Code version do you have?

Best regards,
Dejan

RE: nrfconnect vscode extension problems with "Add Build Configuration" wizard and "Actions" view

Betta Sharma — Sat, 23 Nov 2024 01:07:26 GMT

I have nrf-connect 2024.11.75-win32-x64

nrf-connect-extension-pack-2024.9.5

Zephyr V3.7.99

Zephyr SDK 0.16.8

and I am facing same issues. Add Build Configuration is greyed out and I can't seem to activate it. My code builds correctly in CLI with:

west build -p always -b nrf52840dk/nrf52840 samples\fund_less3_exer1

However, I can't run this from the terminal mode of VS code extension as west command is not recognized.

RE: nrfconnect vscode extension problems with "Add Build Configuration" wizard and "Actions" view

zsn — Sat, 26 Oct 2024 14:38:09 GMT

Hi stefanino ,

1. Make sure you disable Kconfig extension. (Maybe devicetree too, it was disabled too when I was testing it. But now I have the devicetree extension enabled ).

[quote userid="118681" url="~/f/nordic-q-a/114555/nrfconnect-vscode-extension-problems-with-add-build-configuration-wizard-and-actions-view/508017"]

How did you exactly change the board path?

[/quote]

good question 🙂. Im just scratching my head to remember what I did. But not really. Only one thing I can say is that im sure I had a only change on my custom board in my custom module.

So, maybe you can try to remove your custom board if you have. And observe if the extension is working or not.

RE: nrfconnect vscode extension problems with "Add Build Configuration" wizard and "Actions" view

stefanino — Sat, 26 Oct 2024 13:21:24 GMT

Hi zsn ,

I tried the workaround (again on Zephyr 3.7 and latest vscode extension). Pristine build from the terminal works like a charm.

However, the action buttons are still not working in my case (view is empty with, at best, a progress bar never ending).

How did you exactly change the board path?

cheers

RE: nrfconnect vscode extension problems with "Add Build Configuration" wizard and "Actions" view

dejans — Tue, 22 Oct 2024 09:16:49 GMT

Hi,

Release Notes webpage for nRF Connect for VS Code extension v2024.9.31 mentions added Hardware Model v2 support. There might not be full HMv2 support in the extension yet but build system support should be there.

Best regards,
Dejan

RE: nrfconnect vscode extension problems with "Add Build Configuration" wizard and "Actions" view

zsn — Tue, 22 Oct 2024 08:14:48 GMT

just an additional update. I think nrf-extension is not support hmv2, thats the reason we are seeing a blank page, so, had a change on the board path in my module, and now im getting this error but i can see now the build config page.. So just the workaround, I am creating build configuration on the terminal by running

 west build -b yourboard --pristine

then you will be able to run action buttons and the rest of the functionalities.

RE: nrfconnect vscode extension problems with "Add Build Configuration" wizard and "Actions" view

dejans — Tue, 22 Oct 2024 07:46:57 GMT

Hi,

[quote user="nunofrd"]Allow me to correct that information. It is supported - it is the first version that supports it, and I believe NCS support is built on that.[/quote]

This is correct. I am sorry for confusion. I have edited my previous reply.

Please let me know if you have any further questions.

Best regards,
Dejan

RE: nrfconnect vscode extension problems with "Add Build Configuration" wizard and "Actions" view

nunofrd — Mon, 21 Oct 2024 14:41:44 GMT

Allow me to correct that information. It is supported - it is the first version that supports it, and I believe NCS support is built on that.

In fact, I'm currently using it, according with the available guidelines.

Zephyr 3.7 LTS release notes -https://docs.zephyrproject.org/latest/releases/release-notes-3.7.html

Board porting guide to HMv2 - https://docs.zephyrproject.org/latest/hardware/porting/board_porting.html#hw-model-v2

Thanks

RE: nrfconnect vscode extension problems with "Add Build Configuration" wizard and "Actions" view

dejans — Mon, 21 Oct 2024 14:30:32 GMT

Hi,

[quote user="nunofrd"]Just a note to clarify that Zephyr 3.7 is a tagged LTS release, it is not Zephyr main (dev head)[/quote]

HMv2 is supported in Zephyr v3.7 but extension v2024.9.87 might not work as expected with Zephyr v3.7.

Best regards,
Dejan

RE: nrfconnect vscode extension problems with "Add Build Configuration" wizard and "Actions" view

nunofrd — Mon, 21 Oct 2024 14:02:00 GMT

Thank you for the update. Just a note to clarify that Zephyr 3.7 is a tagged LTS release, it is not Zephyr main (dev head)

RE: nrfconnect vscode extension problems with "Add Build Configuration" wizard and "Actions" view

dejans — Mon, 21 Oct 2024 13:59:24 GMT

Hi,

The official extension v2024.9.87 is not compatible with Zephyr main. We will be working on this in time to come. Unfortunately, I cannot provide any estimate on this at this point.

Best regards,
Dejan

RE: nrfconnect vscode extension problems with "Add Build Configuration" wizard and "Actions" view

stefanino — Mon, 21 Oct 2024 10:59:49 GMT

Hi dejans and nunofrd ,

thank you for the pointers. I just tested with Zephyr v3.6.0 (from zephyr-rtos GitHub repo) and I'm happy to report that the latest extension (wizards and views) work as expected

so maybe the issue is related indeed to the introduction of HWMv2?

is Nordic planning to add support / move to Zephyr 3.7?

cheers

RE: nrfconnect vscode extension problems with "Add Build Configuration" wizard and "Actions" view

dejans — Mon, 21 Oct 2024 10:06:39 GMT

Hi,

Zephyr RTOS fork revision that is used in the NCS can be found in west.yml file which is located in the nrf folder.

Best regards,
Dejan

RE: nrfconnect vscode extension problems with "Add Build Configuration" wizard and "Actions" view

nunofrd — Sun, 20 Oct 2024 19:55:18 GMT

Just in case it is useful - Zephyr 3.7 was the first version supporting HMv2. This was also the first nRF extension with support for HMv2.

RE: nrfconnect vscode extension problems with "Add Build Configuration" wizard and "Actions" view

stefanino — Sun, 20 Oct 2024 08:54:30 GMT

Can you please advise a released tag zephyr version (from NCS I guess) that you think should work so I can give it a try and see if I can reproduce the bug or not?

RE: nrfconnect vscode extension problems with "Add Build Configuration" wizard and "Actions" view

dejans — Fri, 18 Oct 2024 08:23:58 GMT

Hi,

This seems to be related to the Zephyr version used. What is expected to be working is when you use tagged NCS versions. The extension has been mainly tested to be working with released NCS versions and those have been proved to work only with just certain Zephyr versions.

Best regards,
Dejan

RE: nrfconnect vscode extension problems with "Add Build Configuration" wizard and "Actions" view

nunofrd — Thu, 17 Oct 2024 11:31:18 GMT

Hi Stefanino,

Yes, both extension modules - "nRF Connect for VS Code" and nRF Device Tree - report that.

I've also shared the logs.

RE: nrfconnect vscode extension problems with "Add Build Configuration" wizard and "Actions" view

stefanino — Thu, 17 Oct 2024 11:02:43 GMT

Hi nunofrd ,

not finding SOC seems to be a common theme between mine and your issue. Does your extension report the same error as mine?

RE: nrfconnect vscode extension problems with "Add Build Configuration" wizard and "Actions" view

stefanino — Thu, 17 Oct 2024 10:59:34 GMT

Hi dejans,

I used the following

- nrf SDK 2.7.0

- Zephyr 3.7 (actually 3.7.99 which is the rolling development main branch, i.e. no release tag)

RE: nrfconnect vscode extension problems with "Add Build Configuration" wizard and "Actions" view

nunofrd — Wed, 16 Oct 2024 16:02:51 GMT

Not Stefanino here,

Just wanted to share this link for issue I opened, that seems related.

devzone.nordicsemi.com/.../nrf-connect-sdk-extension-v2024-9-87-stopped-working-for-building-zephyr-apps-hwmv2

In my case, using Zephyr 3.7.

Thanks

RE: nrfconnect vscode extension problems with "Add Build Configuration" wizard and "Actions" view

dejans — Wed, 16 Oct 2024 13:45:27 GMT

Hi stefanino ,

Which specific versions of nRF Connect SDK and Zephyr did you use when you made the list of what is working and what not?

Best regards,
Dejan

RE: nrfconnect vscode extension problems with "Add Build Configuration" wizard and "Actions" view

stefanino — Tue, 15 Oct 2024 20:48:03 GMT

Hi dejans ,

- v2024.9.87 + nrf SDK --> working

- v2024.9.87 + Zephyr (no nrf SDK) --> not working

- v2024.9.31 + nrf SDK --> working

- v2024.9.31 + Zephyr (no nrf SDK) --> not working

- v2024.6.20 + Zephyr (no nrf SDK) --> working

as I pointed out, maybe the error below is a clue?

RE: nrfconnect vscode extension problems with "Add Build Configuration" wizard and "Actions" view

dejans — Tue, 08 Oct 2024 14:36:40 GMT

Hi,

There is west.yml file in nrf folder which contains corresponding zephyr version for specific NCS version, for example NCS version 2.7.0 specifies sdk-zephyr revision v3.6.99-ncs2.

zafer sen Could you provide more specific information on which combination you tested to be working, and which are not working?

stefanino Could you provide more information about your setup, your environment and which specific Zephyr versions work with specific versions of extension (and which not) in your case?

Best regards,
Dejan