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
GtkWave can display signals values as ASCII. What if litescope uses this option to add a text translation of any signal ?
I don't know if it's possible but Litex could generate analyzer.csv with FSM states names. Then litescope would add "virtual signals" with ASCII translation of FSM states.
We could also add a configuration file to litescope with dictionaries of value:name for any signal.
During simulations Migen already does this for FSM:
The text was updated successfully, but these errors were encountered:
GtkWave can display signals values as ASCII. What if litescope uses this option to add a text translation of any signal ?
I don't know if it's possible but Litex could generate analyzer.csv with FSM states names. Then litescope would add "virtual signals" with ASCII translation of FSM states.
We could also add a configuration file to litescope with dictionaries of value:name for any signal.
During simulations Migen already does this for FSM:
The text was updated successfully, but these errors were encountered: