In reply to chr_sue:
Hi Chris,
Thanks for going the extra mile on this.
The short answer to your question is no, UVMF is not the structure I am aiming for.
I started with UVMF framework but found it too cumbersome for the project I am on that is not going to use HW emulation. In fact many projects that I develop testbenches for do not use HW emulation. I have taken their initial structure and simplified it back to a more standard UVM structure.
I give lots of kudos to their UVMF structure for HW emulation but my needs are to have a testbench that doesn’t require going back to their python scripts when I need to add an interface or BFM.
When I need to add a new BFM I would really like to just code the required classes (driver, monitor, transaction) and add/override at the test_top level. No changes to the environment or even the generic agent. There should be a way to do this, but I can’t seem to find it.
Going back to the question previous, if I derive all my drivers from a base class driver I should be able to override it though right? At least that is what I see in the advanced UVM videos. Not exactly my situation but close.
Scott
Scott