In reply to chr_sue:
I am clarifying by questions:
Driver is one which converts the inputs into pin wiggles. I have all tasks(with suitable pin wiggling format) for my design. I have to call those tasks based on the sequence. Tasks can be reset task or scan in task or scan out task etc… I have decide which task to call based on the sequence items
For example
If I want to do reset, following is the order of that things follow
a)set the reset signal 1 in the sequence.
b) Driver receives the sequence items. Now I need to interpret the received sequence item so that I call reset task so that reset signal is sent in required protocol. I implemented this by adding new sequence item called command whose value is set based on the sequence. In this case command=“RESET_SEQ”. Based on the received command, I call suitable tasks
Questions:
- is the above approach ok ? is this the normal way of communicating between driver and sequences ? I can figure out the number of agents or any thing needed for the environment.
2)Other than randomizing the inputs in the required fashion , are there any advantages of defining new sequences ? I understand that sequences are portable and other advantages of laying the sequences etc