You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, there are test data files which are fixed and, with the developement going on with symbiflow-arch-defs, prjxray, etc., these data files are becoming obsolete (and will become obsolete) and unsuited for testing purposes.
The problem is that there is a circular dependency between fasm2bels and symbiflow-arch-defs, for which a set of features might change both in prjxray-db, and the FASM files in the tests do not reflect the changes in the DB, hence being unsuited for testing anymore.
Possible solutions
[TODO]
The text was updated successfully, but these errors were encountered:
One potential solution we discussed adding tarball'd bitstreams generated from Vivado as the source of truth to break the circular dependency. So fasm2bels would have the "truth" bitstreams, generate FASM from those, and output verilog to be checked.
Problem statement
Currently, there are test data files which are fixed and, with the developement going on with symbiflow-arch-defs, prjxray, etc., these data files are becoming obsolete (and will become obsolete) and unsuited for testing purposes.
The problem is that there is a circular dependency between fasm2bels and symbiflow-arch-defs, for which a set of features might change both in prjxray-db, and the FASM files in the tests do not reflect the changes in the DB, hence being unsuited for testing anymore.
Possible solutions
[TODO]
The text was updated successfully, but these errors were encountered: