• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Functional Verification
  3. vr_ahb_tlm systemc model

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 66
  • Views 13734
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

vr_ahb_tlm systemc model

nishvlsi2011
nishvlsi2011 over 14 years ago
Hi, I would like to know where I can find the latest vr_ahb_tlm systemc model. I have KITSOCV9.2 but It seems this model is not present in that. Thanks! Manish
  • Cancel
  • abhineet22
    abhineet22 over 14 years ago

    Hi Even same problem i am facing thay dont have compatible version for VR_AHB 9.2 with respect to VR_AHB_TLM.and also they are not giving any kind of support on that.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • StephenH
    StephenH over 14 years ago

    Hi guys.

    I think there's maybe a little confusion here. The Functional Verification Kit (KITSOCV) that ships with Incisive has a basic AHB UVC, which is really meant as an educational tool as part of the kit workshops. The fully featured AHB verification component with full protocol coverage (including AXI4 and ACE) is part of the VIPP92 and VIPCAT112 products on the download server.

    VIPP92 is an old product to be used with Incisive 9.2 and 10.2, VIPCAT112 is the replacement product that works with Incisive 10.2 onwards and features a new more flexible licensing model, as well as other new protocols.

    Regarding TLM, it's not clear from your message what feature you are looking for. The AHB VIP does support TLM, but your requirements are too unclear to say whether the current TLM support matches what you need / want.

    I would strongly encourage you to work with your local Cadence AE to learn more about what the vr_ahb VIP can do, and to get some help to set it up.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • nishvlsi2011
    nishvlsi2011 over 14 years ago
    Hi Stephen, In our old systemC model of our module, we used vr_ahb eVC V2.2 and vr_ahb_tlm V1.1. Now we have to use the latest vr_ahb eVC V9.2 but it seems there is no vr_ahb_tlm model compatible for 9.2 version of vr_ahb eVC. As per your advice we will definitely try to contact local Cadence AE. Thanks!
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • abhineet22
    abhineet22 over 14 years ago

    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

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information