Jump to content

Generic Payload Vs PROTOCOL specific packets/seq_items in UVM env

Recommended Posts

Hello All,


I am wondering for the use of generic payload instead of PROTOCOL specific packets/seq_items in UVM agents.


Why : 

1. This will help to verify the SC-TLM models(used as golden ref models) with the same testenv.
2. Generic Payload is standard.
3. GP has better interoperability options, less changes in scoreboards etc for new UVC's connections.


1. All the UVC's work on the Generic Payload.
2. Only Driver needs the extra functionality for GP-Protocol toggling conversion.
3. Monitor need to pack the protocol toggling to GP.


1. Functional Coverage would be somehow difficult to calculate.


Please let me know am I moving in right direction or there may be some serious problems using it.



Link to comment
Share on other sites

  • 3 weeks later...

Hi Karandeep,


We presented a paper "A Beginner's Guide to Using SystemC TLM-2.0 IP with UVM" at several European Synopsys User Group (SNUG) meetings in 2012. This included a discussion of using the Generic Payload in a UVM environment which may help. You can download it from the "KnowHow" pages on the Doulos website - http://www.doulos.com/knowhow/sysverilog/SNUG12_uvm_tlm2/




Link to comment
Share on other sites

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...