Custom board VSCode plugin and SDK connect v2.2.0

[lbe]

Hello everyone,

I am having a big problem in defining a custom board using the new VSCode plugin. 

I tried to follow a few tutorials and videos, but the ones I found are outdated (they refer to Segger and SDK V.1.5) and some of the instructions they

give are not valid anymore. I tried to

- create a completely new board using VSCode, but I got a lot of compilation errors that I do not entirely understand

- create a board by using an existing one (NRF52833_DK) as model, just changing names to the board. This compiles, but then I cannot even see a led blinking. I checked with ozone, and I can control leds, so I don't think there is an issue with the hardware

- started from different examples both from zephyr and nordic (zephyr blinky, nordic peripheral uart), but I got nothing.

Is there any official guide I can follow to solve this issue? My board is a very trivial one, and the baby step I would like to realize is to just blink the onboard leds for now....

Thanks in advance for your help!

Lorenzo

[lbe]

Hello everyone,

I was finally able to figure out the problem: for some reason, the reset pin was interfering with the program even if it shouldn't have been activated by the programming....It seems that by default, the NCS on VScode does something with this pin configuration. I was able to have the board work by physically connecting the reset pin to Vdd, and now I can program the board and see the leds blinking.

I would appreciate an explanation of how to avoid this, though, because the suggested workaround of the "nrfjprog --softreset" was not working for me.....

[Priyanka]

Since your build logs are clean, and the VSCode extension looks fine, it doesn't seem to be the problem with VSCode. I will convey this internally and discuss this with the team. I will get back to you with a response soon.