Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

ability to force/freeze signal

See original GitHub issue

rather than just being able to deposit signals, it is helpful to force signals inside a design. Would be great if cocotb would support that. Maybe as an signalname attribute. dut.signalname._force = 1

Issue Analytics

State:
Created 5 years ago
Comments:17 (13 by maintainers)

Top GitHub Comments

3reactions

cmarqucommented, Nov 6, 2018

Force/release would allow us to build a tool for what is called “testbench qualification” or “mutation coverage” - inject an error into the design, run a regression test and check that at least one of the tests finds the injected error. If the error is not detected, the testbench is too sloppy.

We could start by injecting stuck-at faults at the DUT ports (I have a pull request coming up for providing _is_port and _port_direction attributes for discovered objects).

This could be a good project for something like Google’s Summer of Code.

3reactions

lukedarnellcommented, Oct 28, 2018

Ok, I will do a pull request with the changes.