The Debug Interface: Revision Date: 8/08

1 The Debug Interface
Revision Date: 8/08

In this chapter... ■ Overview, 1-2
■ Materials Needed to Begin, 1-4
■ Board Debug Process, 1-6
■ Using the Debug Interface, 1-8
■ Features of the Debug Interface, 1-12
■ BT-BASIC Commands in the Debug Interface, 1-22
■ Log Files, 1-24
This chapter gives an overview of the debug features on

the Medalist ICT system, and describes the board debug
process.
© Agilent Technologies 2008 Test Development Process: Debug Tests 1

Overview
Overview This chapter describes the Debug Interface for When you save the changes made during debugging, the
debugging tests on the Medalist i3070 systems (both debug software automatically compiles the test source
UnMux and Mux platforms). and updates the wirelist and testorder file. For more
information about using the Debug Interface, see Board
The Debug Interface allows you to evaluate, debug, and
Debug Process.
fine-tune:
■ pins and shorts tests AutoDebug capabilities
■ unpowered analog in-circuit tests (capacitors, An alternative to manually adjusting the tests is to allow
diodes, FETs, fuses, inductors, jumpers, the AutoDebug utility to automatically debug analog
potentiometers, resistors, switches, transistors, in-circuit tests, reducing the time it takes to get the tests
and zeners) into production.
■ Agilent VTEP v2.0 and TestJet tests AutoDebug provides the following features:
■ debugs unpowered analog devices (capacitors,
NOTE diodes, FETs, fuses, inductors, jumpers,
The debug software helps you to fine-tune the potentiometers, resistors, switches, transistors,
tests in the selected board directory but does not and zeners)
allow you to add devices or change device types.
■ allows you to set the minimum stability
To do so, use the Debug Interface on the UnMux
requirement for tests during debugging
system or Board Consultant on the Mux system.
■ provides a highly flexible rule editor to customize
the debugging rules to suit your test requirements
Use the debug software to quickly run and locate failing
tests, then adjust them so that they pass. The software
will:
■ execute specified tests
■ perform statistical analysis on the results
■ display the information for you to evaluate
■ allow you to modify test parameters and see the
results

Overview
Auto Optimizer
You can use the Auto Optimizer utility to fine-tune
analog in-circuit tests to improve throughput wherever
possible. A rule editor allows you to adjust the
optimization parameters.
NOTE
To run Auto Optimizer, all the control cards in
your system must be ControlXTP Cards.

Materials Needed to Begin
Materials Needed to Before debugging a testplan: The default location for the board directory is under the
directory.
Begin ■ Verify that the test fixture was built and wired
$AgilentICT_ROOT/boards
correctly (see Build and Verify the Fixture). If you place your board directory in a location other than
the default directory, you have to ensure that users are
■ Have at least one known good board for
granted full access rights to that directory.
debugging. Using several boards to evaluate and
debug the tests helps ensure success during 1 In Windows Explorer, right-click on the board
production testing. directory you are using and select Properties.
■ License files for the test system and any optional 2 Select the Security tab and click Add (Figure 1-1).
features you intend to use must be present on the
test station. Figure 1-1
■ If using AutoDebug, ensure that values for
variable components on the known good board
have been set.
Move Board Directory to Test Station

If test development was done on a developer’s
workstation, transfer the board directory to the test
station for debugging.
■ Use a tar utility to archive the board directory.
Then transfer it to the test station and extract the
board directory. Use this option when you have to
transfer files to a system that is not on a network.
■ On the UnMux system, you can click the
Administrator button on the toolbar and transfer
the board directory using the Copy Board Directory
function. (For more information, see
Administrator Utilities.)

Materials Needed to Begin
3 Type Everyone and click OK (Figure 1-2). Figure 1-3
Figure 1-2
4 Select Everyone and select Full Control in the

Permissions box (Figure 1-3). Click Apply.
5 Click OK to close the dialog box.

Board Debug Process
Board Debug Board debugging consists of the following steps: 10 Debug analog functional and mixed tests.
Process 1 Debug Pins Tests. Evaluate the analog functional and mixed tests, and
use Pushbutton Debug to debug the tests that are
2 Debug Pre-shorts Tests.
marginal or failing.
3 Debug Shorts and Opens Test.
To launch Pushbutton Debug, select Pushbutton
4 Debug Analog In-circuit Tests. Debug from the Launch menu.
The Debug Interface provides the tools to help you in In Pushbutton Debug, use the Analog and Digital
debugging the above tests. The Debug Flowchart options on the Mode menu to switch between analog
shows the typical debugging steps for these tests. and digital sources when debugging a mixed test that
uses both.
An optional step is to run the Auto Optimizer on
passing tests to improve throughput. See Auto For information about analog functional and mixed
Optimizer. testing, refer to Chapter 4, Analog Functional and
Mixed Testing in Analog Testing.
5 If VTEP or TestJet tests are used, also debug them
using the Debug Interface as described in Debug 11 Run Board Test Grader to evaluate how well tests
VTEP or TestJet Tests. are working and determine fault coverage of the
tests.
6 Turn on DUT power supplies and adjust the power
supply current limit. When board debugging is successfully completed,
perform the final step: Release to Production.
7 Debug digital tests using Pushbutton Debug. See
Debugging Digital Tests.
Debug Flowchart
For information about digital testing, refer to Digital
Testing. Figure 1-4 shows the typical debug workflow in the
Debug Interface.
8 If Boundary-Scan tests are used, debug them using
Pushbutton Debug. See Debugging Boundary-Scan
Tests in the Boundary-Scan Guide.
9 If Cover-Extend tests are used, debug them using
Pushbutton Debug. See AutoDebug (ADB) for
Cover-Extend Tests in Pushbutton Debug.

Board Debug Process
Figure 1-4 Debug flowchart
Start
RUN ALL AIC Sort failed tests
Pins Test
Do you want
Yes to Auto Debug
Pre-shorts Test
all tests?
Select all failures

Shorts Test No
Run Auto Debug

Is test a
Yes
marginal failure?
Yes Tests pass? No
No
No Select marginal failure

End Check physical board
and schematics devices and run
Auto Debug
Investigate problem Any problem with

and if necessary Yes physical board or Tests pass?
change board schematics?
No
Rerun Auto Debug

(change Auto Debug
parameters if needed)
Manually change test

No Tests pass?
options & parameters
Comment out tests No Tests pass?

Yes
Yes
Yes
End

Using the Debug Interface
Using the Debug This section describes some common tasks in the Debug Tasks in the Debug Interface
Interface. For a list of the menu options in the Debug
Interface Interface, see Debug Interface Menus and Toolbar.
• Opening a Board Directory for Debugging
• Editing and Restoring Tests
Logging In to the Debug Interface
• Editing Tests in Multiple Board Versions
• Locating a Device
Your administrator will provide a user name for you to • Sorting the Data
log in to the Debug Interface. • Launching Other Applications
1 At the test station, launch the Medalist ICT software
by clicking its icon on the desktop.
The Operator Interface is displayed. This restricted
environment allows an operator to load and run
testplans.
2 Log in by selecting Actions > Login (or pressing F9),
and entering your username and password.
The Debug Interface is displayed. Once you have
logged in, you can switch between the debug,
developer, and operator interfaces using the buttons
on the toolbar. Log out (Actions > Logout) when you
have completed your debug tasks.

Opening a Board Directory for Debugging Editing and Restoring Tests

A board directory is automatically loaded (based on the
Editing a Test
Autofile configuration1) when you place a fixture and
board on the system and click the LOAD button in the Changes to the test and measurement options are made
Operator Interface. in the device panel:
If Autofile loading fails, manually load the board ■ In columns where changes can be made, click the
directory from the Debug Interface, by selecting File > check box to turn the option on and off, or click in
Open. Then select the board directory and click OK to a cell to enter text. If a menu is provided, make
open it. your selection from the menu.
■ You can select multiple cells in a column (for
Multiple Board Versions
example, Remark) for editing. Right-click on any
If the board directory supports multiple board versions, of the selected cells and select the editing function
the base version is automatically loaded. To load (for example, Mass Edit) from the menu. The text
another version for debugging, select it from the or selected option will be applied to all the
drop-down menu on the toolbar. selected cells.
A grey background indicates that changes were
Multiple-board Panels
made to the value in the cell during the current
If you are working with a multiple-board panel, the session.
individual boards can be selected from the drop-down
menu on the toolbar. Restoring a Test
Figure 1-6 shows a board directory opened in the Changes made while debugging can be undone.
Debug Interface. Navigate through the sections of the
■ To undo the last operation, click the Undo button.
board directory by clicking on the device types in the
Continue clicking to undo actions in reverse order.
component navigation panel on the left. Details will
appear in the device panel on the right. ■ To undo a specific change, right-click on the
changed value and select Restore from File.
1 The Autofile code, assigned during board development, identifies the fixture when it is loaded onto the testhead and
enables the appropriate board directory to be automatically loaded.

Editing Tests in Multiple Board Versions A board version is defined by specifying its differences
from a base version. When debugging, you can define a
If the board directory supports multiple board versions, new version for a device by right-clicking on it and
select the board version for debugging from the selecting Create New Version (Figure 1-5). This option
drop-down menu on the toolbar. is available if the version of the device is not the same as
the current board version.
Figure 1-5
board version
selected device
is currently same
as base version
new version of
device defined

Locating a Device
The Find function lets you find a device quickly. Press
Ctrl-F (or select Edit > Find Device) to enter text and find
devices names beginning with the search text.
Drop-down lists let you filter the search results by Type
(e.g. Resistor) and Status (e.g. Fail). To view the details
of any of the devices found, double-click on it. The
device will be highlighted in the device panel.
You can also use the ICT Browser to pinpoint the actual
location of the device on the board. Click the Browser
button to see a graphical display of the features on the
board and fixture. See The ICT Browser for more
information.
Sorting the Data

You can do the following:
■ Change the order of the columns in the table by
dragging the column headers.
■ Sort the table by any column, by clicking on the
column header.
Launching Other Applications

You can also launch other board test applications from
the Debug Interface. These applications can be found on
the Launch menu. For more information, see Other
Board Test Applications.

Features of the Debug Interface
Features of the This section describes the features of the Debug

Interface and the options on the menus and toolbar.
Debug Interface
Figure 1-6 Debug Interface

Table 1-1 Features of the Debug Interface
Name Description
1, 2 Menu bar, toolbar The functions on the menus and toolbar are described in detail in Debug Interface
Menus and Toolbar.
3 Component navigation Lists the sections of the board directory. Move the cursor over the sections to see test
panel statistics for each device type. The icon beside each section shows its test status:
Critical errors (for example, the source file cannot be compiled).
The section contains one or more failed tests.
One or more tests have not been run in this section.
All the tests in the section have passed.
The section contains one or more commented tests.
The section is empty for this board.
Click on a device type to display the test details in the device panel. Any initialization that
needs to be done prior to running the tests will be performed when the device type is
selected.
4 Testhead execution queue Lists the tests currently queued at the testhead and indicates whether each test is run
manually or invoked by AutoDebug. You can remove selected tests or pause and continue
test execution using the buttons provided.
5 Output panel Shows BT-BASIC output and print statements.
6 Command line Allows you to run BT-BASIC commands. Type the command and press Enter. See
BT-BASIC Commands in the Debug Interface for a list of commands that can be used.
7 Buttons beside command Executes the testhead is 1 command (gains control of the testhead resources).
line Executes the testhead is * command (releases control of the testhead resources).
8 Status line Shows the status as you perform actions and execute commands.
9 Device panel Lists the tests for the selected type of device. Test details and results are shown in one or
more panels, depending on the device type.

Table 1-1 Features of the Debug Interface
Name Description
10 Board version selection Lets you select a different board version for testing, if the board directory support multiple
board versions.
11 Board selection Lets you select a different board for testing, on a multiple-board panel.
Debug Interface Menus and Toolbar File Menu
In the Debug Interface, the functions are provided on the Use the File menu to open a board directory, save
following menus: changes, or exit the program.
■ File Menu
■ Edit Menu Table 1-2 File menu options
■ View Menu Menu Item Description
■ Actions Menu
Open Opens a board directory.
■ Launch Menu: Launch other board test
Reopen Opens a recently used board directory.
applications. For information, see Other Board
Select it from the list provided.
Test Applications.
■ Help Menu: View the online help. Save Saves the test source files and test order
file; also recompiles the test objects if
The Toolbar provides shortcuts to frequently used necessary.
functions.
Exit Exits the program.

Edit Menu
The Edit menu contains editing and search functions.
Table 1-3 Edit menu options
Menu Item Description

Undo Lets you undo the last operation.
(To undo a specific change, right-click on the changed value and select Restore from File.)
Redo Lets you redo the last operation.
Preferences Lets you set the following preferences:
• In the Engineer Test tab, select the default Column Name Format. Column names in the
device table can be long or short. For example, selecting Short displays "ad" and selecting
Long displays "Adjust".
• In the Vacuum tab, if you are testing a multiple-board panel, you can specify the vacuum
system to be activated for each board.
• In the Test Time tab, choose whether to display a column showing test times for analog
in-circuit tests.
Link Links selected tests. Select a test and click Link. In the dialog box that appears, select the tests
to be linked and click OK.
The test source files are linked. When a change is made, the linked files are updated as well as
the corresponding object files.
Unlink Unlinks selected tests. Select a test and click Unlink. In the dialog box that appears, select the
tests to be unlinked and click OK.

Table 1-3 Edit menu options
Menu Item Description

Find Device Lets you search for a particular device. You can filter the search results by Type (e.g. Resistor)
and Status (e.g. Fail).
In the Find Device dialog box, enter the text to search for and click Find. All device names that
start with the search text will be displayed. To view the details of any of the devices found,
double-click on it. The device will be highlighted in the device panel.

View Menu
Use the View menu to show or hide the toolbar and
selected panels.
Table 1-4 View menu options
Menu Item Submenu Item

Toolbar Standard Toolbar
Engineer Component Navigation
Test Execution Panel
Test Output Panel

Actions Menu
Use the Actions menu to execute tests, start AutoDebug,
and control the testhead.
Table 1-5 Actions menu options
Menu Item Submenu Item Description

Logout Log out of the Debug Interface.
AutoDebug Run Performs AutoDebug on the selected tests.
Rule Editor Defines the AutoDebug rules. For details, see Customizing AutoDebug.
Optimize Run Runs Auto Optimizer on analog in-circuit tests.
Rule Editor Sets parameters for the Auto Optimizer. For details, see Customizing Auto
Optimizer.
Verify Fixture Checks the wiring of the test fixture using the verify all statement. See
Verifying the Fixture.
All MUX Cards Automatically checks the mux card wiring, filter circuit, and orientation of the
VTEP or TestJet probes. See Verifying the Mux Cards.
VTEP/TestJet Checks the wiring and DC operation of each VTEP or TestJet probe. See
Verifying the VTEP/TestJet Probes
Learn Capacitor Compensation Measures the capacitance of the system and fixture.

Table 1-5 Actions menu options
Menu Item Submenu Item Description

Testhead Power On Boots up the testhead.
Power Off Shuts down the testhead.
Is 1 Gains control of the testhead resources.
Is * Releases control of the testhead resources.
Fixture Lock Pulls the fixture down onto the testhead.
Fixture Unlock Releases the fixture from the testhead.
Vacuum On Turns the vacuum on to pull down the board.
Vacuum Off Turns the vacuum off to release the board.
Execute Test Run Executes the selected tests. You can select the device type in the
component navigation panel to run all the tests in the device family, or select
individual tests in the device panel.
Run Till Fail Start - Executes the test until the first failure occurs or, if the test does not
fail, to the end of the test.
End - Stops execution.
Run N Times Executes the test a predefined number of times.

Toolbar
The toolbar provides quick access to some of the
options on the menus.
Table 1-6 Buttons on the toolbar
Button Description
Operator Launches the Operator Interface.
Engineer Test Launches the Debug Interface.
Developer Launches The Developer Interface (in the UnMux system development environment only).
Administrator Launches the Administrator Utilities (in the UnMux system development environment only).
Undo Lets you undo the last operation.
Redo Lets you redo the last operation.
Save Saves the changes made.
Run Executes the selected tests.
You can select the device type in the component navigation panel to run all the tests in the device family,
or select individual tests in the device panel.
AutoDebug Runs AutoDebug on the selected tests. See AutoDebug on page 4-2.
You can select the device type in the component navigation panel to run all the tests in the device family,
or select individual tests in the device panel.
Auto Optimize Runs Auto Optimizer on analog tests. See Auto Optimizer on page 4-23.
iVTEP Run AutoDebug with both VTEP and iVTEP. See Debugging Agilent VTEP or TestJet Tests.

Table 1-6 Buttons on the toolbar
Button Description
Browser Displays the board graphics. See The ICT Browser.
Run All AIC Runs all unpowered analog tests currently listed in the Debug Interface, and reports the failures. This
option uses the object files and is faster than using the Run option, which recompiles the test source.
However, note that it will only report failures.

BT-BASIC Commands in the Debug Interface
BT-BASIC Table 1-7 lists the BT-BASIC commands that can be

used in the command line of the Debug Interface. For
Commands in the details about these commands, refer to Syntax
Debug Interface Reference.
Table 1-7 BT-BASIC commands in Debug Interface
autoadjust off dutfailed msi$ report using

autoadjust on fabon panelfailed revision$
autofile faon/faoff powered rli$
Basic;win fbon/fboff print testhead cleanup
boardfailed fcdon print using testhead configuration
buffered reporting on/off fcon/fcoff printer is testhead is
cat fdon/fdoff pwd testhead power
check board filter off/on quick report testhead status
check boardxy fixture lock report th$
clear nrun fixture unlock report clear time$
clear dutfailed list object report is unpowered
compile list source report level is vacuum well
datetime$ lli$ report out

BT-BASIC Commands in the Debug Interface
filter off/on
The test development software automatically filters the
commands you enter in the command line, and will only
allow the commands listed in Table 1-7 to run.
The filter off command turns off this checking and
enables you to run other commands from the command
line. The filter on command turns on automatic
filtering again.
CAUTION
; Ifthatyouaresetnot supported byandtheexecute

filter off commands
test development
software, you could cause the software to fail.

Log Files
Log Files If you encounter problems when running the test

development software, the following log files (found in
Agilent_ICT\log) may help to determine the cause.
■ Agilent_ICT_<username>.log
Logs the Medalist ICT applications that are

running, and any application exceptions.
■ rmiserver_<username>.log
Indicates if there are any problems with the RMI

server connection.
■ startupRmi.ksh_<username>.log
Logs the activities when the RMI server is started.

Log Files

The Debug Interface: Revision Date: 8/08

Uploaded by

Copyright:

Available Formats

The Debug Interface: Revision Date: 8/08

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

The Debug Interface: Revision Date: 8/08

Uploaded by

Copyright:

Available Formats

1 The Debug Interface

Revision Date: 8/08

■ Materials Needed to Begin, 1-4

■ Board Debug Process, 1-6

■ Using the Debug Interface, 1-8

■ Features of the Debug Interface, 1-12

■ BT-BASIC Commands in the Debug Interface, 1-22

■ Log Files, 1-24

This chapter gives an overview of the debug features on

© Agilent Technologies 2008 Test Development Process: Debug Tests 1

© Agilent Technologies 2008 Test Development Process: Debug Tests 2

© Agilent Technologies 2008 Test Development Process: Debug Tests 3

Move Board Directory to Test Station

© Agilent Technologies 2008 Test Development Process: Debug Tests 4

3 Type Everyone and click OK (Figure 1-2). Figure 1-3

4 Select Everyone and select Full Control in the

5 Click OK to close the dialog box.

© Agilent Technologies 2008 Test Development Process: Debug Tests 5

© Agilent Technologies 2008 Test Development Process: Debug Tests 6

Figure 1-4 Debug flowchart

RUN ALL AIC Sort failed tests

Select all failures

Run Auto Debug

Yes Tests pass? No

No Select marginal failure

Investigate problem Any problem with

Rerun Auto Debug

Manually change test

Comment out tests No Tests pass?

© Agilent Technologies 2008 Test Development Process: Debug Tests 7

© Agilent Technologies 2008 Test Development Process: Debug Tests 8

Opening a Board Directory for Debugging Editing and Restoring Tests

© Agilent Technologies 2008 Test Development Process: Debug Tests 9

© Agilent Technologies 2008 Test Development Process: Debug Tests 10

Sorting the Data

Launching Other Applications

© Agilent Technologies 2008 Test Development Process: Debug Tests 11

Features of the This section describes the features of the Debug

© Agilent Technologies 2008 Test Development Process: Debug Tests 12

Table 1-1 Features of the Debug Interface

© Agilent Technologies 2008 Test Development Process: Debug Tests 13

Table 1-1 Features of the Debug Interface

Debug Interface Menus and Toolbar File Menu

© Agilent Technologies 2008 Test Development Process: Debug Tests 14

Table 1-3 Edit menu options

Menu Item Description

© Agilent Technologies 2008 Test Development Process: Debug Tests 15

Table 1-3 Edit menu options

Menu Item Description

© Agilent Technologies 2008 Test Development Process: Debug Tests 16

Table 1-4 View menu options

Menu Item Submenu Item

© Agilent Technologies 2008 Test Development Process: Debug Tests 17

Table 1-5 Actions menu options

Menu Item Submenu Item Description

© Agilent Technologies 2008 Test Development Process: Debug Tests 18

Table 1-5 Actions menu options

Menu Item Submenu Item Description

© Agilent Technologies 2008 Test Development Process: Debug Tests 19