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,

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

[Kazi Afroza Sultana]

Hello JM,

You can try to do west update from nRF Connet profile on the VS Code terminal. From there you can go to the SDK directory (parent directory of Zephyr and nrf) and write this command: 

west update

[Jacek Majda]

Hello Kazi,

As advised by you, I tried today to build the "Blinky" sample using west command: "west build" , but without success.

The following error messages showed up:

"Fatal Error, Errors occurred! ModuleNotFoundError: No module named 'jinja2'.  CMake Error at: tools/CmakeLists.txt:161 (message):File generation failed"     I attach the screenshot of these errors in the file: West Build Error - 27-January-2023.

I then did west update from nRF Connect on the VS Code terminal, as advised. I attach a file: "West Update from nRF Connect -27-January-2023" that shows the final messages of that activity.

I then rebooted my PC and I tried to build a simple application/sample: "Blinky" for my nRF9160 DK , but unfortunately, the same errors as in the past came up, namely:

"Fatal Error: Zephyr/dt-bindings/adc/adc.h: no such file or directory.

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

compilation terminated".

I attach a screenshot of these errors in the file: Fatal Error 27-January_2023".

Am I the only person who is experiencing this problem?

West Build Error 27-January-2023.docx

West Update from nRF Connect 27-January-2023.docx

Fatal Error-27-January-2023.docx

[Kazi Afroza Sultana]

Hello,

Please insert the error information here as code not in word documents. It is difficult to read the screenshot from word document.