Re: [myhdl-list] Mixing MyHDL-generated source with other code

[Henry G. <he...@ca...>]

On 07/05/15 08:39, Henry Gomersall wrote:
> On 07/05/15 03:19, Christopher Felton wrote:
>>>> >> >I like the simulation possibilities provided by MyHDL.
>>>> >> >@Ben, are you adding Vivado simulator as a cosimulation option to myhdl?
>> >I am fairly sure the isim (ISE/Vivado simulator)
>> >does not support a foreign language interface,
>> >no PLI/VPI.  You can't do Cosimulation as it is
>> >done with all other simulators.
>> >
>> >Henry (@heng) I believe put together a process to
>> >create stimulus files, run the simulation, capture
>> >the outputs, and then read them into the MyHDL and
>> >validate (I think it went like that).  I believe
>> >that is the best you can do with isim.
>> >
>> >The isim Cosimulation is best kept as a standalone
>> >package.  Although I haven't tried it, from Henry's
>> >description it sounds like he has made good progress.
>> >The isim Cosimulation as a standalone package might
>> >make sense (i.e using Henry's approach).
> Yes, I'm using it on a daily basis now for quite serious code - it's now
> pretty stable with a good test suite. In the confines in which I'm using
> it, i'm very pleased with it.
>
> The build chain at the moment is limited to Vivado, but it's not really
> specific to Vivado - the calling interface is written in templated tcl,
> so a similar one (or indeed any other kind of driver script) could be
> written for other simulators.

It also comes with set of utilities for making the stimulus easier (such 
as a random source) and various utilities to verify things like signal 
types (i.e. interface verification).

Cheers,

Henry