Unable to build standard Nordic application: Blinky, using the nRF Connect SDK v2.9.1

[Jacek Majda]

Good day,

I tried to build the standard Nordic application: Blinky for the nrf52840dk/nrf52840 board from the following directory on my PC: c:\ncs\v2.9.1\zephyr\samples\basic\blinky.

I was using:

1. VS Code

2. nRF Connect SDK v2.9.1

3 nRF Connect SDK Toolchain v2.9.1

4. Board Target:  nrf52840dk/nrf52840

as shown on the attached Screenshot_3 and Screenshot_4.

However, some error messages came up, as shown in the attached Screenshot_5 and Screenshot_2.

I also attach the whole build log split between the attached Screenshot_1 and Screenshot_2 - as I could not find an easy way to save or print the whole log file.

What shall I do to successfully build that application?

Regards,

JM

[Maria Gilje]

Hi JM,

It looks like there is something wrong with your toolchain or SDK.

When you installed nRF Connect SDK, did you follow all the instructions here? 

Have you modified or moved any directories after installation? The error refers to "drivers/Kconfig" missing. Can you verify that "ncs/v2.9.1/zephyr/drivers/Kconfig" exists on your PC?

nRF Connect for VS Code has a feature to refresh the SDK and toolchain. If you are not familiar with that feature, they are found by hovering over Manage toolchains/SDKs as a circle arrow.

Best regards,

Maria

[Jacek Majda]

Hi Maria,

I tried to verify that "ncs/v2.9.1/zephyr/drivers/Kconfig" exists on my PC - but it does not exist.

I then tried to refresh the SDK and toolchain by clicking a circular arrow in the Manage toolchains/SDKs.

I then tried to verify that "ncs/v2.9.1/zephyr/drivers/Kconfig" exists on my PC - but it still did not show in the "ncs/v2.9.1/zephyr" directory, as shown on the attached Screenshot.

I recently installed on my PC the nRF Connect SDK v2.7.0 - then I removed that v2.7.0 version and I installed the nRF Connect SDK v2.9.1.

Then, after experiencing some issues, I re-installed the nRF Connect SDK v2.9.1 (by removing it and then by installing it again).

Best Regards,

JM