1. ► Callbacks can only be implemented using function pointers in any language.
2. ► Iterators obtained using vpi_iterate can be rewinded using VPI routines.
3. ► Depth-first walk is only defined for a Tree.
4. ► Stimulus for simulation must always be in the form of binary data i.e. 0’s and 1’s.
5. ► In s_cb_data, the obj field is used to point to the handle on which the callback is registered.
6. ► Verilog compiler can detect argument mismatch between Verilog and ‘C’ land when a routine is called as a function.
7. ► Event Driven Simulation will stop if there are no more events.
8. ► CompileTf routines can make use of all the VPI routines.
9. ► It is possible to easily retrieve the simulation time using VPI routines.
10. ► A cbValueChange callback can be directly registered from vlog_startup_routines called
11. ► CompileTf routines are called only once for any given function.
12. ► A checker will typically register itself at cbNextSim time.
13. ► BFM stands for Bus Flow Model.
14. ► vpiSysTfCall returns the handle to the task or function call which occurred in Verilog and in
turn called this C/C++ routine.
15. ► Providing tf.type as vpiSysTask in the s_vpi_systf_data will export the corresponding ‘C’ routine as a task.