ScanWorks^® JTAG Interconnect Development Station Bundle

Creating Tests

Test creation in ScanWorks is semi-automated. Each type of test is organized as an “Action”. The different types of tests include scan path verification, interconnect tests, PLD programming, I2C programming, custom tests using ScanWorks macros and Boundary Scan Language (BSL) files, Serial Vector Format (SVF) tests, plus the optional memory access verification and flash programming. Multiple actions of each type can be created and saved for each design.

Each action is created through an intuitive user interface designed specifically for that action. The organization and format of the dialog box is consistent across all actions, making them easy to learn and use. Because most of the information needed to create a test is already available in the design description, the initial test can usually be built with one click of a button. Report logs indicate any errors or warnings that must be resolved. The test developer is given options to modify the test for increased coverage or to adjust the test for special circumstances. ScanWorks’ test coverage reports help you determine where additional coverage is needed and how to implement the additional coverage. Also, tests can be applied directly from the development dialog so they can be validated rapidly against the hardware. You can also set preconditions to initialize your design for testing and select the scan path for testing if more than one is available.

For more information on each test type, see Interconnect Development Station Tests on Page 4.

Deployment to Manufacturing

Once tests have been created, they must be organized into a logical sequence for effective PCB testing. For prototype debugging and low volume applications, ScanWorks provides a simple operator user interface to control the application of test sequences. The sequence can be automatically created from the test actions created for the design. Later, sequences can be modified to set flow control options or to change the order in which the tests are applied. ScanWorksAPI allow your tests to be easily integrated into the most prevalent test methods such as LabView, TestStand, Agilent VEE, Visual Basic, or any language that supports Microsoft COM. With ScanWorks API, you can create your own sequence of actions or apply a sequence that was previously created in ScanWorks. An Interconnect Development Station can be used as a manufacturing station, but a more economical alternative would be to move the tests to the more cost-effective ScanWorks Manufacturing Station. The complete test set-up can be moved to manufacturing by exporting a single compressed file containing all the data needed for testing and then importing this file onto a manufacturing station.

Previous : Next                   Page 3 of 8          Back to Page 1