In reply to warnerrs:
You don’t have to use a configuration object.
How and when are you setting REQ_NUM_WORDS to 803,900 in your driver? You don’t show it.
According to your log, at the time your driver calls set() REQ_NUM_WORDS is 0. You must be changing the value after that.
But before you try to fix that, you really shouldn’t have a component setting a value in a sibling component, it’s not good encapsulation. In other words, REQ_NUM_WORDS should be a field in your agent, and it should propagate it down to both the driver and monitor. This is fine if you have a single value like this, but if you have more than a couple, a configuration class makes more sense.
Sorry, i have not yet completed the coding part. Below is the intent.
REQ_NUM_WORDS represents packet size. I want to send faulty packets(sending the packets with less or more than the standard size). The packet size is set by the sequence and i have added a field in the seq_item. Using this field REQ_NUM_WORDS(packet size), the driver generates cs(chip_select) accordingly.
And i wanted this info to be passed onto monitor too so that the monitor would take appropriate action.
Yes, REQ_NUM_WORDS might change dynamically throughout the test.
Will try the option mentioned by you,. Thank you!