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
It turns out the _diff_fasm tests were not running bit2fasm with the --verbose flag, meaning that unknown bits generated from Vivado were not reported. When --verbose was added, the result was that the minilitex design reported unknown bits:
prjxray-db should be augmented with the missing bits, and the minilitex design should be used to investigate why these bits are present and not emitted from the symbiflow design.
The text was updated successfully, but these errors were encountered:
@litghost -- Should bit2fasm error with unknown bits these days?
Valid question. I think that might be a good default, with a way to disable the error. For example, during prjxray fuzzing we just want the unknown bits printed, not an error.
It turns out the
_diff_fasm
tests were not runningbit2fasm
with the--verbose
flag, meaning that unknown bits generated from Vivado were not reported. When--verbose
was added, the result was that theminilitex
design reported unknown bits:prjxray-db
should be augmented with the missing bits, and theminilitex
design should be used to investigate why these bits are present and not emitted from thesymbiflow
design.The text was updated successfully, but these errors were encountered: