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

[Maria Gilje]

Hi JM,

Jacek Majda said:

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.

Thank you for checking this!

I have to admit that it is difficult to figure out what is going wrong here. It is very likely that something is going wrong during installation, since you are using a fresh install and a whole directory is missing. 

Do you see the same for several nRF Connect SDK versions or is v2.9.1 the only version which is missing zephyr/drivers? nRF Connect SDK v3.0.0 was released last week, so I recommend upgrading if you only have the issues with v2.9.1.

Can you test out if it works to install the SDK in another location than the default? You can configure this during the installation process on the "Install nRF Connect SDK (2/2)" step.

For reference, this is how my ncs/v2.9.1/zephyr looks like:

So it it only zephyr/drivers which is missing in your install (as far as I can tell).

edit: If you can make sure that you are using the latest versions of VS Code and nRF Connect for VS code extension we can rule out older versions of those as a factor.

Best regards,

Maria

[Maria Gilje]

Hey again,

I realise that I was referring to the wrong functionality when I was talking about refreshing the SDK and toolchain. The functionality I intended to point you to was where to perform a "west update". This is found via Manage SDKs -> Manage West Workspace -> West Update. Apologies for the inconvenience.

Best regards,

Maria

[Jacek Majda]

Hi Maria,

As advised, I tried to install the nRF Connect SDK v2.9.1 in another location than the default location, by choosing a new installation directory: C:/ncs_2_9_1/  - and it has worked!

The relevant directory was now included in C:/ncs_2_9_1/v2.9.1/zephyr/drivers/Kconfig and I was able to successfully build the standard Nordic application: Blinky for the nrf52840dk/nrf52840 board.

I then tried to build the Acconeer default sample: "example_control_helper" for the custom board xm126/nrf52840 - but many error messages came up, that I forwarded to the Acconeer HelpDesk for assistance.

The reply from the Acconeer HelpDesk was as follows:

"The error messages created during the build process of the Acconeer default sample "example_control_helper", for the custom board xm126/nrf52840 - seem to indicate that there is a 250 character limit for the full path which seems to prevent it from creating the object files. Three months ago, Nordic did not have a solution for it, except to use shorter paths for the project"

So, in view of the above I decided to shorten a path for my project by changing the name of the installation directory for nRF Connect SDK v2.9.1 from C:/ncs_2_9_1/   to C:/ncs9/.

However, I did not succeed in installing the nRF Connect SDK v2.9.1 in the new directory: C:/ncs9/  and the following error message came up half-way through the installation process:

"ERROR: Failed with exit code 1.

Failed to download toolchain bundle.

Caused by: An existing connection was forcibly closed by the remote host. OS error 10054".

as shown on the attached screenshot.

I tried several times to repeat the process of installation of the nRF Connect SDK v2.9.1 (from the Toolchain Manager v1.6.0) - but each time, about half-way through the process of installation - the above error message came up.

How can I successfully install the nRF Connect SDK v2.9.1 on my PC?

Best Regards,

JM