Vivado as a tool for linting is not properly detected in Windows environment

[sominlee74]

In windows environemt, Vivado is not detectd well at the July 10 in 2025.

Here is the detail environment.

• Windows 11 64bit (Home edtition, verstion 24H2), (Korean language_
• Vivado 2024.2 (64bits)
• VSCode 1.102.0
• TerosHDL (7.0.1, 7.0.3, and 7.0.5): I tried 7.0.5 which I downloaded directly from the github. And the results are same fails to detect vivado.

I know the same issue was already submitted and closed, but this error seems to be not fixed yet. I also tried to run settings64.bat, and others, but they didn't work so I create this issue. (Previous issue: https://github.com/TerosTechnology/vscode-terosHDL/issues/715 )

Here is the message capture image from terosHDL "Verify Setup" in VSCode.

Same as the experience of @ht145 and @cezchitos, in the command prompt, vivado -version works well.

Here is the Linter settings in terosHDL

This the Tools configuration. As you find, the path to vivado binary for windows version is C:\Xilins\Vivado\2024.2\bin

And for CLI, we can find vivado.bat in window version as shown in the below image.

c.f) Interestingly, modelsim altera version for windows OS (32bit) is properly detected when I choose Modelsim.

[toine512]

Hi. That fails but the linting process with Vivado actually works when you save a file.

[iva2k-asic]

I noticed that "Verify Setup" ignores PATH and ignores Vivado path in Tools > Vivado, when the tool path is set in the project (which I was not aware of).

But to shoot itself in the foot, even when the path is set correctly, it tries to run "vivado.exe" in the path set by project or global settings, and "vivado.exe" is not present (only "vivado" without extension (bash script) and "vivado.bat" (windows script) are the executables found in .../Vivado/bin).

BTW, there is "vivado.exe" in ".../Vivado/bin/unwrapped/win64.o", but setting path to it is not working either.

So this problem on Windows is multi-faceted:

1. Ignores PATH and Vivado path in setup when Project setting override it
2. Tries to run vivado.exe instead of vivado.bat (or .../Vivado/bin/vivado.exe instead of .../Vivado/bin/unwrapped/win64.o/vivado.exe)

[cezarbontas333]

I noticed that "Verify Setup" ignores PATH and ignores Vivado path in Tools > Vivado, when the tool path is set in the project (which I was not aware of).

But to shoot itself in the foot, even when the path is set correctly, it tries to run "vivado.exe" in the path set by project or global settings, and "vivado.exe" is not present (only "vivado" without extension (bash script) and "vivado.bat" (windows script) are the executables found in .../Vivado/bin).

BTW, there is "vivado.exe" in ".../Vivado/bin/unwrapped/win64.o", but setting path to it is not working either.

So this problem on Windows is multi-faceted:

1. Ignores PATH and Vivado path in setup when Project setting override it

2. Tries to run vivado.exe instead of vivado.bat (or .../Vivado/bin/vivado.exe instead of .../Vivado/bin/unwrapped/win64.o/vivado.exe)

Yeah, tested setting the path to ...\Vivado\bin\unwrapped\win64.o\ and it seems that it doesn't really do anything. I thought maybe double backslashes will work, but nope, not that either, so it seems that this issue persists for now. Maybe there's something we're missing, do all other linters work fine?