Compact representation of vendor hardware module revisions in an open architecture test system

• US 8,214,800 B2
• Filed: 03/02/2005
• Issued: 07/03/2012
• Est. Priority Date: 03/02/2005
• Status: Expired due to Fees

• Current Assignee: Advantest Corporation
• Original Assignee: Advantest Corporation
• Inventors: Pramanick, Ankan, Elston, Mark, Adachi, Toshiaki
• Primary Examiner(s): Zhen, Wei
• Assistant Examiner(s): Chen, Qing
• Application Number:
  US11/070,957
• Publication Number:
  US 20060200816A1
• Time in Patent Office: 2,680 Days
• Field of Search: 717/100, 717120-135, 717/170
• US Class Current: 717/120
• CPC Class Codes: G01R 31/31907 Modular tester, e.g. controlling and coordinating instruments in a bus based architecture

Abstract

Method and system for associating software components with vendor hardware module versions in an open architecture test system are disclosed. The method includes receiving a set of hardware versions of a vendor hardware module, receiving a set of software components supported by the vendor hardware module, processing the set of hardware versions, where the set of hardware versions is represented as an equivalence class of hardware version numbers using a mask value, obtaining user choices of hardware versions of the vendor hardware module, validating the user choices of hardware versions of the vendor hardware module, and creating a system profile in accordance with the user choices of hardware versions.

Claims

1. A method, executed by a computer, for associating software components with vendor hardware module versions in an open architecture test system, wherein the open architecture test system comprises a System Controller, one or more Site Controllers, one or more vendor hardware modules, and one or more devices-under-test (DUTs), comprising:

receiving a set of hardware versions of a vendor hardware module;

processing the set of hardware versions of the vendor hardware module, wherein a mask value representing an equivalence class of hardware version numbers is generated based on the set of hardware versions of the vendor hardware module, wherein the mask value comprises a mask and a masked number, wherein the mask is a data pattern within the range of the set of hardware versions of the vendor hardware module, and wherein the data pattern comprises at least a don'"'"'t-care bit and an unmasked bit;

obtaining user choices of hardware versions of the vendor hardware module;

validating the user choices of hardware versions of the vendor hardware module;

creating a system profile in accordance with the user choices of hardware versions of the vendor hardware module;

receiving a new hardware version of the vendor hardware module, wherein the new hardware version of the vendor hardware module is a member of the equivalence class of hardware version numbers; and

testing the new hardware version of the vendor hardware module using the system profile.

2. The method of claim 1, wherein processing the set of hardware versions of the vendor hardware module comprises:

specifying the equivalence class of hardware version numbers in accordance with the mask and the masked number.

3. The method of claim 2, wherein specifying the equivalence class of hardware version numbers comprises:

for each don'"'"'t-care bit in the mask, masking the corresponding bit in the masked number, thereby indicating that all members of the equivalence class of hardware version numbers have either a 1 or 0 in the corresponding bit position; and

for each unmasked bit in the mask, using the corresponding bit in the masked number in the equivalence class of hardware version numbers, thereby indicating that the corresponding bit in the masked number is not masked.

4. The method of claim 2, wherein validating the user choices of hardware versions of the vendor hardware module comprises:

if a user choice is covered by the mask value, identifying an entire equivalence class of hardware version numbers corresponding to the mask value as being chosen.

5. The method of claim 4, wherein validating the user choices of hardware versions of the vendor hardware module comprises:

for each user choice of hardware version of the vendor hardware module, representing the user choice of hardware version of the vendor hardware module as valid if and only if a bitwise-AND of the user choice of hardware version of the vendor hardware module and the mask equals to the masked number.

6. The method of claim 1, wherein creating a system profile comprises:

receiving a set of software components supported by the vendor hardware module;

determining a set of compatible software components in accordance with the user choices of hardware versions of the vendor hardware module and the received set of software components;

selecting a version of software component for each user choice of hardware version of the vendor hardware module;

creating a list of user selected software components for each user choice of hardware version of the vendor hardware module; and

storing the list of user selected software components.

7. The method of claim 6, wherein the set of software components comprises:

one or more vendor software development kits;

one or more user software development kits; and

one or more vendor driver software versions corresponding to the set of hardware versions of the vendor hardware module.

8. The method of claim 6, wherein selecting a version of software component comprises:

querying a user to choose a version of software component from the set of compatible software components; and

for each user choice of the version of software component, computing an intersection, across the user choices of hardware versions of the vendor hardware module, for generating a list of supported hardware versions.

9. The method of claim 8, wherein computing an intersection comprises:

computing resulting mask using the user choices of hardware versions of the vendor hardware module; and

computing resulting masked number using the user choices of hardware versions of the vendor hardware module.

10. An open architecture test system, comprising:

one or more computers implementing;

a System Controller;

one or more Site Controllers coupled to the System Controller;

one or more vendor hardware modules coupled to a Site Controller;

one or more devices-under-test (DUTs) coupled to a vendor hardware module in parallel;

means for receiving a set of hardware versions of a vendor hardware module;

means for processing the set of hardware versions of the vendor hardware module, wherein a mask value representing an equivalence class of hardware version numbers is generated based on the set of hardware versions of the vendor hardware module, wherein the mask value comprises a mask and a masked number, wherein the mask is a data pattern within the range of the set of hardware versions of the vendor hardware module, and wherein the data pattern comprises at least a don'"'"'t-care bit and an unmasked bit;

means for obtaining user choices of hardware versions of the vendor hardware module;

means for validating the user choices of hardware versions of the vendor hardware module;

means for creating a system profile in accordance with the user choices of hardware versions of the vendor hardware module;

means for receiving a new hardware version of the vendor hardware module, wherein the new hardware version of the vendor hardware module is a member of the equivalence class of hardware version numbers; and

means for testing the new hardware version of the vendor hardware module using the system profile.

11. The open architecture test system of claim 10, wherein the means for processing the set of hardware versions of the vendor hardware module comprises:

means for specifying the equivalence class of hardware version numbers in accordance with the mask and the masked number.

12. The open architecture test system of claim 11, wherein the means for specifying the equivalence class of hardware version numbers comprises:

for each don'"'"'t-care bit in the mask, means for masking the corresponding bit in the masked number, thereby indicating that all members of the equivalence class of hardware version numbers have either a 1 or 0 in the corresponding bit position; and

for each unmasked bit in the mask, means for using the corresponding bit in the masked number in the equivalence class of hardware version numbers, thereby indicating that the corresponding bit in the masked number is not masked.

13. The open architecture test system of claim 11, wherein the means for validating the user choices of hardware versions of the vendor hardware module comprises:

if a user choice is covered by the mask value, means for identifying an entire equivalence class of hardware version numbers corresponding to the mask value as being chosen.

14. The open architecture test system of claim 13, wherein the means for validating the user choices of hardware versions of the vendor hardware module comprises:

for each user choice of hardware version of the vendor hardware module, means for representing the user choice of hardware version of the vendor hardware module as valid if and only if a bitwise-AND of the user choice of hardware version of the vendor hardware module and the mask equals to the masked number.

15. The open architecture test system of claim 10, wherein the means for creating a system profile comprises:

means for receiving a set of software components supported by the vendor hardware module;

means for determining a set of compatible software components in accordance with the user choices of hardware versions of the vendor hardware module and the received set of software components;

means for selecting a version of software component for each user choice of hardware version of the vendor hardware module;

means for creating a list of user selected software components for each user choice of hardware version of the vendor hardware module; and

means for storing the list of user selected software components.

16. The open architecture test system of claim 15, wherein the set of software components comprises:

one or more vendor software development kits;

one or more user software development kits; and

one or more vendor driver software versions corresponding to the set of hardware versions of the vendor hardware module.

17. The open architecture test system of claim 15, wherein the means for selecting a version of software component comprises:

means for querying a user to choose a version of software component from the set of compatible software components; and

for each user choice of the version of software component, means for computing an intersection, across the user choices of hardware versions of the vendor hardware module, for generating a list of supported hardware versions.

18. The open architecture test system of claim 17, wherein the means for computing an intersection comprises:

means for computing resulting mask using the user choices of hardware versions of the vendor hardware module; and

means for computing resulting masked number using the user choices of hardware versions of the vendor hardware module.

19. A method, executed by a computer, for representing vendor hardware module versions in an open architecture test system, wherein the open architecture test system comprises a System Controller, one or more Site Controllers, one or more vendor hardware modules, and one or more devices-under-test (DUTs), comprising:

receiving a set of hardware versions of a vendor hardware module;

processing the set of hardware versions of the vendor hardware module, wherein a mask value representing an equivalence class of hardware version numbers is generated based on the set of hardware versions of the vendor hardware module, wherein the mask value comprises a mask and a masked number, wherein the mask is a data pattern within the range of the set of hardware versions of the vendor hardware module, and wherein the data pattern comprises at least a don'"'"'t-care bit and an unmasked bit;

obtaining user choices of hardware versions of the vendor hardware module;

validating the user choices of hardware versions of the vendor hardware module;

receiving a new hardware version of the vendor hardware module, wherein the new hardware version of the vendor hardware module is a member of the equivalence class of hardware version numbers; and

testing the new hardware version of the vendor hardware module using the equivalence class of hardware version numbers.

20. The method of claim 19, wherein a mask value representing an equivalence class of hardware version numbers comprises:

for each don'"'"'t-care bit in the mask, masking the corresponding bit in the masked number, thereby indicating that all members of the equivalence class of hardware version numbers have either a 1 or 0 in the corresponding bit position; and

for each unmasked bit in the mask, using the corresponding bit in the masked number in the equivalence class of hardware version numbers, thereby indicating that the corresponding bit in the masked number is not masked.

21. The method of claim 19, wherein validating the user choices of hardware versions of the vendor hardware module comprises:

for each user choice of hardware version of the vendor hardware module, representing the user choice of hardware version of the vendor hardware module as valid if and only if a bitwise-AND of the user choice of hardware version of the vendor hardware module and the mask equals to the masked number; and

if a user choice is determined to be valid, identifying an entire equivalence class of hardware version numbers corresponding to the mask value as being chosen.