Good morning :-)
Le 2014-05-16 05:57, Paul Taylor a écrit :
I started to do essentially the same thing, by hooking up Tcl to GHDL.
Compile VHDL files, rough out a quick scripted testbench. Run the
script. Change the script a bit, run it again. No compilation between
running the scripts. That's about as interactive as I'd want to get.
But then the script is there ready to be expanded on for a complete
testbench. You could of course make it more interactive however, as
you described above.
Now the question is how you interface/hookup.
I don't see the underlying source code of your system,
it makes me very curious :-)
As an example, see the short testbench script here (shown in the
second code box on the page):
http://pdt.github.io/script-tb_uart_tx_ex.html
The idea of scripting a testbench is nice because of the no compiling
between testbench modifications. You can make top level ports readily
available (which is what I've done here), so no need to create an
instance UUT, and no declaring signals and connecting up the UUT. And
you can build in lots of nice features, such as dynamic threads, etc.
You mention convenience with scripting languages, that's essentially
what I was aftero. Scripting testbenches means you get more
flexibility and significantly less typing vs VHDL, making it easier
and quicker to write testbenches.
a Rhino-based JavaScript console would be just awesome :-P
but the question of how to "connect" to the GHDL simulation is still
there.
Thanks for complementing Martin Strubel's post,
YG
_______________________________________________
Ghdl-discuss mailing list
[email protected]
https://mail.gna.org/listinfo/ghdl-discuss
