Error When Compiling Sample Project

[Asanka]

Hello,

I recently got an nRF7002 DK and am trying things out. I recently tried to run a sample Matter project and I got this error when compiling. I was following the tutorial given here.

[{
	"resource": "/c:/ncs/v2.5.0/nrf/subsys/partition_manager/partition_manager_enabled.conf",
	"owner": "kconfig0",
	"severity": 8,
	"message": "Kconfig failed: [Errno 2] No such file or directory: 'c:/ncs/v2.5.0/zephyr/${zephyr_connectedhomeip_module_dir}/config/nrfconnect/chip-module/kconfig.mcuboot.root'",
	"startLineNumber": 1,
	"startColumn": 1,
	"endLineNumber": 1,
	"endColumn": 1
}]

My development environment is Windows 64 bit and I installed nRF through the nRF Connect Desktop App. I'm using toolchain version 2.5.0. Any Help is appreciated. Thanks.

[Charlie]

Hi Asanka,

I did a quick try with my setup. light_buble sample can be built without issue.

Here is my configuration and building log. Can you share your building log to show how it fails?

Best regards,

Charlie

[Asanka]

Thanks for the quick reply. This is my build configuration:

This is the build log:

Build Log

I also need to point out that for some reason the nRF Connect for VS Code doesn't automatically detect the SDK. I've tried reinstalling the whole toolchain from both the nRF Connect Desktop Application and VS Code itself but the issue still persisted. Even if I leave the `Topdir` setting empty or `${nrf-connect.sdk:2.5.0}`, it still says that I have to install the SDK. nRF Connect Application detects everything properly. I've tried installing SDK version 2.4.2, reinstalling the whole nRF applications (nRF Connect Desktop and CLI tool including a fresh install of the toolchain) and even reinstalling VS Code and the extensions (Deleted the settings file as well) but still the issue exists. It only works if I add `C:\ncs\v2.5.0` manually to the `Topdir`. This was not the case when I started off however it appeared after I installed Zap (Not sure if that's relevant).

I wanted to mention this just in case it has something to do with the issue.

Thank you.

[Charlie]

Hi Asanka,

Hard to say where the issue comes from based on the current evidence. ZAP tool is not very friendly to Windows PC, I remember I only made it work on Ubuntu before.

Anyway, a reinstall will mostly hopeful to solve this issue. Could you try the following steps?

1) Clean up all the current related installations about NCS.

2) Open VS code and install toolchain and SDK from nRF Connect VS code extension.

3) Build the official sample located in NCS\v2.5.0\nrf\samples\matter\light_switch

Best regards,

Charlie

[Asanka]

Hello,

I have an update. I reinstalled everything and I tried the light_switch example. I am still running into the same error. However, I made the following changes to the CMakeLists.txt file.

Replaced:

set(mcuboot_KCONFIG_ROOT "\\\${ZEPHYR_CONNECTEDHOMEIP_MODULE_DIR}/config/nrfconnect/chip-module/Kconfig.mcuboot.root")
set(multiprotocol_rpmsg_KCONFIG_ROOT "\\\${ZEPHYR_CONNECTEDHOMEIP_MODULE_DIR}/config/nrfconnect/chip-module/Kconfig.multiprotocol_rpmsg.root")
set(hci_rpmsg_KCONFIG_ROOT "\\\${ZEPHYR_CONNECTEDHOMEIP_MODULE_DIR}/config/nrfconnect/chip-module/Kconfig.hci_rpmsg.root")

With:

set(mcuboot_KCONFIG_ROOT ${ZEPHYR_CONNECTEDHOMEIP_MODULE_DIR}/config/nrfconnect/chip-module/Kconfig.mcuboot.root)
set(multiprotocol_rpmsg_KCONFIG_ROOT ${ZEPHYR_CONNECTEDHOMEIP_MODULE_DIR}/config/nrfconnect/chip-module/Kconfig.multiprotocol_rpmsg.root)
set(hci_rpmsg_KCONFIG_ROOT ${ZEPHYR_CONNECTEDHOMEIP_MODULE_DIR}/config/nrfconnect/chip-module/Kconfig.hci_rpmsg.root)

Added:

set(ZEPHYR_CONNECTEDHOMEIP_MODULE_DIR "C:/ncs/v2.5.0/modules/lib/matter/config/zephyr/chip-module")

As shown below:

Now I run into an error but the Problems tab doesn't show any as below.

Build Log

[Charlie]

Hi Asanka,

Can you try to add and build the official sample located in NCS\v2.5.0\nrf\samples\matter\light_switch to see what happens?

Best regards,

Charlie

[Asanka]

Still run into the same error.

[Charlie]

Hi Asanka,

How about your building process? Can you build the FW now?

I have the same "error" report on PROBLEM, this is not related to your project. 

The PROBLEM reported here is provided by VS code to generally scan your folders added into the workspace and report potential errors. It is not very intelligent sometimes.

The error reported here may just because the folder path is not known by VS code or its extensions, but for the toolchain, it has no problem.

Best regards,

Charlie

[Asanka]

Hello,

No, the output is empty.

Also, now the device is also not getting detected.

However, I feel like all of these issues are VS Code and its extension-related issues as none of these issues seem to exist in the nRF Connect App.

[Asanka]

Hello,

I think the issue is fixed. The device is not showing up fixed after several reboots. I ran the last command that caused the issue in the terminal and got a better explanation of what was happening. Apparently, the path to cmd.exe (C:\Windows\System32) had gone away from the environment variables. This was causing the compilation process to run into an error without even showing an error on VS Code. After adding it to the path variables, it worked. The code was compiled and uploaded to the device correctly.

So to summarize there had been two major issues with the code. One is that the path to

ZEPHYR_CONNECTEDHOMEIP_MODULE_DIR

had been missing. Adding the path to the CMakeLists.txt file fixed it.

Next issue had been the Path variable to System32 folder. Adding it to the Path variable in System > About > Advanced system settings > System Properties > Advanced > Environment Variables fixed the issue.

Seems like installing Zap messed up the path variables in the system.