Re: [myhdl-list] Developing PLI module for cosimulation with VCS
Brought to you by:
jandecaluwe
From: James L. <rob...@gm...> - 2012-05-11 19:44:21
|
No luck with 0.8 either, I tried cver, icarus, and modelsim. Maybe I'm not compiling it for VCS correctly? All I'm doing is changing cver/myhdl_vpi.c to include "vcs_vpi_user.h" instead of "cv_vpi_user.h", and changing the include path in the Linux makefile to point to the VCS include directory. After that, I just compile the module into a .so and link that into VCS by using the -load myhdl_vpi.so:myhdl_register +vpi options, if anyone if familiar with VCS. On Fri, May 11, 2012 at 3:01 PM, James Lee <rob...@gm...>wrote: > Hi all, > > Thanks for the quick responses. I'm hoping this gets placed into the same > email chain, since I foolishly forgot to subscribe to the mailing list > before sending my previous post. > > I tried compiling both the icarus and cver versions of the PLI modules and > linking them in as shared objects, but the simulation seems to hang. I can > confirm the callbacks are being executed by placing some debug print > statements in myhdl_vpi.c, but when I dump the VCD, no signals are > generated, so I'm convinced the VPI routines are not communicating signals > correctly between the Python and the RTL. > > Previous to attempting to use VCS, I used iverilog for cosimulation > successfully. So I am using all the same code with the only modifications > being how the simulator is called on the Python side to create the > Cosimulation object. > > I am using the 0.7 release right now, but I will go ahead and try with the > latest dev release and report back with findings. > > Best, > James > > > On Thu, May 10, 2012 at 10:23 PM, James Lee <rob...@gm...>wrote: > >> Hi, >> >> I'm hoping to hack the PLI module for cosimulation with iverilog to make >> it compatible with VCS. >> Has anyone attempted something like this already and possibly provide me >> with some insight on what changes would need to be made? >> >> Just based on what I read about the iverilog implementation, it seems >> like the biggest hurdle is figuring out what type of callback to use and >> when. >> Would looking into if VCS can use the cbReadWriteSync callback instead of >> the cbReadOnlySync be a good place to start? >> >> Thanks, >> James >> > > |