VPI: vpiPort should be a ModifiableObject?
See original GitHub issueAs mentioned in #796 in the current implementation of the VPI interface (here and here) , vpiPort
s are made into HierarchicalObject
s. I believe this is not correct and a vpiPort
should be considered as a ModifiableObject
instead.
I already have a patch for this but I’d like to hear more about the original rational and also #796 to settle.
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Using PLI 2.0 (VPI) with VCS (Yes, it really works!)
A handle is a pointer to a structure contain- ing information about the object. In this regard, the VPI works similarly to the...
Read more >Details about the VPI Routine Library - Springer Link
The VPI routines are a library of 37 C functions that can interact with Verilog sim- ulators. The previous chapter has introduced how...
Read more >Verilog PLI Tutorial Part-III - ASIC World
This routine returns the handle to a Verilog-HDL object based on the specified name and scope. This function returns the hierarchically lower net...
Read more >RFC 2297: Ipsilon's General Switch Management Protocol ...
A virtual channel connection is specified by the input port, input VPI, ... used by the controller to establish, delete, modify and verify...
Read more >Deploying and Discovering Objects
If you only want to deploy a few objects or if many of your objects are not yet ... Source VPI—Enter the virtual...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
While investigating #497 / #2075, I found that
vpiPort
objects don’t have values themselves and just detail connections. Usingvpi_handle(vpiLowConn, port_handle)
gets the handle of whatever it’s connected to (or NULL for no connection) lower in the hierarchy (such as a variable or net). So I thinkModifiableObject
is not the correct mapping for avpiPort
.Has your question been resolved? If so please close this issue. If it has not been resolved, you may need to provide more information. If no more activity on this issue occurs in 7 days, it will be closed.