Re: [myhdl-list] Developing PLI module for cosimulation with VCS
Brought to you by:
jandecaluwe
From: James L. <rob...@gm...> - 2012-05-11 20:21:32
|
Ah, okay, I'll keep at it and see what I can do. It seems VCS has some limitations with vpi_get_value and vpi_put_value, this might be a lead. Anyway, thanks for your time! On Fri, May 11, 2012 at 4:15 PM, Christopher Felton <chr...@gm...>wrote: > On 5/11/12 2:44 PM, James Lee wrote: > > 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. > > > > That sounds about right, if it is compiling and you don't' see any > errors in VCS when you import the foreign interface, it "should" work. > Sorry I don't have any suggestions for debugging the interfaces also. > You do have to be careful for 64bit vs. 32bit but you will (should) get > an error when importing if they don't match. > > I don't know enough (off the top of my head) about VCS or have access to > VCS to be much use. > > Regards, > Chris > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > myhdl-list mailing list > myh...@li... > https://lists.sourceforge.net/lists/listinfo/myhdl-list > |