cliffc Posted January 20, 2015 Report Share Posted January 20, 2015 The parameterized uvm_driver base class includes a built-in uvm_seq_item_pull_port called seq_item_port. The parameterized uvm_sequencer base class includes a built-in uvm_seq_item_pull_imp called seq_item_export. These are always connected in the agent. Every UVM agent that I create declares a uvm_analysis_port that I connect to the tb_monitor's uvm_analysis_port. Question for UVM Library Developers: Is there any reason the uvm_agent base class should not enhanced to be parameterized to the transaction type and include a built-in uvm_analysis_port? Regards - Cliff Cummings Quote Link to comment Share on other sites More sharing options...
David Black Posted January 21, 2015 Report Share Posted January 21, 2015 What if you have more than one monitored type of transaction (some monitors pull out multiple types)? If you consistently name your monitor and analysis port, do you even need to have an agent analysis port (just connect directly to agent.m_monitor.ap)? Quote Link to comment Share on other sites More sharing options...
Recommended Posts
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.