1.Is there any perfect way to verify the design using RAL?
2.Can anyone give me some critical scenarios which can be found using RAL only?
3.How can we use value,m_desired,m_mirrored properties in reg_field at their best?because except set() method ,almost all methods are making both desired,mirrored values equal by implicitly calling predict() method.
You can suggest me if there is any source that can clear my doubts.
Thanks
SATYA
In reply to SATYA369:
As with any methodology, there is no perfect way or thing you can do that cannot be done another way, except maybe the time and effort it takes you.
In reply to SATYA369:
1.Is there any perfect way to verify the design using RAL?
2.Can anyone give me some critical scenarios which can be found using RAL only?
3.How can we use value,m_desired,m_mirrored properties in reg_field at their best?because except set() method ,almost all methods are making both desired,mirrored values equal by implicitly calling predict() method.
Finding bugs in a design is always application specific. Status registers play aspecial role. They might containspecific values set by the design. Then thes registers and their values have to be checked.
Status registers might influence the output values of your DUT. Then the scoreboard has to consider these register values using the RAL.
These are only 2 simple scenarios.