Skip to content

The factory override runs clean, but the DUT’s parity checker never gets tested

factory-override / phase-orderingUVM · runs take about 2 minutes

A register-write test wants an error-injecting driver, which corrupts one bit of every write so the DUT’s write-parity checker gets exercised. It swaps drivers with a factory type override, base_write_driver -> error_inject_write_driver, so the env never needs to know the variant exists.

Right nowThe test believes it configured the error-injecting driver, but env.drv is still a plain base_write_driver.

Fix the code so env.drv is an error_inject_write_driver.

Source on GitHub

factory_override.sv