VS Code extension doesnt change west workspace

[Ahmed Samir]

I have two toolchains and two nrf SDKs installed. v2.4.1 and v2.6.1.

I could change the toolchain used from vs code extension, but I couldn't change the west workspace. It always points to v2.4.1, even when I select the mainfiest file in v2.6.1, it doesn't change.

Here is my folder structure:

I tried to press Manage west workspace -> then select v2.6.1 manifest file, but it doesn't work

My application is out of tree, and not under nrf SDK folder structure.

[donpavlov]

This happened to me, when i created an application inside an already present west workspace. For example you create an example application at the folder <west-workspace>/zephyr/example-app/blinky and then you try to change the toolchain revision or the west manifest, it will fail as it is already inside an initialized workspace of version x. Best you could do create a new location with your application and make sure its not inside the west workspace.

[Ahmed Samir]

my application is out-of-tree, it is not in the zephyr folder structure. I have it on a folder in the D directory while NCS SDK is installed in the default C:\\ncs folder.

[Håkon Alseth]

Can you share more information about your application?

 

Does it include its own west.yml file? Or is it like this, explicitly without a own west.yml?

https://docs.zephyrproject.org/latest/develop/application/index.html#zephyr-freestanding-application

 

Have you deleted all your build-folders within the application, to ensure that this was not built with an older SDK version on a previous occasion?

 

Kind regards,

Håkon

[Ahmed Samir]

The application is without west.yml file.

Yes no building folder exist in the application directory

Here is what I get when I try to select west workspace

I don't see v2.4.1 option, also if I manually open v2.4.1 west.ymll file by Browse.. nothing happens.

This is how my ncs folder looks like

[Håkon Alseth]

Hi,

 

Thanks for explaining. You are now unable to select v2.4.1, as compared to v2.6.1 in the original post.

Could you try to open VS Code, then go to "File -> Open Folder..." and navigate to the wanted NCS version folder, and see if the plugin now selects the correct toolchain/sdk version?

 

Kind regards,

Håkon

[Ahmed Samir]

Hi,

Thanks for the note about adding the SDK folder to VS Code workspace.

Even when I added the two SDK folders to VS code Workspace, still couldn't make the extension to switch between the two sdks. However, I found a workaround.

If I need to select v2.4.1, I have to remove all SDK folders from the VS code workspace, add only v2.4.1 to the VS workspace, and re-initialize the extension. At this point, the extension selects v2.4.1 as the west workspace.

I believe there is a bug or limitation on the extension. I hope you can find a more straightforward solution or a workaround.

[Håkon Alseth]

Hi,

 

I will be sure to pipe this feedback back to the VS Code plugin team.

If your workflow will require switching between versions, I would recommend that you try the "project manager" plugin in vscode. This allows you to open up each ncs installation within an existing vscode window.

 

Kind regards,

Håkon