VIP’s Verification Environment is classical the same as UVM Examples;
##1.1 SV-UVM Agent Standard Architech
a.uvm_config.sv config reg/ram using uvm_object or SOMA file;
b.uvm_driver:BFM;
c.uvm_monitor:pvovides an api to all interesting VIP activities in the form of uvm_events,analysis_ports and callback; reports protocol err; built-in coverage model;
Basic Concepts:
test layer inter with by Configuration,callbacks,Queues;
VIP Configuration using PureView and SOMA file or uvm_configuration.sv file;
PureView is an easy-to-use Gui-based tool to define VIP configuration;
Callbacks:used as error-injection: Modify packet at selected points during data flow–Enables usr to intercept a packet,change its charateristics,and re-insert it ;
History and Trace files For debug ;
Roles of Active and Passive Agents: Active agent is to generate protocol traffice to DUT; Passive Agent is to 1.Monitor protocol traffice for vviolations;2.Function coverage collection;3.Provide connection to scoreboard;
MII interface: MAC and PHY; Backplane interface: PCS PMA TX Station RX Station;
Callback: used to intercept(monitor) a transaction; change the characteristics of a trans;Re-insert the modified trans ;
Error Injection ways:
1.Protocol driver purpose: purpose generate the violated protocol ;
2.Through packet error fields;
3.Through callback:Modify the pkt content to be used to inject errs;
Virtual sequenve tells which sequence to run;
Examples:
`uvm_do_on(seq1,p_sequncer.master_sqr);
`uvm_do_on(seq2,p_sequenver.slave_sqr);
Conclusion:
1.Cadence vip is just so-so,But is worth learning;
2.Know how they employ the uvm ways;