Re: vpi_put_value
- From: Yottameter <yottameter@xxxxxxxxx>
- Date: Fri, 14 Sep 2007 10:30:26 -0700
Not sure what you are doing exactly - usually I just call vpi_put_value without assigning it to a vpiHandle.
The function will usually return NULL, unless you OR the fourth parameter input with vpiReturnEvent.
If you are ORing the flag, and expect a vpiHandle, it shows that it's of type vpiSchedEvent. I'm assuming that is a scheduled event. Is it possible you are scheduling an event, and then telling it to free the handle before the event is scheduled?
I'm really reaching here, as I have never used the return value of vpi_put_value. I'd be interested to hear how you are applying it. I could set up a test snippet pretty easily if I know what flag and time property you are using.
SrFPGA wrote:
Hi,.
vpi_put_value() returns a vpiHandle and to free that handle, The
Verilog PLI Handbook uses vpi_free_object() on the vpiHandle
returned. Did anyone have success freeing the handle.
Thanks in Advance
Sarma
- Follow-Ups:
- Re: vpi_put_value
- From: SrFPGA
- Re: vpi_put_value
- References:
- vpi_put_value
- From: SrFPGA
- vpi_put_value
- Prev by Date: Re: "Latch generated" warning from Synplicity
- Next by Date: Re: "Latch generated" warning from Synplicity
- Previous by thread: vpi_put_value
- Next by thread: Re: vpi_put_value
- Index(es):