TLM 2.0 & The Generic Payload

Moving beyond Put/Get. The industry standard for high-performance, interoperable Verification Components.

The Unified Container

In high-level modeling, the overhead of custom transaction classes is a bottleneck. TLM 2.0 introduces the Generic Payload (GP)—a pre-defined, memory-mapped transaction container that serves as the "Universal Language" for architectural models.

Why use the Generic Payload?

Interoperability: Component A (custom) can talk to Component B (third-party) without class conversion.
Performance: Optimized for multi-threaded simulation speeds.
Simplicity: No need to define new classes for standard memory reads/writes.

Detailed Field Analysis

The uvm_tlm_generic_payload class contains all the essential elements required to describe a memory transaction across most modern buses (AXI, AHB, Wishbone).

Field	Description	Legal Values
m_command	Direction of transfer	READ, WRITE, IGNORE
m_address	64-bit Target address	0 to 2^64-1
m_data	Byte array of payload	byte[]
m_byte_enable	Strobe/Masking	byte[] (00/FF)

The Extension Mechanism

Standard buses have specific sideband signals (like AXI IDs or Cache attributes) that aren't in the GP fields. TLM 2.0 solves this with Extensions—a way to "side-load" bus-specific info onto the standard container.

Implementation: Adding AXI Sidebands


// 1. Define the extension
class axi_ext extends uvm_tlm_extension #(axi_ext);
    int mid; // Master ID
    bit [3:0] cache;
    `uvm_object_utils(axi_ext)
endclass
// 2. Attach to the Generic Payload
uvm_tlm_generic_payload gp = new();
axi_ext ext = new();
ext.mid = 5;
gp.set_extension(ext);

Best Practice: Interoperability

When building a transactor (e.g., an AXI to TLM2 bridge), always populate the standard GP fields first. Use extensions only for metadata that is strictly necessary for the destination component. This ensures your transactor remains compatible with generic TLM 2.0 monitors and scoreboards.

Deeper Insight

The Generic Payload is a pooled resource. Always call reset() on a GP object before reusing it to ensure clean state and avoid extension leakage.

Previous TLM Basics & Handshakes Next Sockets & b_transport