• 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. UVM Monitor Help!!!

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 65
  • Views 13780
  • 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

UVM Monitor Help!!!

Nhatt
Nhatt over 10 years ago

Hi all,

I have a SPI interface, it has three modes to transfer the data out on IO[0:7]. In SPI standard there is just IO[0] is used. QPI mode, it uses IO[3:0] and In OPI mode, the whole IO are used. When driver receives a req from sequencer, it drives that req to the interface depending on modes. The interface sometimes goes with SPI, sometimes QPI or OPI. And I want to monitor the tx data, but I dont't know how to setup the monitor to sample the data corresponding to the mode that the driver has used. Are there ways to make monitor works in the same mode with the driver?

Thank you!

  • Cancel
  • StephenH
    StephenH over 10 years ago

    Well, I guess there are two options: first you could make your monitor smart enough to monitor all the wires all the time, and if the values on the higher bits are zero or meaningless then you can assume that the interface is running in one of the reduced width modes. That might be easy if your design / BFM always drives X, Z or 0 on the unused lines but if you have random data on them, then you might fail to detect the right configuration.

    The alternative would be to have a way to poke the current configuration into the monitor from another part of the TB, for example if you have a monitor on the register interface, connected to UVM_REG model of the DUT, then you could detect writes for the SPI configuration and pass the info to the monitor. Or your monitor could have a pointer to the necessary UVM_REG registers so that it can figure out the current config itself, but then your monitor becomes tightly coupled to the DUT and is less re-usable across projects.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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