P1450.4 Test Program Flow Assumptions
• Flow constructs are owned / developed / implemented by
Test or Test Development (TD) Engineering group
• Usually TD engineering has developed test methodologies
for specific IC capabilities
• Test methodologies can / should have “libraries” or
templates of TestMethods and flows to apply the standard
suite of tests for given IC capabilities
• Reuse and pre-defined test sets are common and desired by
TD engineering
Test Program Flow Constructs Organization
• Top-level STIL Constructs
–
–
–
–
TestMethod definitions
TestModule definitions
SubFlowModule definitions
Entry Objects definitions
• “Environment-level constructs
– Top-level TestProgram “container”
– EntryPoint declarations or references
– Flow hierarchy references
Diagram of Flow Constructs within STIL
Standard Libraries via Includes
(could be blocked like MacroDefs)
STIL
1450.0
constructs/defs
EntryPoint defs
Environment
TestMethod defs
TestProgram “Char”
TestProgram “WS”
TestModule and
SubFlowModule
defs
TestProgram blocks can align with
CTL “configuration/TestMode blocks
TestProgram “FinalTest”
TestProgram “LabATE”
TestProgram blocks
contain references to
EntryPoints, TestModules
And SubFlowModules
Mock Up STIL File with TestProgram Flow Constructs:
Top Segment
Mock Up STIL File with TestProgram Flow Constructs:
TestModuleDefs and EntryPointDefs Segment
Mock Up STIL File with TestProgram Flow Constructs:
Environment/TestProgram Segment
Contrast with CTL Extension Assumptions
• There are several “owners” and uses with CTL data
– IP Core providers: Define Core test methodology – provide “test” data to
the boundary of the Core (for integration to full chip by EDA tools)
– EDA tools: Use CTL from Core provider for inclusion and integration of
Core into full SoC chip. As part of integration, these tools regenerate the
CTL to make test data relate to the boundary of the SoC
– Test generation tools (where needed) use the full SoC CTL/STIL data to
generate tester-ready files
• High level of Reuse is assumed for test data… reconfigurable per-use
via the EDA integration process
CTL Extension Construct Mechanisms Used
• DomainNamed CTL constructs used for reconfigure/reuse
of test data
– SignalGroup and pattern protocol constructs are vehicles
• Multiple CTL blocks used within the P1450.1 Environment
block, each for different Test Method / configuration /
Core instance grouping
• DomainNamed blocks generated by EDA integration tools
and referenced by CTL configuration “reference” blocks.
These DomainNamed blocks reside at the top STIL level
and not within the CTL blocks. This promotes reuse.