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

[alwalker]

I am working from this video:

https://webinars.nordicsemi.com/developing-bluetooth-low-energy-6

Which nRF5340-DK build configuration should I use please?

• nrff5340dk_nrf5340_cpuapp
• nrff5340dk_nrf5340_cpuapp_ns
• nrff5340dk_nrf5340_cpunet

I've downloaded the source files and manually put the folders named 'bluetooth_remote' and 'bluetooth_remote_template' in my macOS workspace folder.

I add the 'bluetooth_remote_template' folder as a new application into VS Code, immediately I'm asked if I want to change from the current v1.9.0 version of the nRF Connect SDK. I assume that I should be working with the latest version, so confirm that I don't want to change. When I then open the project in Explorer and look at main.c I see the following Includes underlined with red squiggles.

main.c

#include <zephyr.h>
#include <logging/log.h>
#include <dk_buttons_and_leds.h>
#include "remote.h"

The same is true for the Includes in remote.c and remote.h:

remote.c
  
#include "remote.h"
    
remote.h
   
#include <zephyr.h>
#include <logging/log.h>
 
What do I need to do to provide the paths to these header files please?

[Sigurd Hellesvik]

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

[alwalker]

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:

[Sigurd Hellesvik]

Hi

After doing some research, I found that the error

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

have been spotted on MacOS VS Code before. I have reported this to our developers as a bug.

Thank you for the report. If I find a workaround, I will let you know.
And hopefully this will be fixed in a later update of our extension.

EDIT, added the following:

alwalker said:

Bad CMake executable "". Is it installed or settings contain the correct path (cmake.cmakePath)?

I think out extension does some configuration that is dependent of the build folders. Therefore, some error messages might appear before the build, but should disappear after your project has a build folder. My guess is that the cmake path error is of this type.

Regards,
Sigurd Hellesvik

[alwalker]

Hi Sigurd, any thoughts on the JSON file apparently being absent when using a sample project such as blinky please?

[Sigurd Hellesvik]

Hi Alan

I guess this JSON file is a configuration overlay file local for your project.
When I create an application from sample using using VS Code, I am not able to see this file.
The file is generated if you try to configure intellisense manually using VS Code .

Regards,
Sigurd Hellesvik

[alwalker]

Hi Sigurd, 

Thanks for the confirmation, if you repeat the example I give at the start of this thread using the bluetooth_remote_template example per the Nordic video, do you see the JSON file being created please?

[alwalker]

Hi Sigurd,

Any progress on resolving this issue please?

[Sigurd Hellesvik]

Hi

After building bluetooth_remote_template in v1.9.1 on VS Studio Code, no folder named .vscode can be found in my project folder.

Regards,
Sigurd Hellesvik

[alwalker]

Hi Sigurd, are you using macOS Monterey? If not which OS are you using please?

[Sigurd Hellesvik]

Hi

I tested this using Windows 10.

Regards,
Sigurd Hellesvik

[alwalker]

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

[Sigurd Hellesvik]

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