Implementing ScanWorks’ new I2C
action will be easy for users of ScanWorks who are familiar
with the flash programming action because the two types
of actions are very similar. From the I2C dialog box,
the target device is selected and assigned a model definition.
Next, an I2C bus address is defined and either “program”
and/or “verify” are selected. At this point,
a source file with data can be imported and incorporated
into the ScanWorks I2C action or a link can be included
in the I2C action, connecting the action to a source
data file in binary, S-record or Intel Hex format. ScanWorks
automatically determines the most efficient boundary-scan
access when the action is built. Once a ScanWorks I2C
action has been created, it can be included in a sequence
or called from a ScanWorks application programming interface
(API) just like any other ScanWorks action.
When a source file is imported into
the action, the same data will be written to the memory
device whenever the action is run. If the action is
linked to a source file, the contents of the source
file can be modified so that unique data is written
each time the action is executed. A ScanWorks script
action will automate this process by automatically requesting
user input to modify the contents of the source file
for each board. The script routine can be embedded in
a ScanWorks test sequence prior to the execution of
the I2C action or it can be included in a custom test
procedure.
The I2C action is included with all
ScanWorks development stations at no additional cost.
New Design Browser
The latest version of the InterComm
Design Browser (5.1) by OHIO Design Automation has been
incorporated into ScanWorks 3.4. InterComm is a graphical
design-oriented interface that’s based on information
from electronic design automation (EDA) equipment such
as schematics and layouts. With a design browser interface,
ScanWorks users are able to easily and graphically correlate
boundary-scan test information and design data. InterComm
also allows personnel who do not have access to an EDA
system to quickly browse intelligent schematic and printed
circuit board (PCB) design data and effectively communicate
design issues.
Version 5.1 of InterComm has significant
new and valuable features for ScanWorks users, including
a new format for EDA data which allows faster access
and shortens the loading of data from schematic and
layout files. EDA files can be imported directly by
ScanWorks from the major computer aided design (CAD)
tools or they can be exported from InterComm for use
by ScanWorks.
For detailed information about the
new features and benefits of InterComm 5.1, visit the
OHIO Design Automation web site at www.ohio-da.com.
Web conferences are regularly scheduled to demonstrate
the use of InterComm. In addition, introductory and
informative videos can be downloaded from the site.
New Script Actions
Actions based on Java Script (JScript)
or Visual Basic scripts can now be included in ScanWorks
sequences or they can be called from any ScanWorks API.
ScanWorks’ easy-to-use integrated process automation
scripting capability simplifies the test development
flow and facilitates communications within the organization.
Scripting is based on familiar test control languages,
including Tcl and Perl, and now JScript and Visual Basic.
Scripting relieves engineers from many tedious tasks
involving data gathering, data preparation, data logging
for further analysis and data updates. In addition,
scripting can interface ScanWorks with other applications
in the organization and automatically communicate test
results or consolidate certain follow-on steps in the
process that are dependent upon test results.
With the new capabilities of ScanWorks
3.4, Visual Basic and JScript routines can be applied
to the design that is currently active within ScanWorks.
In addition, a Visual Basic or JScript routine can be
initiated from within ScanWorks and perform operations
external to ScanWorks. Examples of this might be turning
on a power supply or reading measurements from external
instrumentation.
Moreover, ScanWorks 3.4 has a new command
line utility under its Tools menu. The command line
can be used to execute any script operation from within
ScanWorks. After the script has run on the design that
is currently active in ScanWorks, the design is reinitialized
and reset to its default. Any Windows-compatible command
can also be executed without leaving ScanWorks.
Automatic UUT Detection
The new automatic UUT detection feature
in ScanWorks 3.4 can be very valuable when several versions
of a design are being tested or when second-sourced
boundary-scan devices have been implemented in a design.
This new feature allows a ScanWorks 3.4 Manufacturing
Station to automatically find the correct design definition
file for the UUT that is currently connected to the
station. The operator simply requests that ScanWorks
retrieve the design file. ScanWorks then queries the
UTT by performing a non-intrusive scan of the BYPASS
and IDCODE registers, and compares this data with information
stored in each design file.
The automatic UUT detection feature
saves manufacturing production time by quickly finding
and loading the appropriate design file for the operator,
but it also reduces the risk of possible damage to the
UUT that could result by mistakenly running the wrong
boundary-scan tests on a certain version of the design.
License Handling Features
ScanWorks 3.4 has several new unique
features that help users get the most value from their
ScanWorks licenses. For example, with the automatic
license release feature a license administrator can
set parameters that control how long a ScanWorks system
will be inactive before its license is released and
made available to other users. In this way, managers
can make efficient use of resources around the world.
A test engineer in China, for instance, might forget
to close ScanWorks before leaving for the weekend. The
automatic license release feature would return the license
to the administrator and inform the engineer when he
returns. Then the engineer can choose to request access
to a ScanWorks license to continue working or he can
save the current state of ScanWorks and close it.
Another new license feature reserves
a license for a specific user. This can be very helpful
when access to ScanWorks is needed in an engineer’s
office, the development lab, the manufacturing floor
or other locations. A ScanWorks license can accompany
the engineer no matter where he is temporarily working.
ScanWorks’ User Access Control
option and network licensing is required for both of
these new license handling features.
Other New Features
ScanWorks 3.4 has several other new
features, including the following:
- Support for FabMaster netlist formats
- New Process Automation Scripting
functions
- New ScanWorksAPI functions
- Importing power and ground information
from similar designs
For more information on ScanWorks 3.4,
click
here.
|