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

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

Hung Bui — Mon, 05 Jun 2023 07:31:59 GMT

Hi JM,

I agree. It's just some incompatible issues between Visual Studio Code and the SDK. But luckily Visual Studio Code is not used for building it's the SDK's toolchain does the compiling (ninja, make, west, gcc). VS Code is only the IDE and the interface for configuration.

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

Jacek Majda — Sat, 03 Jun 2023 13:56:34 GMT

Hi Hung,

I can build and flash the application despite the include errors coming up. However, as the include errors do not affect the build process, I am ignoring them.

It is a pity that such errors with VS code resulted in many hours lost by me for unnecessary search for a root of the problem.

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

Hung Bui — Thu, 01 Jun 2023 14:06:20 GMT

Hi Jacek,

Please answer me , can you build the application and flash the application ? Any error when you build ?

If the include error doesn't affect the build process, you can ignore them. As far as I know it's the error with VS code, not the toolchain for building the application.

Have you finished the Nordic Academy NCS fundamental course (not the BLE course) ? https://academy.nordicsemi.com/courses/nrf-connect-sdk-fundamentals/

You don't have to include picture in the .docx file, you can insert the picture directly here in this text box.

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

Jacek Majda — Thu, 01 Jun 2023 13:54:23 GMT

Hi,

I attach a build_log for the sample blefund_less2_exer2_solution that I renamed as blefund_less2_exer2_sol_JM3.

I also attach a list of include errors that came up during the process of building that sample.

After I flashed that sample to my nRF5340 DK, the sample seemed to work OK.

Why are these include errors coming up and how can one eliminate them?

devzone.nordicsemi.com/.../Build_5F00_log-on-1_2D00_June_2D00_2023.docx

devzone.nordicsemi.com/.../Include-errors-on-1_2D00_June_2D00_2023.docx

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

Hung Bui — Wed, 31 May 2023 09:17:19 GMT

Hi,

Please show us the issue when you build the project, not when you just open the project. As I showed you in the last reply.

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

Jacek Majda — Tue, 30 May 2023 15:13:01 GMT

Hi Hung,

I did test the example: peripheral_uart and the build process concluded without errors.

I then tried again to build the sample: blefund_less2_exer2_solution and the build process concluded without errors.

I then introduced some changes to the main.c of the sample blefund_less2_exer2_solutions and the include errors came up again.

So I reversed the changes that I just introduced to the main.c of the sample: blefund_less2_exer2_solution and I tried to make another build of that sample but the include errors came up again (I attach a screenshot of these include errors).

I then tried again to make another build of the sample: peripheral_uart (that was built without any problem 30 minutes earlier) but this time the include errors came up (I attach a screenshot of these include errors).

It seems that by trying to make some changes to the main.c of the sample blefund_less2_exer2_solution, some serious and permanent corruption is introduced to the Visual Studio Code that results in include errors coming up for all samples, despite the fact that the changes that were introduced to the main.c of the sample blefund_less2_exer2_solution were reversed by me.

Are we not supposed to try to introduce any changes to the main.c files of the samples?

devzone.nordicsemi.com/.../Include-erors-when-building-sample-blefund_5F00_less2_5F00_exer2_5F00_solution--on-30_2D00_May_2D00_2023.docx

devzone.nordicsemi.com/.../Include-errors-when-building-sample-peripheral-UART-30_2D00_May_2D00_2023.docx

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

Hung Bui — Tue, 30 May 2023 07:58:57 GMT

Hi JM,

Could you please try to test with the examples we have in the SDK, not the fundamental BLE course ? For example peripheral_uart and peripheral_lbs located in \nrf\samples\bluetooth

In your screenshot it's not the build log, have you tried to build ?
It should look like this:

You may want to try re-install Visual Studio Code and the nRF Connect extension.

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

Jacek Majda — Sat, 27 May 2023 15:07:59 GMT

Hi Hung,

I tried the recommended solution on: How to fix the error "Invalid type definition" - and it worked. The error: "Invalid type definition" no longer comes up on my PC.

However, my previously reported problems with #include errors came up again.

So, I took the following steps to try and eliminate them:

1. I re-installed the SDK v2.3.0 in a new folder c:\Nordic-230-bis\ on my PC

2. I double-checked that the include files are located in the directory: c:\Nordic-230-bis\zephyr\include

3. I double-checked that the nrfxlib folder was located in the directory: c:\Nordic-230-bis\v2.3.0\nrfxlib and that it was not empty.

4. I made sure to tell Visual Studio Code to use the correct toolchain folder after re-installing the SDK v2.3.0 in a new directory.

However, despite taking the above mentioned steps, the #include errors are coming up again on my PC, when I try to build the sample: blefund_less2_exer2_solution, as can be seen on the attached file.

The following #include errors are reported on the attached file:

1. #include errors detected.

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

3. Cannot open source file "syscalls/log_msg.h" (dependency of C:\Nordic-230-bis\v2.3.0\zephyr\samples\bluetooth\zephyr\logging\log.h)

I verified the following:

1. There is no subdirectory: \zephyr\kernel.h in the directory: C:\Nordic-230-bis\v2.3.0\zephyr\samples\bluetooth on my PC.

2. The subdirectory: \zephyr\kernel.h is located in C:\Nordic-230-bis\v2.3.0\zephyr\include directory on my PC.

3. There is no subdirectory: \zephyr\logging\log.h in the directory: C:\Nordic-230-bis\v2.3.0\zephyr\samples\bluetooth on my PC.

4. The subdirectory: \zephyr\logging\log.h is located in C:\Nordic-230-bis\v2.3.0\zephyr\include directory on my PC.

How can these problems be resolved?

devzone.nordicsemi.com/.../Include-errors-for-sample-ble_5F00_less2_5F00_exer2_5F00_solution-on-26_2D00_May_2D00_2023.docx

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

Hung Bui — Tue, 23 May 2023 13:24:28 GMT

Hi JM,

Please clarify if you can build and run the examples ?

If you simply ignore the "Problem" would it still compile ?

Could you try the solution here: How to fix the error "Invalid type definition: Cannot set properties of null (setting 'name')"?

If it doesn't help my suggestion is to remove the SDK and try reinstall it. It may help fix the problem.

Note: You can add image directly to devzone, you don't need to paste it in .docx document

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

Jacek Majda — Tue, 23 May 2023 12:53:36 GMT

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?

devzone.nordicsemi.com/.../Problem-Notification-_2D00_-Invalid-Type-Definition-on-23_2D00_May_2D00_2023.docx

devzone.nordicsemi.com/.../Yaml-Source-File-_2D00_-arm_2C00_sbsa_2D00_uart--on-23_2D00_May_2D00_2023.docx

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

Hung Bui — Mon, 22 May 2023 14:17:53 GMT

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

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

Jacek Majda — Mon, 22 May 2023 13:33:23 GMT

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?

devzone.nordicsemi.com/.../7356.Errors-while-building-a-sample-Lesson2_5F00_exer2_5F00_solution-22_2D00_May_2D00_2023.docx

devzone.nordicsemi.com/.../8836.Errors-while-building-a-sample-Central_5F00_and_5F00_peripheral_5F00_hr-on-22_2D00_May_2D00_2023.docx

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

Jacek Majda — Mon, 22 May 2023 13:30:27 GMT

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 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?

devzone.nordicsemi.com/.../Errors-while-building-a-sample-Lesson2_5F00_exer2_5F00_solution-22_2D00_May_2D00_2023.docx

devzone.nordicsemi.com/.../Errors-while-building-a-sample-Central_5F00_and_5F00_peripheral_5F00_hr-on-22_2D00_May_2D00_2023.docx

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

Hung Bui — Mon, 22 May 2023 11:34:44 GMT

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.