Highlights


 Supports the following
 system platforms:

 Sun Solaris
    (2.6 and higher)
 Linux
    (kernel 2.4 and higher)
 Windows NT
    
TPA ( Test Program Analyzer ) Tool for comparing ATE test programs, with TPA it is possible to monitor and detect changes in an ATE test program.

Customer who wanted to be able to monitor the ATE program being used on the production floor.
To be able to check if there had been any significant changes made to the production program -
effectively to see if the "golden" program issued to production had been changed in any way.

The Output is detailed log file with the differences between the two test programs.


Most of the challenges related to proper handling of test programs and tester resources.
The challenges related to the test engineering and management tasks such as:

  • Control Test Program release and version
  • Control remote Test Program usage
  • Monitoring on changes in the test which may have been introduced in remote locations or by subcontractors
  • Monitoring test program release to production
  • Ability to relate device faults to the correct test program revision.



  • TPA highlights the following differences between the two TP:

    Differences in Pin configuration file
  • Added/removed pins
  • Pin name vs tester channel mapping
  • Pin groups added/removed/modified

  • Differences in Level file
  • Added/removed/modified level equation set
  • Level set
  • Specs Parameter values

  • Differences in Timing file
  • Added/removed/modified (equation set, timing set , spec sets )
  • Parameter values


  • Differences in Pmf file
  • Added/removed binl file

  • Differences in TestFlow file
  • Added/removed tests
  • Changes in test numbers assignment ,Testflow flags, test suite flags, system flags
  • Testflow variables (added/removed/modified)
  • Binning modifications
  • Changes in primaries (timing/level/vector) for every testsuite and more.

  • Differences in Patterns file
  • Patterns pins data
  • Patterns size

  • Output Parameters:
  • File highlighting all the checks being done, including warning + changes.
  • File with a summary of the modifications done. This should include useful information such as testsuite name, level set/spec, etc, related to that.
  • Particular change summary to screen.


  • Highlights
    • analysis is context sensitive.
    • results reported in a meaningful, understandable way.
    • Test program elements check.

    Back to top
    Concept of Test Program Analyzer:

    Test Program Analyzer

    Back to top
    Event driven to Tester Simulation results -
    WGL/STIL ATPG to Tester -
    Verification of test program before silicon -
    Simulate a test program -
    Simulation Data processing -
    VCD/EVCD files to tester files -
     new
    Directly extract timing into WaveWizard Constructs -
    Suite of tools enables users to expand use of STIL - new