Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Verify Setup issue #697

Open
victobui opened this issue Nov 8, 2024 · 0 comments
Open

Verify Setup issue #697

victobui opened this issue Nov 8, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@victobui
Copy link

victobui commented Nov 8, 2024

I am new to this I ahve installed the vscode exetension with all dependencies.
But when I verify setup it says there are errors in the checks, but shows me that all have passed.


Checking general configuration (https://terostechnology.github.io/terosHDLdoc/docs/category/installation-checklist)
❌ Some checks failed ❌


⊙ Checking make. This tool is used to run some external tools. Current configured installation path: ""
🔎 Searching for the binary "make" in the system path
✅ make Found in the system path using the command: "make --version"
🎉 The make installation path is correctly configured.

⊙ Checking Python installation. Configured installation path: ""
✅ Python was found in the path "python". Tried to find it using the command: "python -c "import sys; check_version = sys.version_info > (3,0); exit(0) if check_version == True else exit(-1)""
🎉 Python installation path is correctly configured.

⊙ Checking Python dependencies. Current configured installation path: ""
🎉 vunit found.
🎉 edalize found.
🎉 cocotb (optional) found.
🎉 vsg (optional) found.


Checking Linter configuration (https://terostechnology.github.io/terosHDLdoc/docs/guides/linter)
🎉 Correctly configured 🎉🎉


⊙ Linter errors for VHDL is disabled. Skipping configuration check.

⊙ Checking linter errors with modelsim for Verilog/SV. Current configured installation path: System path
🔎 Searching for the binary "Modelsim" in the system path
✅ Modelsim Found in the system path using the command: "vlog -version"
🎉 The linter installation path is correctly configured.

⊙ Checking linter style with vsg for VHDL. Current configured installation path: System path
🔎 Searching for the binary "Vsg" in the system path
✅ Vsg Found in the system path using the command: "vsg --version"
🎉 The linter installation path is correctly configured.

⊙ Linter style for Verilog/SV is disabled. Skipping configuration check.


Checking External Tool Configuration (https://terostechnology.github.io/terosHDLdoc/docs/external_tools/)
🎉 Correctly configured 🎉🎉


⊙ Selected external tool: GHDL. Installation path: ""
🔎 Searching for the binary "ghdl" in the system path
✅ ghdl Found in the system path using the command: "ghdl --version"
🎉 The GHDL installation path is correctly configured.

⊙ Execution mode: CMD. The tool will be executend in the command line.

⊙ Waveform viewer: TOOL. Built-in tool waveform viewer will be opened after the simulation if it is available.


Checking Formatter configuration (https://terostechnology.github.io/terosHDLdoc/docs/guides/formatter)
🎉 Correctly configured 🎉🎉


⊙ Checking formatter standalone for VHDL.
The formatter is built into TerosHDL. Skipping configuration check.
🎉 The linter installation path is correctly configured.

⊙ Checking formatter istyle for Verilog/SV.
The formatter is built into TerosHDL. Skipping configuration check.
🎉 The linter installation path is correctly configured.


Checking Schematic configuration (https://terostechnology.github.io/terosHDLdoc/docs/guides/schematic_viewer/installation)
🎉 Correctly configured 🎉🎉


⊙ Selected backend: yowasp with installation path: "". This backend doesn't support VHDL files.
🔎 Searching for the binary "yowasp" in the system path
✅ yowasp Found in the system path using the command: "yowasp-yosys --version"
🎉 The Schematic Backend installation path is correctly configured.

Could someone explain to me if there are skipped checks that are causing errors.

@victobui victobui added the bug Something isn't working label Nov 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant