wuddi Posted December 20, 2012 Report Share Posted December 20, 2012 Hi UVM experts: Normally, driver gets transaction at posedge clock and then drive transaction to interface. But when driver gets a transaction at non-posedge clock, it cannot drive transaction immediately, and must wait next posedge clock (NBA region) to drive it out. My code as below shows: [example code begin] forever begin seq_item_port.get_next_item(req); vif.cb.address <= req.address; vif.cb.data <= req.data; @(vif.cb); end [example code end] transaction_1 : address = 32'h0000_1010; data = 32'h0000_1111; transaction_2 : address = 32'h0000_1111; data = 32'h1111_0000; When driver gets tranasction_1 at non-posedge clock, and gets transaction_2 at next posedge clock, I found only transaction_2's address=32'h0000_1111 & data=32'h1111_0000 been driven to the interface. So how to fix this bug? Thanks in advence. Best Regards wuddi Quote Link to comment Share on other sites More sharing options...
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.