Jump to content

Search the Community

Showing results for tags 'transaction recording'.

  • Search By Tags

    Type tags separated by commas.

  • Search By Author

Content Type


Forums

  • Accellera Systems Initiative
    • Information
    • Announcements
    • In the News
  • SystemC
    • SystemC Language
    • SystemC AMS (Analog/Mixed-Signal)
    • SystemC TLM (Transaction-level Modeling)
    • SystemC Verification (UVM-SystemC, SCV, CRAVE, FC4SC)
    • SystemC CCI (Configuration, Control & Inspection)
    • SystemC Datatypes
  • UVM (Universal Verification Methodology)
    • UVM (IEEE 1800.2) - Methodology and BCL Forum
    • UVM SystemVerilog Discussions
    • UVM Simulator Specific Issues
    • UVM Commercial Announcements
    • UVM (Pre-IEEE) Methodology and BCL Forum
  • Portable Stimulus
    • Portable Stimulus Discussion
    • Portable Stimulus 2.0 Public Review Feedback
  • IP Security
    • SA-EDI Standard Discussion
    • IP Security Assurance Whitepaper Discussion
  • IP-XACT
    • IP-XACT Discussion
  • SystemRDL
    • SystemRDL Discussion
  • IEEE 1735/IP Encryption
    • IEEE 1735/IP Encryption Discussion
  • Commercial Announcements
    • Announcements

Categories

  • SystemC
  • UVM
  • UCIS
  • IEEE 1735/IP Encryption

Find results in...

Find results that contain...


Date Created

  • Start

    End

Last Updated

  • Start

    End

Filter by number of...

Joined

  • Start

    End

Group

AIM

MSN

Website URL

ICQ

Yahoo

Jabber

Skype

Location

Interests

Biography

Location

Interests

Occupation

Company

Found 2 results

  1. T. Zimmermann
    Hi, I am using transaction recording with the latest version of SCV (version 2.0.1) and currently I am getting a segmentation fault. I have just searched for a list or something similar with known bugs but I haven't found one. Is there a bug list or a list of known problems somewhere? Regards, Thomas PS: I will create a minimal model in the next few days.
  2. ambreezesj
    I am trying to improve transaction recording. So far we have used field automation macros, but to make debugging efficient I am trying to customize the recording. I've understood that the do_record function should do the trick class proj_brc_tr extends proj_tr; rand time cmd_width; rand time brc_per; `uvm_object_utils_begin(proj_brc_tr) `uvm_field_int(cmd_width,UVM_ALL_ON+UVM_TIME) `uvm_field_int(brc_per,UVM_ALL_ON+UVM_TIME) `uvm_object_utils_end function void do_record(uvm_recorder recorder) ; `uvm_record_attribute(recorder.tr_handle,"cmd_width",cmd_width) ; endfunction So here I'm trying to override the field automation micros and display only 'cmd_width' using do _record. But the change is not getting reflected when I simulate the files. I've read in some forums that do_record needs to be called by the record function, but doesn't do_record gets called automatically when begin_tr() and end_tr() are called in monitors and drivers?
×
×
  • Create New...