Academy's Bluetooth LE Fundamentals, Lesson6_Exercise1: Problems with #include errors during the build process.

[Jacek Majda]

I successfully completed the original Lesson6_Exercise1, where I used my nRF5340 DK to  run code found in lesson6/blefund_less6_exer1  to make it act as the "Nordic_Beacon" that is to advertise in a scannable, non-connectable mode its name and its manufacturer specific data - while I used my nRF52840 DK to run the sniffer firmware.

Subsequently, I wanted to make some changes in the main.c file of the original firmware obtained from sample: blefund_less6_exer1 to try and simplify the format of the manufacturer specific data - but without success.

When I tried to make another version of the build (build_1) of that sample, I saw a number of #include errors that I could not get rid of.

While investigating why there was a problem with accessing #include files, I found that the subdirectory \v2.2.0\zephyr\include had disappeared from the \v2.2.0\zephyr directory on my PC !!

So I decided to install the latest version of nRF Connect  SDK v2.3.0 in the new directory: c:\Nordic-230 , to replace my existing version of the nRF Connect SDK v2.2.0.

After I installed the latest version of nRF Connect SDK v2.3.0 , I verified that the #include files were present in the c:\Nordic-230\v2.3.0\zephyr\include directory.

I then tried to make another version of the build of the sample: lesson6/blefund_less6_exer1 , but the #include errors were still coming up as before.

So I tried to make another version of the build for another sample: bluetooth:observer but the following two #include errors came up again:

1. #include errors detected based on info provided by the configuration Provider setting. Squiggles are disabled for this translation unit [ln9, Col 1].

2. Cannot open source file "syscall_list.h" (dependency of C:\Nordic-230\v2.3.0\zephyr\samples\bluetooth\zephyr\bluetooth\bluetooth.h

as can be seen on the attached "Screenshot_1 on 19-May-2023".

And line 9 of the main.c file of the sample bluetooth:Observer reads as follows: #include <zephyr/bluetooth/bluetooth.h> as can be seen on the attached "Screenshot_1 on 19-May-2023".

I then verified the following:

1. There is no subdirectory: \bluetooth.h in the directory: C:\Nordic-230\v2.3.0\zephyr\samples\bluetooth\zephyr\bluetooth\ on my PC as can be seen on the attached "Screenshot_2 on 19-May-2023".

2. The subdirectory: \bluetooth.h is located in C:\Nordic-230\v2.3.0\zephyr\include\zephyr\bluetooth\bluetooth.h on my PC but it does not have a reference to the source file "syscall_list.h" as can be seen on the attached "Screenshot_3 on 19-May-2023".

How can these #include errors be eliminated?

JM

Screenshot_1 on 19-May-2023.docx

Screenshot_2 on 19-May-2023.docx

Screenshot_3 on 19-May-2023.docx

[Hung Bui]

Hi Jacek, 

The exercise in Lesson 6 Exercise 1 is the same as Lesson 2 exercise 2 . Do you have any problem compiling the code in Lesson 2 exercise 2 ? 
And they are also based on our sample in \nrf\samples\bluetooth , could you try to build one of the example and see if it work ? 
My suggestion is to erase the build file and start again. Note that when you change the SDK, you need to tell Visual Studio Code to use the correct toolchain folder of the new SDK. 

[Jacek Majda]

Hi Hung,

As advised, I tried to build the sample: Lesson2_Exercise2_solution, but without success: Fatal Error came up.                      I attach a list of all errors that showed up during the process of build of that sample.

I then tried to build another sample: Central_and_peripheral_hr from the directory nrf\samples\bluetooth - but again, without success: Fatal Error came up.  I attach a list of all errors that showed up during the process of build of that sample.

I also made sure to tell Visual Studio Code to use the correct toolchain folder of the new SDK.

What else can I try to overcome these problems?

JM

Errors while building a sample Lesson2_exer2_solution 22-May-2023.docx

Errors while building a sample Central_and_peripheral_hr on 22-May-2023.docx

[Jacek Majda]

Hi Hung,

As advised, I tried to build the sample: Lesson2_Exercise2_solution, but without success: Fatal Error came up.                      I attach a list of all errors that showed up during the process of build of that sample.

I then tried to build another sample: Central_and_peripheral_hr from the directory nrf\samples\bluetooth - but again, without success: Fatal Error came up.  I attach a list of all errors that showed up during the process of build of that sample.

I also made sure to tell Visual Studio Code to use the correct toolchain folder of the new SDK.

What else can I try to overcome these problems?

JM

7356.Errors while building a sample Lesson2_exer2_solution 22-May-2023.docx

8836.Errors while building a sample Central_and_peripheral_hr on 22-May-2023.docx

[Hung Bui]

Hi Jacek, 
It looks like a corrupted installation of nRF Connect SDK to me. 
Could you please check if you have the nrfxlib folder in the SDK ? 

My suggestion is to either click on "Update SDK" in the Toolchain manager app or try to remove the SDK and freshly install it again. Please also try with nRF Connect v2.2

[Jacek Majda]

Hi Hung,

As advised, I checked if I had the nrfxlib folder in the SDK and I found that the nrfxlib folder was shown in the directory: c:\Nordic-230\v2.3.0\ but the nrfxlib folder was empty. Not a single file was in that folder.

So as advised, I clicked on "Update SDK" in the Toolchain manager app and this resulted in nrfxlib folder getting populated  by about 26 entries (some subdirectories and some files) and this has resolved the problems that I was experiencing so far and I was able to build the sample: "blefund_less2_exer2_solution".

However, before I even selected which sample I wanted to use for the build process, the following problem was reported at the bottom of the Visual Studio Code screen:

Problems 1

! arm,sbsa-uart.yaml c:\Nordic-230\v2.3.0\zephyr\dts\bindings\serial  -  Invalid type definition. Cannot set properties of null (setting 'name') [Ln1,Col1].

I attach a screenshot of that problem notification.

I also attach a copy of the Yaml Source File: arm,sbsa-uart.yaml that is located in the directory: c:\Nordic-230\v2.3.0\zephyr\dts\bindings\serial , that is being referred to as problematic in the above mentioned problem notification.

How can this problem be eliminated?

JM

Problem Notification - Invalid Type Definition on 23-May-2023.docx

Yaml Source File - arm,sbsa-uart on 23-May-2023.docx