I am having a requirement to convert the existing VMM based VIP to a UVM based. Is it okay to have a UVM wrapper which will instantiate the VMM based VIP. I have heard of the interop libraries to do VMM2UVM and UVM2VMM communication.
I am doing some initial R&D on this. Is it okay to go head with this wrapper plan using the interop libraries.
There is no released UVM ↔ VMM interoperability kit available today, as the UVM 1.0 has not been released yet. The OVM ↔ VMM interoperability kit is proof that wrappers can be created, but it’s not trivial. The key piece of work is that the phases of the methodology libraries need to be coordinated so that class objects are constructed in the proper order so their are no null handle references. The UVM 1.0 will have some significant phasing restructuring, so it doesn’t make sense to invest in any interoperability work until the UVM phasing is completed.
Mahesh,
If you use VCS, there is inbuilt inter-op for this. Check their doc/examples or contact them. As Dave mentioned, investing in an inter-op kit is not the wisest thing for now.
Thanks for the advice. But is there any way so that i can convert UVM Code/Env into VMM? Actually the BFM is in UVM but now i have to use the same logic in VMM so i don’t have time to start from the beginning. Can you please suggest some better way.
Thanks in advance…