vr_ahb_tlm systemc model

Let me give the clear picture.

1.We are doing co-verification of RTL with equivalent systemC implementation, which implies that we reuse the RTL DUT verification environment for the systemC DUT verification also. And for this reuse, the vr_ahb_tlm add on IS A MUST.

2.It is natural that RTL environment uses the latest version of eVCs - in this case it is vr_ahb 9.2.

3.For some IPs, the systemC verification environment customisation began when the eVC versions that were used were early ones - like vr_ahb 2.2 in this case, along with vr_ahb_tlm 1.0a1.

4. But the RTL development went ahead and so also the vr_ahb eVC moved to newer versions like 9.2 5. Now when we want to resume co-verification with systemC DUT, the vr_ahb_tlm 1.0a1 not being compatible to vr_ahb 9.2 IS DEFINITELY A SHOW STOPPER. Because by co-verification, we guarantee the customer that RTL and systemC implementations are equivalent (and we have a host of IPs lined up for this), and as proof of this they should have run the same tests on the same environment WITH THE SAME TOOL VERSIONS.

If we cannot have the vr_ahb_tlm upgraded with vr_ahb eVC, then specman coverification of RTL with systemC will come to a halt!!

we already contacted local cadence AE but till now no updates.

Thanks,

Abhineet

Let me give the clear picture.

1.We are doing co-verification of RTL with equivalent systemC implementation, which implies that we reuse the RTL DUT verification environment for the systemC DUT verification also. And for this reuse, the vr_ahb_tlm add on IS A MUST.

2.It is natural that RTL environment uses the latest version of eVCs - in this case it is vr_ahb 9.2.

3.For some IPs, the systemC verification environment customisation began when the eVC versions that were used were early ones - like vr_ahb 2.2 in this case, along with vr_ahb_tlm 1.0a1.

4. But the RTL development went ahead and so also the vr_ahb eVC moved to newer versions like 9.2 5. Now when we want to resume co-verification with systemC DUT, the vr_ahb_tlm 1.0a1 not being compatible to vr_ahb 9.2 IS DEFINITELY A SHOW STOPPER. Because by co-verification, we guarantee the customer that RTL and systemC implementations are equivalent (and we have a host of IPs lined up for this), and as proof of this they should have run the same tests on the same environment WITH THE SAME TOOL VERSIONS.

If we cannot have the vr_ahb_tlm upgraded with vr_ahb eVC, then specman coverification of RTL with systemC will come to a halt!!

we already contacted local cadence AE but till now no updates.

Thanks,

Abhineet