chevillotn

Well no that's not the problem. The simulation never starts, i.e. it is stuck at 0ns! so no simulation at all. This happens when i add one more trigger on...

I have already tried to enable the debug passing COCOTB_LOG_LEVEL=DEBUG and all my yield on RisingEdge or FallingEdge are done through a fork. As said, the simulation starts and stays...

Well i know it's not easy to really understand what i'm trying to describe but the questa is completely stucj when i push the start simulation button... and the log...

ok so what i've done in put a raise_error in decorators.py line 194 in the send function. So the test never starts. Using my faulty python test i manage to...

If i comment the following: int GpiCbHdl::run_callback(void) { ... //this->gpi_function(m_cb_data); ... } The simulation is functional. Of course nothing is really generated.. but something's wrong in the callbacks.

So i have enable scheduler profiling and debug. I have forked a class that yield an Edge on a clock signal. Looking at the log, it looks the scheduler is...

Here is the narrowed down version of my test code which hangs: #--------------------------------------------------------- #--! @file fpga_tb.py #--! @brief Module fpga testbench #--------------------------------------------------------- import cocotb from cocotb.triggers import Timer, RisingEdge, FallingEdge,...

if test_edge is commented out then it works. If it is not commented out, i get this in the log: ``` # 0.00ns DEBUG cocotb.scheduler scheduler.py:243 in react Trigger fired:...

Thanks for your efforts, it looks like you've identified the same problem as I. In the meantime i think i will implement Edge only and check the value of the...

I see... was worth checking anyway. I'm using Edge only now.. no mixing of different edge type as workaround.