Build Configuration Issue Due to Incomplete SDK : kcmake.conf

RE: Build Configuration Issue Due to Incomplete SDK : kcmake.conf

Milan Bhatnagar — Fri, 24 Oct 2025 12:57:12 GMT

Done, we have created a new suppot case

RE: Build Configuration Issue Due to Incomplete SDK : kcmake.conf

Amanda Hsieh — Fri, 24 Oct 2025 12:32:15 GMT

Please create a new support case since the last issue is away from the original scope.

RE: Build Configuration Issue Due to Incomplete SDK : kcmake.conf

Milan Bhatnagar — Fri, 24 Oct 2025 06:47:06 GMT

Greetings!

We were able to solve previous query and have following query now:

Can I use any of the header pins on P20 of nRF52840 DK as the on-board 3.3 V rail? If yes then which is most preferred for current and later use in the microprocessor for 3V-3.3V Vout

Please suggest.

RE: Build Configuration Issue Due to Incomplete SDK : kcmake.conf

Amanda Hsieh — Wed, 08 Oct 2025 14:02:36 GMT

It's strange that the issue only happens to your project. The board path is updated in the NCS v2.7.0 (C:\ncs\v2.7.0\zephyr\boards\nordic\nrf52840dk). It seems your project looks for the old board path setting before v2.7.0. I would suggest you remove the board path setting in your project or duplicate an NCS v2.7.0 sample as a base for development.

RE: Build Configuration Issue Due to Incomplete SDK : kcmake.conf

Milan Bhatnagar — Wed, 08 Oct 2025 13:07:35 GMT

Amanda Hsieh

Greetings!

No , NCS sample was build fine. Major problem is the recurring error due to absence of board file in C:\ncs\v2.7.0\zephyr\boards\arm\nrf52840dk_nrf52840, due to absence of nrf52840dk_nrf52840 & nrf52840dk_nrf52840_defconfig. Tried updating SDK but this board files remain absent always. Is there any other way out to resolve this issue ? My SDK is v2.7.0 and Toolchain is 2.7.0.

RE: Build Configuration Issue Due to Incomplete SDK : kcmake.conf

Amanda Hsieh — Wed, 08 Oct 2025 12:47:18 GMT

Hi,

Do you also experience the same issue when building an NCS sample? If so, please try to reinstall the SDK. If the problem persists after a clean reinstall, double-check that your SDK directory contains the required board files.

Regards,
Amanda H.