Logger Posted January 10, 2013 Report Share Posted January 10, 2013 I have ran into a couple of instances where it would be quite handy to introduce some form of sequence router into my environment. Basically, I have two drivers. I can execute a sequence on either one of them. But I'd like to add another sequencer in front of the two. It could have some routing rules (probably constraint based), such that I can run my sequence on this new router sequencer, and the router sequence will then execute the sequence on one of the two downstream sequencers. I've tried building a virtual sequence to do this, but fields inside the sequence get populated once the virtual sequence starts executing. Passing the sequence to the downstream sequencers has undesirable side effects and doesn't seem to work. Seems like we're missing a basic building block component, uvm_sequence_router. -Ryan 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.