|
From: Jon S. <jon...@si...> - 2013-06-23 03:12:41
|
Hi All, I'm having a bit of difficulty with the Icarus VPI. I have some code which worked with Icarus until June 5th of 2012 (git revision 9b3d20239a6688de9127a1d8593d4c83c1c25fce) when vpiPort objects were added. It seems that prior to this revision, when the VPI call vpi_handle_by_name was executed with a path to a module port, that the wire or reg (vpiNet or vpiReg) associated with the port was returned. However now a vpiPort object is returned instead. Unlike a vpiNet or vpiReg, it seems the value of a vpiPort cannot be set or observed with vpi_put_value or vpi_get_value. So some code following the vpi_handle_by_name no longer works in Icarus, but it still does with VCS and NC. I would appreciate any thoughts on what people think the correct behavior should be and whether my VPI code is in error or this is an issue that should be corrected with Icarus. Thanks, Jon |