Vivado License Error
Nobody has claimed this yet.
- Dominant language
- SystemVerilog
- Stars
- 3.6k
- Forks
- 1.1k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 141
Description
### Description
I am getting the following error when trying to open the project in Vivado using the `make -C $(dirname $(find bazel-out/* -wholename '*synth-vivado/Makefile')) build-gui` command from the OpenTitan FPGA Guide page.
`[Common 17-345] A valid license was not found for feature 'Synthesis' and/or device 'xc7k410t'. Please run the Vivado License Manager for assistance in determining which features and devices are licensed for your system. Resolution: Check the status of your licenses in the Vivado License Manager. For debug help search Xilinx Support for "Licensing FAQ". If you are using a license server, verify that the license server is up and running a version of the xilinx daemon that is compatible with the version of Xilinx software that you are using. Note: Vivado 2021.1 and later versions require upgrading your license server tools to the Flex 11.17.2.0 versions. Please confirm with your license admin that the correct version of the license server tools are installed.`
However, when I open License Manager, the licenses are present:

Could someone please help?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the OpenTitan FPGA Guide command `make -C $(dirname $(find bazel-out/* -wholename '*synth-vivado/Makefile')) build-gui` and the reported Vivado error. Check the Vivado License Manager for the `Synthesis` feature and `xc7k410t` device, then compare those results with the attached license information. Done means identifying why the command rejects the available license or documenting the required licensing setup.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100