We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Most of the 1/0 choices in https://github.com/SymbiFlow/prjuray-db/blob/master/zynqusp/segbits_clem.db use .V1/.V0 to distinguish value possibilities.
.V1
.V0
e.g.
CLEM.ABCDFF.CEUSED.V0 !14_07 CLEM.ABCDFF.CEUSED.V1 14_07 CLEM.ABCDFF.CLKINV.V0 !08_19 CLEM.ABCDFF.CLKINV.V1 08_19 CLEM.AFF.INIT.V0 12_02 CLEM.AFF.INIT.V1 !12_02
but WA[789]USED seems to be an exception:
CLEM.WA7USED.0 !08_23 CLEM.WA7USED.1 08_23 CLEM.WA8USED.0 !11_22 CLEM.WA8USED.1 11_22 CLEM.WA9USED.0 !09_22 CLEM.WA9USED.1 09_22
It would simplify things generating/parsing FASM if one convention could be established here (I personally don't mind either way.)
The text was updated successfully, but these errors were encountered:
This is a bug, I"ll submit a fix today.
Sorry, something went wrong.
Merge pull request f4pga#9 from litghost/add_travis
eb0341b
Add initial Travis CI configuration.
Successfully merging a pull request may close this issue.
Most of the 1/0 choices in https://github.com/SymbiFlow/prjuray-db/blob/master/zynqusp/segbits_clem.db use
.V1
/.V0
to distinguish value possibilities.e.g.
but WA[789]USED seems to be an exception:
It would simplify things generating/parsing FASM if one convention could be established here (I personally don't mind either way.)
The text was updated successfully, but these errors were encountered: