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

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

Parents
  • 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

  • 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

  • Hi Maria,

    As advised, I removed/uninstalled all SDK applications and folders that were created during my previous attempts to install SDK v2.9.1.

    Then I tried once again to install SDK v2.9.1 in the new install directory: C:\nc1 and this time I succeeded with installing the SDK v2.9.1 in my new install directory C:\nc1.

    I then had to re-install the VS Code by downloading the Virtual Studio Code Installer for Windows and by running that installer.

    Then, on the VS Code main page, I clicked the icon that represents extensions and I was prompted to install a Toolchain to get started.

    So, I successfully installed Toolchain version 2.9.1.

    I then tried to open an existing application: Blinky located at: C:\nc1\v2.9.1\zepyr\samples\basic\blinky   and build configuration for the board nrf52840dk/nrf52840 and the result was successful.

    I successfully created the build configuration for the sample Blinky for the board nrf52840dk/nrf52840.

    I then tried to open an existing application, the Acconeer default sample: example_control_helper  - without any modifications located at:

    C:\Acconeer\SDK_for_xm126-version1.10.0\acconeer_xm126_a121-v1_10_0\xm126\samples\example_control_helper 

    for the xm126/nrf52840 custom board.

    But the same error as before came up:

    "C:/Acconeer/SDK_for_xm126-version1.10.0/acconeer_xm126_a121-v1_10_0/xm126/samples/example_control_helper/build/example_control_helper/zephyr/drivers/interrupt _controller/CMakeFiles/drivers--interrupt-controller.dir/./  - has 217 characters.

    The maximum full path to an object file is 250 characters, so the object file: C_/nc1/v2.9.1/zephyr/misc/empty-file.c.obj can not be safely placed under that directory and the build may not work correctly.

    So I tried to shorten that path C:\Acconeer\...\samples\exmple_control_helper - but there were still problems, so I removed that path completely from the C:\Acconeer directory and I placed the Acconeer SDK version 1.10.0 in the C:\Acconeer\xm126 directory but still no success.

    When I try to build the Acconeer sample: example_control_helper for the xm126/nrf52840 custom board, and I click on "Add build configuration" - I can not select the xm126/nrf52840 custom board because now under the "Board target" options - there is no "Custom" board option any more, as shown on the attached screenshot.

    I even tried to re-install the Acconeer SDK v1.10.0 in another directory: c:\users\jacek\Downloads\acconeer_xm126_a121-v1_10_0  - but still the same problem persists, namely, when I try to build the Acconeer sample "example_control_helper" for xm126/nrf52840 custom board, and I click on the "Add build configuration" button, I can not select the xm126/nrf52840 custom board because now under the "Board target" options - there is no "Custom" board option any more, as shown on the attached screenshot.

    How can this problem be overcome?

    Best Regards

    JM

      

  • Hi JM,

    I was able to find an internal thread where a similar issue was resolved. The advice there was to place the build directory closer to the C: drive. In your case, maybe something like this can work?

    -d C:\Acconeer\builds\example_control_helper\build

    The above argument can be added to the west build command from command line. I don't think there is a way to configure this with the nRF Connect for VS Code extension.

    If you are not used to command line building, please find relevant documentation here under the "Command Line" tab. To ensure a correct environment in the terminal, open the nRF Connect terminal in VS Code:

    Best regards,

    Maria

  • Hi Maria,

    I will gladly try to use your recommended procedure of placing the build directory closer to the c: drive and using the west build command when building a configuration for the Acconeer: "example_control_helper": - but I am now again experiencing problems with building a Nordic sample: Blinky for the nfr52840dk/nrf52840 board.

    I have re-installed the VS Code by downloading the Visual Studio Code Installer for Windows and by running that installer.

    Then, on the VS Code main page, I clicked the icon that represents extensions and I was prompted to install a Toolchain to get started.

    So, I successfully installed Toolchain version 2.9.1.

    I then opened an existing application: "Blinky" located at: c:\nc1\v2.9.1\zephyr\samples\basic\blinky and I tried to build configuration for the board: nrf52840dk/nrf52840 by clicking on the "+Add build configuration" for board Target: nrf52840dk/nrf52840.

    However, during the build process my Antivirus software: McAfee discovered a threat in a file that was being used, as shown in the attached screenshot.

    The warning message from my McAfee Antivirus software was as follows:

    "Threat name: hti!7b0978c7

    File used: c:\ncs\toolchains\b620d30767\opt\zephyr-sdk\arm-zephyr-eabi\bin\arm-zephyr-eabi-objcopy.exe

    Status: Quarantined

    Date/Time:  08/05/2025 ;16:03

    Suspicious items are kept in a secure quarantine area so that they can not harm your device.

    You can delete or restore these items"

    So, I deleted that suspicious file and I tried to build again the sample Blinky, but without success.

    So, I re-installed the VS Code and then on the VS Code main page, I clicked the icon that represents extensions and I was prompted to install a Toolchain to get started.

    So, I successfully installed Toolchain version 2.9.1. again.

    I then opened the existing application: Blinky, located at: c:\nc1\v2.9.1\zephyr\samples\basic\blinky  and I tried again to build configuration for board: nrf52840dk/nrf52840.However, during the build process my Antivirus software: McAfee once again discovered a threat in the same file as before, that was being used, as shown in the attached screenshot.

    What shall I do now?

    Shall I ignore the warning from McAfee Antivirus software and restore the suspected file, listed in the McAfee warning, instead of deleting it?

    Best Regards,

    JM

  • Hi JM,

    Antivirus software can report false positives for some files in our toolchain. Restoring it should not cause damage to your machine. 

    Best regards,

    Maria

  • Hi Maria,

    After having experienced many problems with using nRF Conect SDK v2.9.1, I decided to delete all apps and folders related to VS Code, nRF SDK 2.9.1 and Acconeer.and to install nRF SDK v3.0.0.

    I installed the nRF Connect SDK following the steps below:

    1. Firstly, I downloaded and installed on my PC the VS Code from the Visual Studio Code website.

    2. I then installed the nRF Connect extension pack, by clicking, on the main screen of VS Code the icon representing extensions, and then selecting the nRF Connect extension pack to install.

    3. Once installed, I clicked the icon representing the nRF extension and I selected: "Install Toolchain" and I successfully installed Toolchain v3.0.1.

    4. Once I installed Tooolchain v3.0.1, I installed the nrf Connect SDK v3.0.0 by clicking on "Manage SDKs" and installing the nRF Connect SDK v3.0.0.   The nRF Connect SDK v3.0.0 was installed on my PC  at: c:\ncs\v3.0.0

    5. After that, I was able to successfully build configuration for the sample: "Blinky" for the Board Target: nrf52840dk/nrf52840.

    I then tried to build configuration for the Acconeer example: "example_control_helper", located at: c:\Acconeer_SDK_v1_10\acconeer_xm126_a121-v1_10_0_(1)\xm126\samples\example_control_helper

    as follows:

    1. I clicked on "Open Existing Application" and I selected the folder: c:\Acconeer_SDK_v1_10\acconeer_xm126_a121-v1_10_0_(1)\xm126\samples\example_control_helper

    2. I clicked on the "+Add build configuration" but I did not see any custom board target options that I could use to build configuration for this sample for my Acconeer xm126 module, so I decided to create a new board by clicking on "Create new board".

    3. I was prompted to enter, under "Board Name" a machine-readable board ID to be referenced by the west build command but my attempts to enter "xm126" or "xm126_module" or similar names as the "Board Name" were unsuccessful and the following error message came up:  'Board Name must match  pattern: "^[a-zA-z0-9_-]+$"'

    As I was unable to create a new board for the Acconeer example: "example_control_helper" for the Acconeer xm126 module using the nRF Connect SDK v3.0.0 from VS Code -I deleted that SDK v 3.0.0 from VS Code using: Manage SDKs>Delete SDK and then I successfully installed the nRF Connect SDK v2.9.1 at C:\ncs\v2.9.1,using: Manage SDKs>Install SDK (v2.9..1).

    I then successfully built configuration for the sample; "Blinky" for the board: nrf52840dk/nrf52840.

    I then opened an existing application, the Acconeer example: "example_control_helper" and I tried to build configuration for this Acconeer example for the Acconeer xm126 module.

    But when I clicked on the "+Add build configuration" - I did not see any custom board target options that I could use to build configuration for this sample for my Acconeer xm126 module, so I decided to create a new board by clicking on "Create new board".

    This time I was able to enter, under "Board name", the name: "xm126" and other required data, as follows:

    Board Name: xm126

    Description: Acconeer xm126 module

    Vendor: Acconeer

    SoC: nRF52840-Q1AA

    Board Root: c:\Acconeer_SDK_v1_10\Accconeer_xm126_a121-v1_10_0_(1)\xm126

    and I clicked on "Create Board".

    After I clicked "Create Board", I saw the message: "Board xm126 has been created at: c:\Acconeer_SDK_v1_10\acconeer_xm126_a121-v1_10_0_(1)\xm126 and I was able to verify that the board xm126 has been created on my PC in the directory: c:\Acconeer_SDK_v1_10\acconeer_xm126_a121-v1_10_0_(1)\xm126\boards\acconeer\xm126

    as shown on the attached Screnshot_1.

    I then tried to build configuration for the Acconeer example: "example_control_helper" for my newly created board: xm126, using the following west build command:

    west build -b xm126 -d c:\Acconeer\builds\example_control_helper\build

    but the following error came up:

    "No board named 'xm126' found. Please choose one of the following boards: ...

    - as shown on the attached Screenshot_2.

    and the message:

    CMake Error at: c:/ncs/v2.9.1/Zephyr/cmake/modules/boards.cmake:228 (message): Invalid board; see above.

    -as shown on the attached Screenshot_3.

    So, despite the new board: xm126 having been created in the folder: c:\Acconeer_SDK_v1_10\acconeer_xm126_a121-v1_10_0_(1)\xm126\boards\xm126\acconeer\xm126 - the west build command generated Error Message: "No board named 'xm126' found".

    How can I overcome this problem to be able to successfully build configuration for the Acconeer example: "example_control_helper" for my newly created board: xm126 ?

    Best Regards,

    JM 

Reply
  • Hi Maria,

    After having experienced many problems with using nRF Conect SDK v2.9.1, I decided to delete all apps and folders related to VS Code, nRF SDK 2.9.1 and Acconeer.and to install nRF SDK v3.0.0.

    I installed the nRF Connect SDK following the steps below:

    1. Firstly, I downloaded and installed on my PC the VS Code from the Visual Studio Code website.

    2. I then installed the nRF Connect extension pack, by clicking, on the main screen of VS Code the icon representing extensions, and then selecting the nRF Connect extension pack to install.

    3. Once installed, I clicked the icon representing the nRF extension and I selected: "Install Toolchain" and I successfully installed Toolchain v3.0.1.

    4. Once I installed Tooolchain v3.0.1, I installed the nrf Connect SDK v3.0.0 by clicking on "Manage SDKs" and installing the nRF Connect SDK v3.0.0.   The nRF Connect SDK v3.0.0 was installed on my PC  at: c:\ncs\v3.0.0

    5. After that, I was able to successfully build configuration for the sample: "Blinky" for the Board Target: nrf52840dk/nrf52840.

    I then tried to build configuration for the Acconeer example: "example_control_helper", located at: c:\Acconeer_SDK_v1_10\acconeer_xm126_a121-v1_10_0_(1)\xm126\samples\example_control_helper

    as follows:

    1. I clicked on "Open Existing Application" and I selected the folder: c:\Acconeer_SDK_v1_10\acconeer_xm126_a121-v1_10_0_(1)\xm126\samples\example_control_helper

    2. I clicked on the "+Add build configuration" but I did not see any custom board target options that I could use to build configuration for this sample for my Acconeer xm126 module, so I decided to create a new board by clicking on "Create new board".

    3. I was prompted to enter, under "Board Name" a machine-readable board ID to be referenced by the west build command but my attempts to enter "xm126" or "xm126_module" or similar names as the "Board Name" were unsuccessful and the following error message came up:  'Board Name must match  pattern: "^[a-zA-z0-9_-]+$"'

    As I was unable to create a new board for the Acconeer example: "example_control_helper" for the Acconeer xm126 module using the nRF Connect SDK v3.0.0 from VS Code -I deleted that SDK v 3.0.0 from VS Code using: Manage SDKs>Delete SDK and then I successfully installed the nRF Connect SDK v2.9.1 at C:\ncs\v2.9.1,using: Manage SDKs>Install SDK (v2.9..1).

    I then successfully built configuration for the sample; "Blinky" for the board: nrf52840dk/nrf52840.

    I then opened an existing application, the Acconeer example: "example_control_helper" and I tried to build configuration for this Acconeer example for the Acconeer xm126 module.

    But when I clicked on the "+Add build configuration" - I did not see any custom board target options that I could use to build configuration for this sample for my Acconeer xm126 module, so I decided to create a new board by clicking on "Create new board".

    This time I was able to enter, under "Board name", the name: "xm126" and other required data, as follows:

    Board Name: xm126

    Description: Acconeer xm126 module

    Vendor: Acconeer

    SoC: nRF52840-Q1AA

    Board Root: c:\Acconeer_SDK_v1_10\Accconeer_xm126_a121-v1_10_0_(1)\xm126

    and I clicked on "Create Board".

    After I clicked "Create Board", I saw the message: "Board xm126 has been created at: c:\Acconeer_SDK_v1_10\acconeer_xm126_a121-v1_10_0_(1)\xm126 and I was able to verify that the board xm126 has been created on my PC in the directory: c:\Acconeer_SDK_v1_10\acconeer_xm126_a121-v1_10_0_(1)\xm126\boards\acconeer\xm126

    as shown on the attached Screnshot_1.

    I then tried to build configuration for the Acconeer example: "example_control_helper" for my newly created board: xm126, using the following west build command:

    west build -b xm126 -d c:\Acconeer\builds\example_control_helper\build

    but the following error came up:

    "No board named 'xm126' found. Please choose one of the following boards: ...

    - as shown on the attached Screenshot_2.

    and the message:

    CMake Error at: c:/ncs/v2.9.1/Zephyr/cmake/modules/boards.cmake:228 (message): Invalid board; see above.

    -as shown on the attached Screenshot_3.

    So, despite the new board: xm126 having been created in the folder: c:\Acconeer_SDK_v1_10\acconeer_xm126_a121-v1_10_0_(1)\xm126\boards\xm126\acconeer\xm126 - the west build command generated Error Message: "No board named 'xm126' found".

    How can I overcome this problem to be able to successfully build configuration for the Acconeer example: "example_control_helper" for my newly created board: xm126 ?

    Best Regards,

    JM 

Children
No Data
Related