From 4d1ffe1fb9bdba9a250c9166dec74f756bd587e9 Mon Sep 17 00:00:00 2001 From: Luke Kenneth Casson Leighton Date: Sat, 15 Aug 2020 12:09:02 +0100 Subject: [PATCH] add alu_fsm.py source link --- Documentation/gtkwave_tutorial.mdwn | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/Documentation/gtkwave_tutorial.mdwn b/Documentation/gtkwave_tutorial.mdwn index a45966c55..f9209c3f6 100644 --- a/Documentation/gtkwave_tutorial.mdwn +++ b/Documentation/gtkwave_tutorial.mdwn @@ -1,9 +1,10 @@ # GTKWave improvements -(Originally at ) +* (Originally at ) +* [alu_fsm.py source](https://git.libre-soc.org/?p=soc.git;a=blob;f=src/soc/experiment/alu_fsm.py;h=9668535aedc8e507212906baf679dc37484b8e8d;hb=1d4fa2db3d660510ebeceb650188c6fcf3127fd4#l209) Lately, I've been investigating about generating better GTKWave "save" -files (*.gtkw), from Python. The goal is to ease analysis of traces +files (\*.gtkw), from Python. The goal is to ease analysis of traces generated by unit-tests, and at the same time to better understand the inner working of modules, for which we are writing such tests. -- 2.30.2