Tomasz Hemperek

@gchqdev1729 Maybe you can look at this https://github.com/themperek/cocotb-test/blob/master/cocotb_test/simulator.py but there are some changes in cocotb 1.4 that will make it all easier (some changes still to be added).

>Is there a good place to see what's planned for the 1.4 release - apologies if this is obvious, I'm new to GitHub as a contributor! Not really but I...

BTW: https://github.com/cocotb/cocotb/issues/1611 > Modelsim and VCS fail when waiting on ReadWrite after RisingEdge.

If one would like to use standard tools should somehow adopt Cobertura example: https://gist.github.com/apetro/fcfffb8c4cdab2c1061d and https://raw.githubusercontent.com/cobertura/web/master/htdocs/xml/coverage-04.dtd but I am not sure if this can apply to functional coverage. For in...

Maybe we use YAML as our functional proper coverage but can write some simple converter to Cobertura that would allow us to trace changes with standard tools (even if this...

@mciepluc Unfortunately not. It is a bit hacking I can try to work on this a bit but not in January. Maybe UCIS makes more sense. Especially if we can...

I started to fit into Cobertura line coverage (it possible with a bit of hacking) but I think in the end we need to generate our own HTML report that...

Something like this? https://github.com/themperek/cocotb-test/blob/b992e3c3c7644f8581811cd2ca6a01d23f2115b3/tests/test_parameters.py#L53-L54 `sim_buld` specify where it will be compiled.

If anything I would change this to `make_args` and add this only to the verilator class.

Can add this. Could you give me the command that are needed? BTW: any idea why vcs returns 4 on exit?