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

I tested this using Windows 10.

Regards,
Sigurd Hellesvik

Thanks Sigurd, but as we've diagnosed issues with nRF Connect specific to versions of macOS with other support tickets, can I ask that you verify on macOS Monterey please? Testing on Windows 10 represents a very different OS environment and doesn't duplicate the test case.

Please see:

https://devzone.nordicsemi.com/f/nordic-q-a/84027/nrf-connect-for-desktop-programmer-v2-2-0-and-heart-rate-monitor-demo

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

Hi

The .vscode folder is generated from VS Code in your workspace root folder.

See What is a VS Code "workspace"?, and the "Single-folder workspaces".

If you first open a workspace in another folder(such as /Users/alan/tmp), a folder /Users/alan/tmp/.vscode should be generated. If you add an application to this workspace, no .vscode folder should be added in the application folder.
Use the "Open Folder..." function to try this.
Does .vscode appear expected if you do this?

Regards,
Sigurd Hellesvik

Hi Sigurd,

If I use Open Folder with an empty folder that I previously create in my workspace folder, I do not get a .vscode file generated.

Folder location 'Test':

Users/XXXXXX/workspace/Test/

For information, I updated to nRF Connect SDK v1.9.1 and had a problem with CMake on launch

I 

I unstalled CMake and then quit VS Code and relaunched it from nRF Connect. It then reinstalled CMake and the issue went away. However as you can see, despite launching the v1.9.1 SDK, the Zephyr installation still points to the v1.9.0 version.

As for the Shell Initialisation conflict with nRF Connect, it appears to be this:

https://nrfconnect.github.io/vscode-nrf-connect/connect/troubleshooting.html#shell-initialization-conflicts-nrf-connect-terminal-profile

I Relaunched VS Code from nRF Connect, and this issue is no longer reported at launch. Neither do I get the 'Bad CMake' error at launch either.

Hi Sigurd,

Any progress please?

I need to see this issue resolved in a timely manner or respectfully I will ask for it to be escalated,

Hi Sigurd,

Any progress please?

I need to see this issue resolved in a timely manner or respectfully I will ask for it to be escalated,

Hi Al

I am sorry about this, but I thought you managed to fix your problem in your last answer.

alwalker said:

I Relaunched VS Code from nRF Connect, and this issue is no longer reported at launch. Neither do I get the 'Bad CMake' error at launch either.

After looking through the post below, I think I am missing the bigger picture.
To avoid further misunderstandings, could you recap your issue?

Regards,
Sigurd Hellesvik

Hi Sigurd,

Some definite progress, however when I launch VS Code with the nRF Connect SDK v1.9.1 in Toolchain Manager I still need to manually change the toolchain etc. to v1.9.1 as it is not set automatically. It would be good if this was set as specified by the selection made in Toolchain Manager.

I can build the bluetooth_remote_template project ok as reported in Terminal:

One the Build is completed, there are no red squiggles under the #include statements in main.c

However a few problems are still reported:

Is there any news on a fix or workaround for this error please?

boards/arm/nrf5340dk_nrf5340/Kconfig.defconfig:62: error: couldn't parse 'default $(dt_chosen_reg_size_hex,$(DT_CHOSEN_Z_CODE_PARTITION))': macro expanded to blank string

Are the other two C syntax errors something that would be fixed by code from the snippets.c file please?

too few arguments in invocation of macro "Z_FOR_LOOP_1"

Hi

alwalker said:

however when I launch VS Code with the nRF Connect SDK v1.9.1 in Toolchain Manager I still need to manually change the toolchain etc. to v1.9.1 as it is not set automatically. It would be good if this was set as specified by the selection made in Toolchain Manager.

The Toolchain Manager does not set the version in VS Code, that is correct.
But is it the same as the previous time you used VS Code?

alwalker said:

Is there any news on a fix or workaround for this error please?

boards/arm/nrf5340dk_nrf5340/Kconfig.defconfig:62: error: couldn't parse 'default $(dt_chosen_reg_size_hex,$(DT_CHOSEN_Z_CODE_PARTITION))': macro expanded to blank string

No, there is not yet any fix for this as far as I know.

For a workaround, you could have a look at the file mentioned and see if you can change something here I guess.

alwalker said:

Are the other two C syntax errors something that would be fixed by code from the snippets.c file please?

too few arguments in invocation of macro "Z_FOR_LOOP_1"

Are you logging as explained in the Logging documentation?

Is the logging error still apparent after you build the project?

Regards,
Sigurd Hellesvik