• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Functional Verification
  3. Transaction tracing in simvision

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 65
  • Views 14666
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Transaction tracing in simvision

Joep Boonstra
Joep Boonstra over 16 years ago

 Hi,

I'm using OVM transaction level tracing in SV. I was wondering if I can have simvision render different types of transactions with different colors e.g. based on a transaction attribute. I know how to do it at signal level using mnemonics but I haven't succeeded doing this at transaction level. Anyone?

 -Joep

  • Cancel
Parents
  • vmotel
    vmotel over 16 years ago
    Hi Joep,
    I agree that coloring transactions can also be very useful, it is complementary to the nice expanding feature explained by Stephen.
    The good news it that it is possible to color transactions in Simvision, but it is not as immediate as expanding by attribute. You need to create a TxE search for that. The transactions to be colored needs to be "accepted" by the search (use the "accept" command in the apply section), then you an use the command "set_attribute highlight color_name_or_number".
    When the result table is selected, the lines take the colors defined in the search, and the transactions in the Waveform Window are highlighted with the same colors. It can make a very nice visual effect, depending on your color choice !
    For example :
    apply {
      fiber "*::Transactions.mem_transactions"  {
        trans_type "mem_transaction" {
             if {[attribute "command"] == "READ"} {
               accept
               incr read_count
               if     {[attribute "bank"] == 0} {
                 set_attribute highlight green
               }
               if     {[attribute "bank"] == 1} {
                 set_attribute highlight purple
               }
               if     {[attribute "bank"] == 2} {
                 set_attribute highlight blue
               }
               if     {[attribute "bank"] == 3} {
                 set_attribute highlight yellow
               }
             }
             if {[attribute "command"] == "WRITE"} {
               accept
               incr write_count
               if     {[attribute "bank"] == 0} {
                 set_attribute highlight cyan
               }
               if     {[attribute "bank"] == 1} {
                 set_attribute highlight red
               }
               if     {[attribute "bank"] == 2} {
                 set_attribute highlight lightblue
               }
               if     {[attribute "bank"] == 3} {
                 set_attribute highlight pink
               }
             }
        }
      }
    }
    exit {
    }
    table {
      sort bank
      col fiber [fiber]
      col trans_type [trans_type]
      col command [attribute command]
      col bank [attribute bank]
      col items [items]
      row
      row total_read_count  $read_count
      row total_write_count $write_count
    }
    Creating such a TxE search (in "text mode") should not be too long if you take benefit of the "Browse" button to interactively create it.
    Best regards,
    Vincent
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • vmotel
    vmotel over 16 years ago
    Hi Joep,
    I agree that coloring transactions can also be very useful, it is complementary to the nice expanding feature explained by Stephen.
    The good news it that it is possible to color transactions in Simvision, but it is not as immediate as expanding by attribute. You need to create a TxE search for that. The transactions to be colored needs to be "accepted" by the search (use the "accept" command in the apply section), then you an use the command "set_attribute highlight color_name_or_number".
    When the result table is selected, the lines take the colors defined in the search, and the transactions in the Waveform Window are highlighted with the same colors. It can make a very nice visual effect, depending on your color choice !
    For example :
    apply {
      fiber "*::Transactions.mem_transactions"  {
        trans_type "mem_transaction" {
             if {[attribute "command"] == "READ"} {
               accept
               incr read_count
               if     {[attribute "bank"] == 0} {
                 set_attribute highlight green
               }
               if     {[attribute "bank"] == 1} {
                 set_attribute highlight purple
               }
               if     {[attribute "bank"] == 2} {
                 set_attribute highlight blue
               }
               if     {[attribute "bank"] == 3} {
                 set_attribute highlight yellow
               }
             }
             if {[attribute "command"] == "WRITE"} {
               accept
               incr write_count
               if     {[attribute "bank"] == 0} {
                 set_attribute highlight cyan
               }
               if     {[attribute "bank"] == 1} {
                 set_attribute highlight red
               }
               if     {[attribute "bank"] == 2} {
                 set_attribute highlight lightblue
               }
               if     {[attribute "bank"] == 3} {
                 set_attribute highlight pink
               }
             }
        }
      }
    }
    exit {
    }
    table {
      sort bank
      col fiber [fiber]
      col trans_type [trans_type]
      col command [attribute command]
      col bank [attribute bank]
      col items [items]
      row
      row total_read_count  $read_count
      row total_write_count $write_count
    }
    Creating such a TxE search (in "text mode") should not be too long if you take benefit of the "Browse" button to interactively create it.
    Best regards,
    Vincent
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information