SpecFor a DMA descriptor (addr, len)
desc_item is what a model writes with confidence from that spec: one constraint per bullet, each fine on its own. They only contradict each other together.
The loop that drives it is the usual create, randomize, use. Right now every descriptor comes back with addr == 0 and len == 0, and randomize()’s return value, which says so, is never read. Verilator prints an UNSATCONSTR warning each time, but a warning fails no regression.
Fix what’s actually broken against the spec, not a leftover default.
One working answer: brokenbench's own fix for this exercise. Try a few runs first.
What changes, against the code you started with:
docker run --pull always --rm -p 127.0.0.1:8787:8787 ghcr.io/adibis/brokenbench-runnerLooking for a runner on this computer…
The first start downloads about 250 MB; after that it starts in seconds and only downloads again when there's an update. Your code goes to the runner on your computer, not to chipdv.io.