Test System Concurrency via Flow Domain Site Regions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The complexity of testing semiconductor devices with multiple cores poses challenges in configuring test systems for concurrent testing, leading to inefficient utilization of tester resources and difficulties in programming and configuring test systems to support concurrent execution of test blocks across multiple cores.
Innovation Solution
The definition of flow domains and the use of site regions within the test system allow for flexible allocation of resources, enabling any degree of concurrency in testing functional regions, even without specific preparation for concurrent execution, by mapping tester sites to cores and executing test blocks in a manner that optimizes resource usage across multiple tester sites.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If test blocks are executed concurrently to reduce test time, then productivity improves, but device complexity increases due to resource conflicts and configuration complexity
Solution Approach 1:
The patent segments the test system into multiple tester sites, where each tester site is assigned to test a specific core. This segmentation allows independent configuration and execution of test blocks at each site, enabling concurrent testing while reducing overall system configuration complexity by localizing resource management.
Solution Approach 2:
The patent introduces an intermediary mechanism that automatically maps tester sites to cores and manages resource allocation. This intermediary handles the complexity of concurrent test block execution by automatically resolving resource conflicts and coordinating timing, allowing users to benefit from concurrent testing without manually managing the complexity.
2Productivity
If multiple tester sites are used to test multiple cores concurrently, then productivity improves, but ease of operation deteriorates due to programming complexity
Solution Approach 1:
The patent implements self-service functionality where the test system automatically performs site-to-core mapping and resource allocation based on simple user inputs. The system self-configures the concurrent test execution environment without requiring complex programming, allowing users to initiate concurrent testing with minimal configuration effort.
Solution Approach 2:
The patent creates a universal tester site configuration that can be applied to test different cores with similar architectures. A single tester site design serves multiple purposes across different cores, reducing the programming complexity required to set up concurrent testing by reusing standardized configurations.
3Productivity
If tester resources are allocated to multiple tester sites for concurrent testing, then productivity improves, but resource utilization efficiency deteriorates
Solution Approach 1:
The patent implements dynamic resource allocation where tester sites can be dynamically assigned to different cores based on test requirements and resource availability. This dynamic assignment optimizes resource utilization by matching resource capabilities with specific test needs, preventing waste while maintaining high test throughput through concurrent execution.
Solution Approach 2:
The patent allows dynamic adjustment of test parameters such as timing, signal levels, and resource allocation based on real-time test conditions. By changing these parameters adaptively during concurrent testing, the system optimizes resource utilization efficiency while maintaining high productivity across multiple tester sites.
Data Source
AI summary
Techniques for configuring a test system that enable simple specification of a degree of concurrency in testing separate functional portions of a semiconductor device. For a test flow with multiple sub-flows, the pins accessed in connection with each sub-flow may define a flow domain. Site regions, each associated with a flow domain, may be defined. Tester sites may be associated with each of these flow domain specific site regions and independently operating resources may be assigned to these tester sites. A second portion of the defined site regions may be associated with tester sites, but resources assigned to these site regions may be accessed from multiple flow domains. Test blocks, even if not developed for concurrent execution, may be executed concurrently using resources in the flow domain specific site regions. Flexibility is provided to share resources through the use of the second portion of the site regions.