Prior to creating a test program flow with tests that contain patterns there is what is commonly referred to as the 'test list'. This test list is commonly stored in Excel or as Jira tickets, and it determines what is run through simulation or emulation prior to first silicon. Given all of the test pattern generation capabilities of Origen, users must deal with this test list in some manner. I don't see any IP or top level $dut modeling for tests that would yield an API like this:
$dut.ddr.has_tests? # => true
$dut.ddr.tests # => [:ddr4_2133_dataeye, :ddr4_1867_dataeye]
Anyone who is creating patterns with Origen, can you explain how Origen interacts with your 'test list'?
thx
We don't tend to handle that in the model, see the comments about lists here: http://origen-sdk.org/origen//guides/pattern/running/?highlight=list