Implementing 'Developing Bluetooth Low Energy products using nRF Connect' video on nRF5340-DK

Hi

From the Terminal log you sent, the projetct actually builds sucessfully, and you should be able to flash it to the device if you want.

After you do the pristine build and get these errors, try to restart VS Code and see if the errors still persists in the existing project?

In your settings, I see you use clang as the compiler used for intellij. Try to set the ncs gnuarmemb as this instead.
It should be located something like. ""/opt/ncs/v1.9.0/toolchain/opt/bin/arm-none-eabi-gcc"

Does any of these suggestings fix your issue?

Regards,
Sigurd Hellesvik

Thanks Sigurd, I've done as you suggested and restarted VS Code, an I still get 10 out of 11 errors as it does at least find remote.h header file in the project folder

How do I set the compiler to arm-none-eabi-gcc instead please? It's located here:

Hi

When you run VS Code, do you open it from the nRF Connect for Desktop Toolchain Manager app?

I realise that the editing of the includePath and compilerPath likely is the wrong aproach to solving this problem.
Remove the changes you made to these, to get the original issue.

The nRF Connect for VS Code extension should be able to configure intelliSense automatically.

Since none of my previous suggestions have worked so far, I will ask our developers for this extension for assistance in the case.
They will need the following information generated by VS Code:

1. Generate support information:

2. C/C++ Log diagnostics:

Paste the generated information into two different files(.txt), remove information you do not want to share, and upload here.

Regards,
Sigurd Hellesvik

HI Sigurd,

Yes, i always launch VS code from the Toolchain Manager app in nRF Connect for Desktop.

Thanks very much, but following your example doesn't produce the same result, what am I missing please?

Hi

You need to open the menu (Ctrl+P), and then type in ">" first. This way, VS Code lets you execte commands, either from itself or from extensions.

Regards,
Sigurd Hellesvik

Thanks very much Sigurd, please find requested files attached.

Hi

How does your c_cpp_properties.json look now?

According to the diagnostics your setup sees "IntelliSense Mode: macos-clang-x64" which is wrong. ("IntelliSense Mode: macos-gcc-arm" is expected) This could be because the file is not opened, the build is not selected, or maybe the intellisense extension was installed or enabled later then our extension. If the latter is true a simple quit and restart would solve the problem.

Regards,
Sigurd Hellesvik

Hi

How does your c_cpp_properties.json look now?

According to the diagnostics your setup sees "IntelliSense Mode: macos-clang-x64" which is wrong. ("IntelliSense Mode: macos-gcc-arm" is expected) This could be because the file is not opened, the build is not selected, or maybe the intellisense extension was installed or enabled later then our extension. If the latter is true a simple quit and restart would solve the problem.

Regards,
Sigurd Hellesvik

Hi Sigurd,

Thanks very much, please see attached text file showing c_app_properties.json both before and after quitting and restarting nRF Connect for Desktop Toolchain Manager and VS Code. As you will see, there is no difference in the file contents.

Is this file settings you have set yourself, or is it automatically created?

Regards,
Sigurd Hellesvik

Thanks Sigurd, it’s all automatically created, I have not edited any of the filepaths.

Hi

If it is possible, I think the easiest way to fix this issue would be to remove all your VS Code configurations (delete the VS Code config directory), and reinstall VS Code and its extensions.

I would like to repeat that despite these error messages, your build looks fine, and I think you should be able to use VS code for nRF Connect despite them.

Regards,
Sigurd Hellesvik

Hi Sigurd,

Thanks for the suggestion, but I've just done that to resolve another ticket:

https://devzone.nordicsemi.com/f/nordic-q-a/84319/nrf-connect-for-vs-code-youtube-videos-having-problems-with-include-paths-and-kconfig-in-mac-os

In this case it was of significantly greater scope as I upgraded to macOS Monterey and deleted (including all hidden files) and reinstalled nRF Connect, the toolchain and SDK, and VS Code to ensure I was running the latest code in all instances.

So I don't think that's the issue, rather it's how nRF Connect is configuring VS Code and that the correct filepaths for the compiler etc. are not being specified.

All I've done is follow the Nordic instructions, so with respect I feel that the issue lies with nRF Connect's configuration of VS Code, and to suggest I just live with the error messages isn't something I can accept for commercial product development.