Stats

  • Locked Locked
  • Replies 2
  • Subscribers 65
  • Views 13067
  • 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

regarding e and sv

Kamal
I need to do mixed language verification with URM ( e and SV ). In IPCM6.2 mrm manual explaining about e(eVC) over System verilog with xbus example. But, i need for System verillog over e(eVC) their is no description like how to create API wrapper or simple examples. I hope somebody come across wtih this!! please guide me.. Thanks in advance. Regards, kamal
Parents

  • Hello Kamal,

    For the time being, I'd recommend you use existing, established e/SV communication utilities including method ports, event ports and simple ports to communicate with your eVC from SV. For example, you can create a e layer on top of your eVC that defines method ports allowing your SV code to -

    • invoke e sequences
    • get transaction information collected by the monitor

    Similarly, you can use event ports for synchronization and communicating status from the eVC to the SV layer.

    A more automated approach, creating a SV wrapper around your eVC is coming soon. Please contact your Cadence AE for more details...

    Regards,

         Zeev. 

Reply

  • Hello Kamal,

    For the time being, I'd recommend you use existing, established e/SV communication utilities including method ports, event ports and simple ports to communicate with your eVC from SV. For example, you can create a e layer on top of your eVC that defines method ports allowing your SV code to -

    • invoke e sequences
    • get transaction information collected by the monitor

    Similarly, you can use event ports for synchronization and communicating status from the eVC to the SV layer.

    A more automated approach, creating a SV wrapper around your eVC is coming soon. Please contact your Cadence AE for more details...

    Regards,

         Zeev. 

Children
No Data

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.