Decide and implement to allow users to have multiple devices in the testing environment.
An example would be using a decoder with outputs that are required for the DUT testing.
Option1
Extend use of terminals to allow for multiple pins and have module patterns. The module patterns are so that the module can also be "evaluated" similar to the DUT. This would have to be combined with more complex "pin linking" (assigning 1 net to another without having a terminal) and pin exclusivity / bus definitions.
An example of pin exclusivity: only 1 (or specified number) pin of specific type.)
An example of bus definitions: going from a DUT with an output of DATA to a module with D_data where x changes with part. It should be able to scan, and assign based on rules. (ex: Data<3:0> to D_data<5:0> fill the other bits with specified default)
ex:
term: "Decoder"
pins:
pattern: "EN"
pattern_mod: "EN"
pattern: "DATA"
pattern_mod: "D_data"
Option2
Create a modules section where a new DUT is specified and placed using the same conventions as terminals but separated into a new class (or using a broken up schematic class) for less complexity in the terminals class less restructuring of schematic/terminal classes.
Decide and implement to allow users to have multiple devices in the testing environment.
An example would be using a decoder with outputs that are required for the DUT testing.
Option1
Extend use of terminals to allow for multiple pins and have module patterns. The module patterns are so that the module can also be "evaluated" similar to the DUT. This would have to be combined with more complex "pin linking" (assigning 1 net to another without having a terminal) and pin exclusivity / bus definitions.
An example of pin exclusivity: only 1 (or specified number) pin of specific type.) An example of bus definitions: going from a DUT with an output of DATA to a module with D_data where x changes with part. It should be able to scan, and assign based on rules. (ex: Data<3:0> to D_data<5:0> fill the other bits with specified default)
ex:
term: "Decoder" pins:
pattern: "EN" pattern_mod: "EN"
pattern: "DATA" pattern_mod: "D_data"
Option2
Create a modules section where a new DUT is specified and placed using the same conventions as terminals but separated into a new class (or using a broken up schematic class) for less complexity in the terminals class less restructuring of schematic/terminal classes.
Schematic->Module->Terminal