VS Code workflow extension with ncs-example-application

RE: VS Code workflow extension with ncs-example-application

Hung Bui — Tue, 03 Oct 2023 11:01:13 GMT

Hi Aloysious,

Please create a new ticket for your question.

Our suggestion if you are getting started with nRF Connect SDK is to go through our course in Nordic Academy:
https://academy.nordicsemi.com/courses/nrf-connect-sdk-fundamentals/

RE: VS Code workflow extension with ncs-example-application

Aloysious Benoy — Tue, 03 Oct 2023 10:16:18 GMT

What is the workflow we should use when working with such the example application using VS code and the connect extension?

RE: VS Code workflow extension with ncs-example-application

nasinn — Wed, 09 Aug 2023 12:16:55 GMT

It builds like that so all good, thanks a lot.

RE: VS Code workflow extension with ncs-example-application

Hung Bui — Tue, 08 Aug 2023 12:55:03 GMT

Hi Nasinn,

I got help from one of our coworker, could you try follow his instruction ?

It is a "workspace" style application (requires a completely separate copy of the SDK to be pulled in).

Here are my steps for a successful build. I think all the steps has to be done by command line, with a toolchain setup.

Open a toolchain manager launched command line window
1. I think a regular command line window would work if the PC already has a manual installation of the SDK
set ZEPHYR_BASE= This is to clear ZEPHYR_BASE
west init -m https://github.com/nrfconnect/ncs-example-application --mr main .(west init the application to the current empty folder)
1. The README of the example application guides you to set it up in a folder named "my_workspace" instead. No difference here.
2. At the end of this, my empty folder now contains one folder named ".west" and another named "ncs-example-application"
west update
cd ncs-example-application\app
west build -b custom_plank

I did start with VS Code, but all I did is get a the nRF Connect terminal window and run cmd to finish step 1 instead of just using the Toolchain Manager

RE: VS Code workflow extension with ncs-example-application

nasinn — Tue, 08 Aug 2023 06:01:47 GMT

Hi Hung Bui,

I used the nRF Connect Desktop on my MacOS to install which then put the latest sdk under /opt/nordic/ncs so that I think is all as it should be.

Thanks for the clarification on the board roots location. It is "good" to hear you also have the same problem once you got the board selected but yeah, I am keen to hear what the deal is with the example template, and if it is recommended to use that or just go with the workspace app structure generated by the extension.

As you suggest my solution so far has been just to use the generated structure as made by the VS Code extension which works very well, I am a big fan 👍 also the dev academy is a great way to start with the NCS, at least for me coming from the SDK 17 etc.

RE: VS Code workflow extension with ncs-example-application

Hung Bui — Mon, 07 Aug 2023 14:29:35 GMT

Hi Nasinn,

Instead of using the guide from Zephyr to install our NCS SDK, have you tried to follow our installtion guide instead ?
https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/installation.html

Our recommendation is to choose the install automatically path. I would assume you can install the nRF Connect for Desktop app on your Operating system (MACOS ?)

I will have to check internally on how this template can be used with VSCode. My understanding is that it's original made to be used with west as in the instruction.

With regarding to board file, you can select where VSCode should look for custom board file by go to File ->Preferences-> Settings-> Extension-> nRF Connect -> Board Roots.
By default VSCode will look inside the app folder to find boards\arm folder. So another option is to copy the arm folder and put it inside app\boards, instead of putting it in the root folder.
However, when I did that and compiled for custom_plank I also got an error about __device_dts_ord_ . I'm checking internally to figure why.

My suggestion is to go with the structure that made by VSCode. It's the minimum structure for simple application. For more advanced application/structure you can check out the "applications" for example asset_tracker_v2 or nrf_desktop .