Kaleb Barrett

@mballance I'm not so sure how that would work? As stated in this issue, calling a DPI function/task from a VPI callback does not seem to be supported by the...

> If callbacks (sim-event, time-callback, signal-callback) are routed through DPI prior to calling cocotb, it should then be fine to make DPI calls from cocotb. How is that possible?

@mballance Maintenance burden is not an issue if the implementation is not incorporated into this repo. We are trying to avoid becoming a dumping pile of good ideas. We want...

@Alex-Mann Unfortunately, digging into the source code and asking questions on the gitter is the best thing to do now. We do plan on documenting it all at some point...

Following on this discussion and those papers, it seems the best way of "calling" a DPI export is actually to not call the DPI export, but instead communicate over an...

@Alex-Mann The ones that @mballance posted. In the second link on page 6 it goes over how it worked around the inability to call DPI exports from VPI callbacks. I...

Questa and the 32-bit ModelSim are different simulators. It would be interesting to see if this triggers in Questa as well. Hopefully this problem will become obsolete in the near...

I think my course of action will be to hack and slash my way to victory, then reflect to see if there is an incremental way forward so we aren't...

Is there any reason to not simply copy unittest's interface? Not sure I understand the point of the hook registering functions.

Pytest accepts unittest's TestCases. https://docs.pytest.org/en/6.2.x/unittest.html The python runner is already merged (though it does need work). It only concerns running simulations and not dealing with with cocotb tests. It's just...