Every start of VS Code the settings.json will get wrong GPU value

Technical Support
, ,
1

Hallo zusammen,
bei jeden neuen Start von VS Code wird der Wert “torizon_gpu” in allen settings.json Files auf -vivante gesetzt.
Wir nutzen einen imx8m, welcher jedoch -imx8 benötigt.
Ich habe es auch schon in der Exentsion Einstellung gesetzt, tortzdem wird es immer wieder überschrieben.
image

Danke für euere Hilfe
@kevin.tx

Deepl’s translation to English:

“with every new start of VS Code the value “torizon_gpu” is set to -vivante in all settings.json files.
We use an imx8m, which requires -imx8.
I have already set it in the exentsion setting, but it is always overwritten.
[picture]
Thanks for your help”

2

Hi @tf_hosenso.de

I ran a quick test here and could not reproduce this. Can you share more details? What versions of VSCode and the Torizon extension are you using? What is your project configuration? What templates?

Drew

3

Hi,
you could install a fresh new template multi project with the last preview version of your extension.
Put in a .Net Blazor and DotNetConsole App.
I use last Version of VS Code and the big Devboard with IMX8

That is Kevin has seen this behaviour 14 days ago.

Tomas

4

Hmm. Even with that project configuration I do not see this behavior. I am on Ubuntu. Which host platform are you running?

Drew

5

i also use ubuntu 22.04

6

Hi @tf_hosenso.de

I did find that if I have a board attached to the extension, and set as default, it will update the workspace settings.json to match. It does not update the individual projects though. I’ll follow up with the dev team on that.

Could that be your scenario?

7

@drew.tx
Yes, that is possible. The GPU still remains correct in the workspace

Tomas

8

OK. I spoke to one of our VSCode experts and he confirmed this is the correct behavior. When using a multi-container project, the settings in the workspace json file are used. You can open each subproject individually in which case the project-specific setting will be used. It can be a bit confusing if you do it that way but it’s evidently the way workspaces in VSCode behave.

Drew