TLM 2.0 Sockets · UVM

Part 4 · TLM & Analysis · Intermediate

5topics
5lessons

On this page

A DV engineer meets TLM 2.0 when the bench has to talk to something that was not written in UVM: a SystemC model of the DMA's register block from the virtual-platform team, a C++ reference model wrapped for co-simulation, or the register layer's own uvm_reg_tlm_adapter. TLM 2.0 standardizes one memory-mapped transaction, the generic payload, and a timing contract, so models from different teams plug together. UVM-SV implements a subset of it. This topic covers that subset, and where it stops.

What you will be able to do

Declare and bind initiator, target and passthrough sockets, and predict what connect() refuses.
Write a b_transport target and initiator that agree on who consumes the annotated delay.
Follow a non-blocking transfer through its phases, including the legal shortcuts.
Explain temporal decoupling and why UVM-SV has no quantum keeper.
Build a generic payload correctly, return the right response status, and carry sideband data in an extension.

Learning path: sockets first, then the generic payload, then blocking transport, then non-blocking transport and temporal decoupling.

Start with sockets. The generic payload lesson can be read next or last; blocking transport comes before the non-blocking and decoupling lessons.

The lessons

Lesson	What you learn
Initiator and target sockets	What a socket bundles, the socket classes, passthrough sockets, and binding rules.
Blocking transport	`b_transport`, `uvm_tlm_time`, and the two ways to account for delay.
Non-blocking transport	The four phases, sync return values, and the 3-, 2- and 1-call shortcuts.
Temporal decoupling	Running ahead of simulation time with a local offset and a quantum, and loosely versus approximately timed.
Generic payload: extensions and status	Fields and accessors, response status codes, byte enables, streaming width, `uvm_tlm_extension`, and what SystemC has that UVM-SV does not.

Related topics

Up nextInitiator and Target Sockets

Practice this lesson Report an error

What you will be able to do

Declare and bind initiator, target and passthrough sockets, and predict what connect() refuses.

Write a b_transport target and initiator that agree on who consumes the annotated delay.

Follow a non-blocking transfer through its phases, including the legal shortcuts.

Explain temporal decoupling and why UVM-SV has no quantum keeper.

Build a generic payload correctly, return the right response status, and carry sideband data in an extension.

Learning path: sockets first, then the generic payload, then blocking transport, then non-blocking transport and temporal decoupling.

Start with sockets. The generic payload lesson can be read next or last; blocking transport comes before the non-blocking and decoupling lessons.

The lessons

Lesson	What you learn
Initiator and target sockets	What a socket bundles, the socket classes, passthrough sockets, and binding rules.
Blocking transport	`b_transport`, `uvm_tlm_time`, and the two ways to account for delay.
Non-blocking transport	The four phases, sync return values, and the 3-, 2- and 1-call shortcuts.
Temporal decoupling	Running ahead of simulation time with a local offset and a quantum, and loosely versus approximately timed.
Generic payload: extensions and status	Fields and accessors, response status codes, byte enables, streaming width, `uvm_tlm_extension`, and what SystemC has that UVM-SV does not.