thanks for your comments.
Please find my answers below:
Are you calling get_config_int in the driver before getting the sequence/scenario item? (In other words, are you trying to get ENABLE before it has been set).
NO...first I am getting the item & then looking for get_config_int as follows:
Have you set the length of the request fifo in the scenario driver to a value greater than 1? Since `apply_send_with does not wait for a response from the driver, this would overwrite the value of ENABLE before the driver could read it.
I don't have any request FIFO as I am using the get_next_item() call for pulling the transaction item.
Please clarify me on this.
Please find some code details & help me in this regard.
In my sequence's run task body:
In my scenario's run task body:
In my scenario_driver/sequence_driver:
if(enable_driver == 0)
this_trans.addr = default_addr;
//else it will be the constrained value by Inline constraint i.e this_trans.addr is used
//Now apply this_trans to my pin level interface of DUT through task calls
Here my issue is "SEQUENCE" is working as per my expectation.
ENABLE-->1 ==> use the laddr vaue for trans1;
ENABLE-->0==>use the default value for trans2.
but "SCENARIO" is NOT working as expected.
In case of scenario, my first set_config_int for ENABLE with value "1" is always overrided by the following set_config_int for ENABLE with value "0".
Hence always ENABLE is "0' for both trans1 & trans2 ==> using default value for addr.
NOTE: Default value for enable_driver is "0".
Am I clear enough?