Honored Contributor
Honored ContributorHi Josy,
--- Quote Start --- Unfortunately I tend to 'augment' my main library on almost a daily basis. So it would be nice to automate ModelSim a bit. --- Quote End --- Tcl is definitely the way to go to automating Modelsim. --- Quote Start --- I 'grew up' with MaxPlusII and Quartus, at first without the II and I have a hard time separating. --- Quote End --- I did too. Having to manually create waveforms in the the Max+PlusII simulator led me to start using Modelsim. I guess you were just more patient than me :) --- Quote Start --- But as you indicate I could easily write the (low-level) code in an external editor, e.g. Sigasi, use ModelSim to do the RTL-simulation, and later integrate it all in Quartus II or Qsys, and as I rarely simulate a top level file,as to my idea one shouldn't have to, I'd be finished. --- Quote End --- I create components in a lib/ folder. Each component has its own folder, and testbench. The testbench can be run via a 'make check' Makefile, so that if I edit a component and break others, I find out reasonably soon ('make check' is run on all testbenches in the lib/ folder). These components can then be used in higher level designs, eg., a Qsys system. I typically include an Avalon-MM BFM in those systems, and then write a basic testbench to check everything is working. All my lib/ code is in VHDL, whereas the Qsys stuff needs to use SystemVerilog ... so Modelsim full-edition is required. I'll write an Avalon-MM BFM in VHDL one of these days ... Cheers, Dave
