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 FASM annotations errors are detected late in the flow. A tool to sanity check VPR arch and rrgraph annotations would allow earlier error detection, and cross linking with Verilog blackbox definitions.
Suggested lint passes:
Error if FASM mux definition defines an input that does not exist
Error if FASM mux definition does not an input that is specified in the mux/direct tag
Warning if FASM params definition is missing a parameter defined in the Verilog module
Error if FASM params definition defines a parameter that does not exist in the Verilog module
Error if the bit width of the FASM params definitions does not match the Verilog module parameter width
Error if FASM prefix length does not match num_pb value
Error if FASM annotation generates a FASM tag that does not exist
Error if FASM lut annotation is missing on a class="lut" or subckt=".names" black box.
Error if FASM annotation is illegal (e.g. syntax error)
The text was updated successfully, but these errors were encountered:
@litghost I wonder if this should be under symbiflow-arch-defs (It will definately be useful there...)? I guess this is useful for any VPR architecture.
Currently FASM annotations errors are detected late in the flow. A tool to sanity check VPR arch and rrgraph annotations would allow earlier error detection, and cross linking with Verilog blackbox definitions.
Suggested lint passes:
The text was updated successfully, but these errors were encountered: