Remote Diagnostics Display – ScanExpress Runner

Introduction
Corelis ScanExpress Runner software includes a hidden remote diagnostic display feature that allows the user to view the results of a previous test failure. This feature is most useful when you need to view test diagnostics but either do not have the hardware available or do not want to rerun the test. In fact, our tech support and applications engineers use this feature all the time to assist with problems around the globe.

Required Files
ScanExpress Runner generates a result file for each test step that fails. The result file, along with the original test step, allows ScanExpress Runner to recreate the test results and diagnostics.

There are two types of result files—one for infrastructure type tests, and one for interconnect type tests.

The required infrastructure test files are:

• CVF file – This file contains the infrastructure test vectors. This file is generated by ScanExpress TPG using the Infrastructure button selection and the file name has the ‘_inf.cvf’ suffix.
• CRF File – This file contains the results of the infrastructure test and the file name has the ‘_inf.crf’ suffix. This file is created only in the case of an infrastructure test failure. If the infrastructure test passes, this file is not created and attempting to remote diagnosing the test always results in a Run Error (further explained later in the document).

In order to simulate interconnect type test steps (interconnect, buswire, memory, pull/pull-down, & cluster), the following two files are required:

• CVF file – This file contains the test vectors that were generated by ScanExpress TPG. The file name must have one of the following suffixes: ‘_int.cvf’, ‘_bus.cvf’, ‘_mct.cvf’, ‘_pull.cvf’, ‘_ct.cvf’
• RES file – This file contains the results of the test step. Suffixes: ‘_int.res’, ‘_bus.res’, ‘_mct.res’, ‘_pull.cvf’, ‘_ct.res’.

Viewing Remote Diagnostics
Viewing remote diagnostics is just like running a test. Once invoked, ScanExpress Runner will go through the internal run process and use the existing results instead of the JTAG controller.

To run the test in remote diagnostics mode, simply depress the CTRL and ALT keys simultaneously and click the R key once. You will see the prompt below.

In order to proceed, dismiss the message box by selecting Append or Overwrite. Pressing Cancel terminates the simulation.

The test plan will execute in the same way it would on hardware. Runner will display the test results (including ADO if licensed) in the test results windows.

Note: Passing test steps will not generate the required remote diagnostics files. These test steps may show a “Run Error” when executed in remote diagnostics mode.

Conclusion
Remote diagnostics are a handy way to examine, troubleshoot, and diagnose test failures without the UUT. There’s no need to tie up a lab or production station—simply transfer the files over to your office station with Runner and perform in-depth failure analysis at your leisure.