1 / 8

P1450.4 Test Program Flow Assumptions

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

neena
Download Presentation

P1450.4 Test Program Flow Assumptions

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 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

  2. 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

  3. TestProgram “Char” TestProgram “WS” TestProgram “FinalTest” TestProgram “LabATE” 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 TestModule and SubFlowModule defs TestProgram blocks contain references to EntryPoints, TestModules And SubFlowModules TestProgram blocks can align with CTL “configuration/TestMode blocks

  4. Mock Up STIL File with TestProgram Flow Constructs: Top Segment

  5. Mock Up STIL File with TestProgram Flow Constructs: TestModuleDefs and EntryPointDefs Segment

  6. Mock Up STIL File with TestProgram Flow Constructs: Environment/TestProgram Segment

  7. 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

  8. 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.

More Related