nrfconnect vscode extension problems with "Add Build Configuration" wizard and "Actions" view

[stefanino]

Hi,

running the latest nrfconnect vscode extension (v2024.9.31) the "Add configuration wizard" comes up and stay blank. Additionally, the Actions view is also empty, while its progress indicator keeps running.

 

Rolling back to v2024.7.13 the build configuration is OK, yet the Actions view is still empty and loading indefinitely.

Rolling back even more the build wizard seems good, while Actions always blank and loading (so maybe these are separate issues)

I'm running an Ubuntu devcontainer in vscode 1.93.0 on Ubuntu 22.04.4 LTS host.

Let me know of any other detail that can help in troubleshooting

[zsn]

I have the same issue exactly, when I try to add a build config, i can only see a blank page for build configs.

but if i click to another project's build config which is already created, i can see the action buttons and build files even though i have the missing compile_commands.json error.

zephyr = v3.7-branch

nrfsdk = v2.8-branch

BTW, when i was installing the nrf extensions, I got this error.

[zsn]

just an update, i rolled back to nRF Connect SDK v2.6.99-cs2-branch, zephyr v3.6-branch and disabled the kconfig extension, and now everything is working as expected. 

Could it be some compatibility issue between zephyr, nrf sdk and exntesions?

[stefanino]

Hi dejans,

I used the following

- nrf SDK 2.7.0

- Zephyr 3.7 (actually 3.7.99 which is the rolling development main branch, i.e. no release tag)

[stefanino]

Hi nunofrd ,

not finding SOC seems to be a common theme between mine and your issue. Does your extension report the same error as mine? 

[nunofrd]

Hi Stefanino,

Yes, both extension modules - "nRF Connect for VS Code" and nRF Device Tree - report that.

I've also shared the logs.

[dejans]

Hi,

This seems to be related to the Zephyr version used. What is expected to be working is when you use tagged NCS versions. The extension has been mainly tested to be working with released NCS versions and those have been proved to work only with just certain Zephyr versions. 

Best regards,
Dejan

[stefanino]

Can you please advise a released tag zephyr version (from NCS I guess) that you think should work so I can give it a try and see if I can reproduce the bug or not?