On Tue, Oct 12, 2010 at 11:36 AM, Mike Crowe <[email protected]> wrote: > After looking at some of the issues associated with a direct calls to > object code, I've decided to take the approach of spawning an instance > of the target application, then use the vpi interface to communicate > with a shared memory or message queue. Has anyone been down this route > before that is willing to share their experiences? > > Advantages of this approach > "Clean" VPI interface to work with > Less development time > > Disadvantages > More modules to compile and keep track of netlist, ngspice-vpi.o vhdl > executable, ghdl-vpi.o, (greater end user complexity) > Use of less portable data transport engine > OS data transport model probably slower than direct function call. > > Thanks for any insights > Mike
Hi Mike, I've been down that route... And I've actually used POSIX shared memory and CORBA to do the job. Some time ago, I've written an article about the verification environment I've developed during my M.Eng. [1] The article doesn't go in depth about GHDL specific parts... If you want greater details, just let me know. Cheers, -Pascal [1] http://ieeexplore.ieee.org/xpls/abs_all.jsp?isnumber=4683356&arnumber=4683393&count=61&index=36 or http://organact.mine.nu/dokuwiki/_media/mesetudes:mnrc08.pdf?id=mesetudes&cache=cache -- Homepage (http://organact.mine.nu) Debian GNU/Linux (http://www.debian.org) COMunité/LACIME: École de technologie supérieure (http://www.comunite.ca) _______________________________________________ Ghdl-discuss mailing list [email protected] https://mail.gna.org/listinfo/ghdl-discuss
