Communication between e and SV

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.

What I meant was time, effort, performance so your guess was correct!! :-) Thank you for your quick reply.

How about interface between C and SV? Do you think still VPI is needed? or DPI might be a solution on that?

Now I'm thinkg about common library, written in C, that can be used in several interface , e-SV and C-SV. I'd like to have other's ideas.

Thank you!

I'm no expert, but what I've seen so far suggests DPI can do the majority of things an everyday user would want, but sometimes you might need to augment it with some VPI to do things to the simulator core, e.g. turning on/off assertions or executing simulator-specific features like TCL commands. The answer will really depend on what you need to achieve.

If what you're most worried about is how to pass transaction data between e, SV and C, I'd expect the TLM ports to be of most use, since they are truly language-neutral and were designed for that purpose. It also means less work yourself to interface the data types etc.