Build Problems With Sample Copy - Nordic Connect Under VSCode

[Mark]

I am attempting to get familiar with the NDEF support on the nRF54L15 DK.  After creating a copy of a sample based on the WRITABLE_NDEF_MSG example, I create a build configuration targeting the nRF15L15 DK.  The attempt to build the project generates 4 "problems", including the following:

• The Button and LED Library for Nordic DKs must be enabled by CONFIG_DK_LIBRARY to be included in the build
• The Non-volatile Storage must be enabled by CONFIG_NVS to be included in the build

The AI Assistant acknowledged the nRF Connect implementation in VSCode was faulty and attempted to guide me through the process of resolving the issue.  The assistant prompted me to  modify the build configuration to define the configuration file as "prj.conf".  This generated additional "problems" on the successive build and the assistant then had me adding the appropriate configuration requirements to the prj.conf file.  Unfortunately, I found myself in an endless loop with the assistant attempting to alleviate one problem after another and never achieved a problem-free build.

Is there something else I must do after creating the project to get these configuration issues resolved for a proper build of the sample code under VSCode, or is this a hopeless endeavor?

Best Regards,

Mark

[runsiv]

Hi Mark

Which SDK version are you using? If you are using the DK as target it should already include the CONFIG_DK_LIBRARY in its config files.  You should also not be using CONFIG_NVS on the 54L15 as it has RRAM and therefor should use CONFIG_ZMS which is a different system designed for RRAM.  This can be enabled using 

CONFIG_ZMS=y CONFIG_SETTINGS_ZMS=y

Regards

Runar

[Mark]

Hello Runar,

I am currently using version 3.2.2 of the SDK.

Thanks for the heads-up on the RRAM configuration... I'll give that a try, but I am also battling the tools complaining that prj.conf is not part of the active build context.  I have configured the "Base configuration files (Kconfig fragments)" to specify this file per the AI Assistant instructions.  Is this the proper way to specify the use of this file?

Mark

[Mark]

Hello Runar,

I attempted to modify the configuration as you described, but it appears I need additional configuration parameters defined.  I now receive the following error messages:

With regard to prj.conf:

CONFIG_FLASH_PAGE_LAYOUT was assigned the value y, but got the value n. Missing dependencies:
FLASH_HAS_PAGE_LAYOUT

CONFIG_FLASH_MAP was assigned the value y, but got the value n. Missing dependencies:
FLASH_HAS_DRIVER_ENABLED

With regard to main.c:

The Button and LED Library for Nordic DKs must be enabled by CONFIG_DK_LIBRARY to be included in the build

With regard to ndef_file_m.c:

#include errors detected based on information provided by the configurationProvider setting. Squiggles are disabled for this translation unit (C:\ABG\Core\Devices\writable_ndef_msg_test\src\ndef_file_m.c).

cannot open source file "zephyr/syscall_list.h" (dependency of "C:\Users\aiujc83\.vscode\extensions\ms-vscode.cpptools-1.31.3-win32-x64\bin\zephyr\kernel.h")

cannot open source file "zephyr/syscalls/flash.h" (dependency of "C:\Users\aiujc83\.vscode\extensions\ms-vscode.cpptools-1.31.3-win32-x64\bin\zephyr\fs\zms.h")

BTW - I currently have the following extensions installed with VS Code... anything wrong here?

nRF Connect for VS Code  v2026.3.1585

nRF Connect for VS Code Extension Pack  v2025.4.4

nRF Device Tree  v2026.3.617

nRF Kconfig  v2026.1.230

nRF Terminal  v2026.3.289

Do I need to install a Zephyr extension as well, or should this be dealt with via the nRF Connect SDK?

Mark

[Mark]

I HAVE A SOLUTION...

Apparently the problems all stemmed from the fact that the path to the project directory was too long.  When I moved the project directory directly off the root drive, the builds began behaving as expected.

Thanks for the suggestions as I worked through this issue!

Mark

[runsiv]

Glad to hear it. Windows path lengths and zephyr can be an issue at times and it will give some really strange errors. In general I would recommend having the SDK placed high up in your file system and the same with the project folders

Regards

Runar