Failure to build an application for the sample: Bluetooth: Peripheral HR for my board: nRF5340dk_nrf5340

[Jacek Majda]

I tried unsuccessfully to build an application for the sample: Bluetooth: Perpheral HR - that could be found under samples/bluetooth/peripheral_HR , in the Zephyr Tree - using the build target: nrf5340dk_nrf5340_cpuapp_ns, for my board: nRF5340dk_nrf5340.  I am using nRF Connect SDK v2.2.0.

The build process was terminared with the message:

"Configuring incomplete, errors occurred!  FATAL ERROR: command exited with status 1"

I attach a screenshot of the page with all eror messages that showed up during the build process.

How can this problem be overcome?

Regards,

JM

Error messages - 11 January 2023.docx

[Jacek Majda]

Hello,

As advised, I have reinstalled the NCS v2.2.0 and I tried to build an application for the sample: Bluetooth: Peripheral HR , that can be found under: samples/bluetooth/peripheral_HR , in the Zephyr Tree , using the following build target: nrf5340dk_nrf5340_cpuapp_ns , for my board: nrf5340dk_nrf5340.

However, the build process was terminated again with the following error messages: 

"Configuring incomplete, errors occurred! FATAL ERROR: command exited with status 1."

I attach a screenshot of the page with all error messages that showed up during the build process.

How can this problem be overcome?

Am I using the correct build target for this sample?

Should I use one of the following build targets for this sample: nrf5340dk_nrf5340_cpuapp or nrf5340dk_nrf5340_cpunet or yet another build target for this sample?

Regards,

JM

Error Messages 13 January 2023.docx

[Kazi Afroza Sultana]

Peripheral_HR is built for nrf5340dk_nrf5340_cpuapp_ns or nrf5340dk_nrf5340_cpuapp. 

So, your build target is ok. You also get the same error if you try the nrf5340dk_nrf5340_cpuapp as build target?  

[Jacek Majda]

Yes, I am getting the same errors when I try the nrf5340dk_nrf5340_cpuapp , as build target.

I then tried to build a simple sample: "Blinky" for the build target nrf5340dk_nrf5340_cpuapps_ns  , but again unsuccessfully! The error messages that showed up during the build process of the sample" "Blinky" are shown on the attached screenshot.

As I said earlier, I did reinstall NCS v2.2.0 as advised by you, but how can I know if all required files were downloaded and installed successfully on my PC,  as a result of my reinstallation of SDK v2.2.0 ?

Error messages 16-January-2023.docx

[Kazi Afroza Sultana]

Hello,

Have you tried to run the sample using west command from command line tool?

[Jacek Majda]

Hello,

I have not tried to run the sample using west command from command line tool, as I do not use this approach to run the samples on my development kits.

My preferred approach to build and run samples on my DKs is to use the nRF Connect SDK v2.2.0 (or any other version of the nRF Connect SDK) - as I was successfully using this approach in the past year or so.

I just tried (unsuccessfully) to build yet another sample: "Central UART" for my nRF5340 DK, using the following build target: nRF5340dk_nRF5340_cpuapp_ns.

As usual, the build process was  terminated with the same error messages as before. I attach a screenshot of the page with all error messages that showed up during the build process.

Among others, the following error messages highlighted in yellow seem to be important:

"FATAL ERROR: Zephyr/dt-bindings/adc/adc.h : No such file or directory".

7: #include <zephyr/dt-bindings/adc/adc.h>

Compilation terminated.

The same error messages have been shown on the screenshots of error messages dated: 16-January-2023 and 13-January-2023 that I sent you already.

Upon investigation, I found that indeed there is no such subdirectory as: dt-bindings/adc  in the directory : v2.2.0>zephyr  on my PC, that was created (on my PC) when I installed/reinstalled the nRF Connect SDK v2.2.0.

However, I found that the adc folder can be found on my PC under: v2.2.0>zephyr>dts>bindings>adc , as shown on the attached screenshot_2.

However, I can not see the required adc.h file in that adc directory.

Is it a bug of the nRF Connect SDK v2.2.0?

If so, how can it be fixed to allow the developers to build and run the samples like: Blinky, Bluetooth:Peripheral HR and "Central UART" for the nRF5340 DK development kit using the nRF Connect SDK v2.2.0 ?

Regards,

JM

Error Messages - 19-January-2023.docx

Screenshot_2 -19-January-2023.docx

[Kazi Afroza Sultana]

Hello JM,

The reason I suggested to try to run the samples using west command to know if the problem occurs only for VScode. if there is no problem in west command then it could be an issue on VScode. You should try this.

However, I will report your issues to the VScode team. 

Thanks.

BR

Kazi