Stats

  • Locked Locked
  • Replies 3
  • Subscribers 64
  • Views 13427
  • 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

Communication between e and SV

YM KIM

Hello all,

I'd like to implement interface channel between e and SV and followings are candidates. Which one do you think the most efficient?
Or else ways? Any ideas will be welcomed.

1. Using ports in Specman 

2. DPI

3. VPI

Thank you.

Parents

  • What sort of efficiency are you after? ;-)

    I guess if you hand-crafted some bit of DPI or VPI code you might possibly get it a shade faster than the core tools can do, but you'd have spent many hours doing it, and it wouldn't be a generic solution. I'd recommend that you use e ports; you have a choice of method ports or TLM ports.

    Using these takes just seconds to hook up, it's easy to maintain, and you won't waste hours trying to get (and keep) it working.

    I used both e-SV method ports and TLM ports for the first time a few months ago, on a USB project, and was up and running really quickly just from the examples in the docs.

    You need to be using at least IES 8.2 for TLM ports to work.

Reply

  • What sort of efficiency are you after? ;-)

    I guess if you hand-crafted some bit of DPI or VPI code you might possibly get it a shade faster than the core tools can do, but you'd have spent many hours doing it, and it wouldn't be a generic solution. I'd recommend that you use e ports; you have a choice of method ports or TLM ports.

    Using these takes just seconds to hook up, it's easy to maintain, and you won't waste hours trying to get (and keep) it working.

    I used both e-SV method ports and TLM ports for the first time a few months ago, on a USB project, and was up and running really quickly just from the examples in the docs.

    You need to be using at least IES 8.2 for TLM ports to work.

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.