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
This would make the resulting graph generated by dot more readable and the FSM fully documented.
I can certainly post-process the .kiss2 files but I guess Yosys offers a more elegant solution.
I am aware that this might not be possible given that the string representation of the states might not be passed to Yosys's internal format by the HDL frontend.
BTW: is there a way to include the input FSM inputs and outputs name in the generated .kiss2 file?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I use SystemVerilog enums to define the states of my FSMs something like
And I use the following to extract the FSM into a
.kiss2
fileI was wondering if there is a simple way to preserve FSM state names while exporting FSMs to a
.kiss2
file assuming no recoding. Instead ofI would like to have something like
This would make the resulting graph generated by
dot
more readable and the FSM fully documented.I can certainly post-process the
.kiss2
files but I guess Yosys offers a more elegant solution.I am aware that this might not be possible given that the string representation of the states might not be passed to Yosys's internal format by the HDL frontend.
BTW: is there a way to include the input FSM inputs and outputs name in the generated
.kiss2
file?Beta Was this translation helpful? Give feedback.
All reactions