Skip to content

Update the vqm2blif parser in order to add support for Stratix 10 and Agliex vqm files #1931

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

Closed
kimiatkh opened this issue Dec 5, 2021 · 2 comments
Labels

Comments

@kimiatkh
Copy link
Contributor

kimiatkh commented Dec 5, 2021

The vqm2blif parser grammar is defined based on the vqm files dumped for Stratix IV. The vqm files generated by the new version of Quartus Prime targeting Stratix 10 and Agilex have subtle differences compared to the older versions that causes them not to fit into the currently defined grammar. By making small modifications to the grammar, the parser can support both the old and new versions of the vqm file.

Proposed Behaviour

The parser should be able to parse both versions of the vqm files.

Current Behaviour

The vqm files dumped for Stratix 10 and Agliex are being marked as invalid by the parser.

Possible Solution

The flex and yacc files available in the libvqm directory define the grammar for the vqm file. By making small modifications to these two files the parser can support both versions of the vqm file.

Context

The vqm2blif tool is a part of the Titan flow. In order to add support for Stratix 10 and Agilex in the Titan flow, the vqm files generated by Quartus targeting these two devices have to successfully go through the vqm2blif tool.

Copy link

This issue has been inactive for a year and has been marked as stale. It will be closed in 15 days if it continues to be stale. If you believe this is still an issue, please add a comment.

@github-actions github-actions bot added the Stale label May 17, 2025
Copy link

github-actions bot commented Jun 1, 2025

This issue has been marked stale for 15 days and has been automatically closed.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant