Unable to change sdk location in workspace after Toolchain update

RE: Unable to change sdk location in workspace after Toolchain update

Michal — Tue, 04 Jul 2023 13:42:18 GMT

Good news!

Looks like everything works as it should in the newest update.

Best regards,

Michal

Michal — Tue, 30 May 2023 14:25:30 GMT

I understand, but I don't have any other fix or a workaround yet.

What you could do is try starting the different NCS versions through the Toolchain Manager instead of changing it directly inside VS Code, like this:

But it won't switch it directly in your VS Code instance.

Best regards,

Michal

Sahu — Fri, 26 May 2023 15:10:52 GMT

But I would like to know how to change into custom sdk dir in latest version.

Sahu — Fri, 26 May 2023 15:09:48 GMT

I didnt restart vcs after downgrading. Now I am able to change sdk successfully

Michal — Fri, 26 May 2023 14:20:16 GMT

Just to be extra sure, did you reload the VS Code after downgrading?

And can you show me a screenshot of the extension version?

Best regards,

Michal

Sahu — Fri, 26 May 2023 14:16:22 GMT

When I clear the topdir on both user and workspace, it takes the default location. So when I change to my desired sdk location,

I see following error:

and on welcome page i see following:

Michal — Fri, 26 May 2023 14:08:11 GMT

What if you clear the setting @id:nrf-connect.topdir (both global and workspace) and try to choose the SDK version again?

Does it change anything?

Best regards,

Michal

Sahu — Fri, 26 May 2023 14:04:17 GMT

The issue exists even with previous version v2023.2.56

Michal — Fri, 26 May 2023 13:56:25 GMT

Hello,

I can confirm and have reported this issue.

A temporary workaround could be to downgrade the VS Code extension "nRF Connect for VS Code" to version v2023.2.56

Also, what happens then your use the Toolchain Manager to start VS Code with a chosen SDK version? Does it work that way?

Best regards,

Michal