In reply to Rogers:
As Bob mentioned in an earlier reply, this sort of error will not occur if you used the generation scripts provided by the UVMF install alongside the base UVMF class definitions. If you did not use those generator scripts there are too many variables in play to effectively help you debug and resolve the fatal error you’re seeing without a full test case or a wider view into what you’re trying to do.
Making changes to the base UVMF code class definitions is definitely not _**_the right way to go here, it’ll just dig the hole deeper.
I would suggest that you back out all changes to the UVMF base class source and look at some of the examples and run the generated examples to see how these BFM interface names are supposed to be passed around a UVMF bench, then apply the same technique to however you’re implementing things on your end.