Problem getting started making a build configuration in nrf Connect Extension for VS code

RE: Problem getting started making a build configuration in nrf Connect Extension for VS code

Marte Myrvold — Mon, 14 Feb 2022 07:13:55 GMT

Hi,

I am glad to hear that 1.8.0 is working in VS Code now!

[quote user="saul.magnusson"]As for my other question regarding connecting the nrf52840 dongle to VS code, I realize that it doesn't connect, so I guess VS code connects through the SWD interface somehow on the other boards.[/quote]

The VS Code extension uses nrfjprog to enumerate devices for the connected devices list. Because of this, Dongle and Thingy are not supported at the moment. Hopefully support for this will be added in the future, but until then the solution is to program the device separately, as you did.

Best regards,

Marte

RE: Problem getting started making a build configuration in nrf Connect Extension for VS code

saul.magnusson — Sun, 13 Feb 2022 20:27:02 GMT

As for my other question regarding connecting the nrf52840 dongle to VS code, I realize that it doesn't connect, so I guess VS code connects through the SWD interface somehow on the other boards. I succesfully put the hex file for blinky onto the dongle by using the programmer. You can consider my ticket closed, unless there are any more details you'd like to know.

RE: Problem getting started making a build configuration in nrf Connect Extension for VS code

saul.magnusson — Sat, 12 Feb 2022 19:55:56 GMT

Ok. I deleted the 1.8.0 folder and re-installed everything and now 1.8.0 is now working. I believe my problem was that I did not have Python3 installed at the time I installed 1.8.0 and so west didn`t initiate properly.

RE: Problem getting started making a build configuration in nrf Connect Extension for VS code

saul.magnusson — Fri, 11 Feb 2022 23:20:44 GMT

Thanks Marte, for your assistance. I have a few things to report. You are indeed right that it seems West was not initialized. When I opened a terminal from the toolchain manager and navigated to my application file and ran "west init" and then "west update" I was then able to build the application, but it then ran into errors of a different type. So it seems you're on the right track.

Also, I tried installing the 1.7.1 toolchain and everything works fine for building an application with that version of the toolchain. However my nrf52840 doesn't show up in the Connected Devices window even though I have it connected through the COM port in VS code, and it is pulsing red. I can open a different ticket for that issue if you like.

Of the fixes you suggested, I don't think it is fix 3 since 1.7.1 works fine. I'm going to try fix 4, building from the command line, and I can report back after I've completed that. And I tried fix 5 re-installing the toolchain and updating the sdk and that did not work.

Thanks again for your assistance.

Here is my NRF connect error report from before I installed 1.7.1 attached.

devzone.nordicsemi.com/.../Nordic-Support-Information.docx

RE: Problem getting started making a build configuration in nrf Connect Extension for VS code

Marte Myrvold — Thu, 10 Feb 2022 10:01:35 GMT

Hi,

From the west error you get, west is not initialized, which is why build is not a valid choice. If you were to open a terminal and build on command line with "west build ..." in your application folder, c:\Users\saulm\ncs\apps\blinky, then it would make sense that you are getting this error, since ncs\apps\blinky is not a west folder. However, when building in VS Code, either when when adding the build configuration or by selecting 'Build' under 'Actions', this should not be an issue, as the nRF Connect extension should fix this.

There are some things you can check.

Go to Settings > Workspace > Extensions > nRF Connect. Make sure that your blinky application is added to Applications there. Additionally, can you share what the Toolchain and Topdir settings are set to?

You can also try some of the fixes in the guide Common fixes for nRF Connect SDK build problems. Specifically fixes number 3, 4 and 5. For number 4, using the command line, you must test this in an existing sample inside either nrf or zephyr, as you will not be able to use west build from command line in your sample folder. As for number 6, environment variables, if your toolchain in VS Code is set to the toolchain folder of the Toolchain Manager installation, you do not need to add the environment variables to your path.

Can you also generate support information and upload it here? Open command palette (ctrl+shift+p or View > Command Palette) and write nRF Connect: Generate support information. When you select this the information should be generated in the output terminal windows. You can copy it and upload it here with Insert > Code, and then paste it there.

Best regards,

Marte

RE: Problem getting started making a build configuration in nrf Connect Extension for VS code

saul.magnusson — Thu, 10 Feb 2022 00:39:59 GMT

Hi Marte,

I have done so, and I did just try again with another install of everything, this time following the order of installation as shown in the video. Again I get the same error as above when I try to add a build configuration to my application. Your advice on the steps I could take to troubleshoot the problem would be appreciated.

RE: Problem getting started making a build configuration in nrf Connect Extension for VS code

Marte Myrvold — Wed, 09 Feb 2022 09:32:56 GMT

Hi,

Have you set nRF Connect SDK version and nRF Connect Toolchain in Quick Setup?

Please see the nRF Connect extensions for VS Code Getting started guide and make sure you do all the steps.

Best regards,

Marte