Jump to content

UVMSC-TLM2.0 Interface

Recommended Posts

Hi All ,

I'm exploring uvmsc as a vitrifaction strategy .Does any one did already with TLM 2.0 model interface .If yes please share me the example to integrate in my environment .As per LRM 


interfaces are defined.

NOTEUVM-SystemC does not yet define the TLM-2.0 blocking and non-blocking transport interfaces, direct memory interface (DMI), nor a debug transport interface. Use the SystemC TLM-2.0 interfaces instead. 


What does use SystemC TLM2-0 mean .Please help me on these .




Link to comment
Share on other sites

Hi Charan,


uvm_(non)blocking_*_port are SystemC TLM-1.0 based UVM-SystemC ports. As stated in your referenced NOTE, UVM-SystemC has not yet defined TLM-2.0 transport interfaces etc.. Hence, in case you need SystemC TLM2.0 based interfaces, you need to use the ones provided by SystemC itself.


In case you have a SystemC model with TLM2.0 based interfaces, you have (at least) two options to verify this with a UVM-SystemC environment:

  • create a UVM driver that contains initiator/target sockets in order to connect directly to your model
  • instantiate a signal-to-TLM2 / TLM2-to-signal adapter between a signal level driver and your model


P.s. you probably meant "verification" i.s.o. "vitrifaction", but at least I learned a new word 😉  https://en.wikipedia.org/wiki/Vitrification



Link to comment
Share on other sites

  • 1 month later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...