boardconvert tool

© Agilent T 9-1

� Bookshelf� Syntax Reference� Master Index� Table of Contents

In this sion Tool is also used to transfer board etween 3070 controllers with same or

erating systems:

to MS Windows

indows to UNIX

indows to MS Windows (when board ories are in different path locations on ent controllers) See the Advice on page 9-19 hy UNIX to UNIX transfers are not mended.)

processing editing will be required if:

ries are not contained within (local to) the directory.

files outside the board directory or ENT3070_ROOT/standard directory are ed.

tandard peripherals not defined in MS ows have been used in UNIX files or vice .

echnologies 2002 Test Development Tools

9 Agilent Conversion Tool

chapter... � Running the Conversion Tool, 9-4

� Troubleshooting Problems, 9-38

� What the Conversion Tool Does, 9-42

� Post-Conversion File Cleanup, 9-52

The Agilent Conversion Tool is used to convert the ASCII (American Standard Code for Information Exchange) text files in a board directory for cross-platform compatibility between UNIX and MS Windows operating systems.

Text files contained in the boards directory are merged into a single compressed file. The executable files are regenerated by IPG Test Consultant.

NOTE

The default location for the board directory is $AGILENT3070_ROOT/boards/<BoardName>. The board directory may not be in the default location on your controller. Change the directory path as required where /boards/<BoardName> is used in this document.

The Converdirectories bdifferent op

� UNIX

� MS W

� MS Wdirectdifferfor wrecom

Some post-

� Libraboard

� Other$AGIL

requir

� Non-sWindversa

© Agilent T 9-2

Chapter 9 � Bookshelf� Syntax Reference� Master Index� Table of Contents

inish reading this chapter, you should be orm the following tasks:

ert a board directory from an UNIX ller to an MS Windows controller.

ert a board directory from an MS Windows ller to an UNIX controller.

a board directory between MS Windows llers when the board directories are on

ent drive letters or paths (for example C:\ to

e and resolve issues resulting from ences between UNIX and MS Windows ting systems and 3070 software directory ures.

tes

begin using this chapter, you should:

a board directory that contains a testplan, and appropriate files that have been iled on software revision 3070 04.00pa or

le to run IPG Test Consultant and fix errors. ore information, see Chapter 1, Agilent IPG onsultant..


: Agilent Conversion Tool

If post-processing is not needed, Running the Conversion Tool is the only section of this document you will need to read.

NOTE

VisTA (Visual Test Advisor) functional testplans cannot be converted using the Conversion Tool. An error message will result if you attempt to convert a VisTA board directory.

NOTE

Resolving issues related to board directory conversion requires 3070 user training and an understanding of the functionality of IPG Test Consultant.

It may also require an understanding of the board being converted as well as any customization which has occurred during board development.

NOTE

For simplicity, the terms “directory” or “subdirectory” are used for both UNIX and MS Windows in this chapter. “Folder” and “subfolder” could have been used.

Objectives

When you fable to perf

� Convcontro

� Convcontro

� MovecontrodifferD:\).

� Locatdifferoperastruct

Prerequisi

Before you

� Havetests, complater.

� Be abFor mTest C

© Agilent T 9-3


st Consultant to completion on the 070_ROOT/boards/class_bd. It will pass nsultant after it compiles the libraries, etc.

ENT3070_ROOT/standard/tutorial

s_bd directory will NOT pass IPG Test ltant until moved to the correct location and est Consultant is run. You may use IPG Test ltant, Management, Copy/Move Board

tory, then modify the permissions, if needed. ore information, see Chapter 1, gement Menu.



� Know the locations of board directories on both operating systems.

� Have enough disk space: Three times the board directory size on the source controller and four times the board directory size on the destination controller. Disk space requirements are verified before execution of the Conversion Tool.

� Know the remote logins, controller names or IP addresses and passwords of both the source and destination controllers to transfer files to or from your controller via FTP.

Required Tools and Materials

To accomplish the tasks in this chapter, you will need:

� A 3070 board test system with a testhead with 3070 04.00pa software (UNIX or MS Windows)

� A functional board directory compiled using 3070 04.00pa software (UNIX or MS Windows)

Practicing a Conversion

If you want to practice a conversion of the class_bd directory documented in this chapter, you can copy the class_bd with subdirectories from:

$AGILENT3070_ROOT/standard/tutorial/class_bd

to

$AGILENT3070_ROOT/boards/class_bd

Run IPG Te$AGILENT3

IPG Test Co

NOTE

$AGIL

/clas

ConsuIPG TConsuDirecFor mMana

© Agilent T 9-4


RunniConve

files are modified directly. It also adds the e common delimiter statement to the config file.re for ECO: Takes an interoperable board

ory, flips the source text files, and modifies w files in preparation for an ECO.og: Used to view resulting log files or other les.: Aborts the Package or Extract process e it has completed.

tails what the Conversion Tool is doing, see of the differences between the two operating cribed in the section Relevant Differences NIX and MS Windows Operating Systems 3.

onversion Tool operates in a copy of the directory. It does NOT modify an existing directory during Package, Make operable, or Prepare for ECO. During ct, if a board directory of the same name , it can replace the board directory after pting the user for approval.



ng the rsion Tool

NOTE

Software revision 3070 04.00p or newer must be installed and the source board directory must pass IPG Test Consultant before running the Agilent Conversion Tool.

The Conversion Tool main screen has the same file menu and buttons in both UNIX and MS Windows; therefore, only one version (UNIX) is shown in this document except where appropriate.

The Conversion Tool consists of these functions:

� Package: Merges and compresses all of the boards/<BoardName> directories text files into a single <BoardName>.cvt file that can be copied to another controller and extracted.

� Transfer: Used to transfer files using FTP (file transfer protocol) to another ftp server-enabled controller.

� Extract: Extracts (uncompresses) a packaged <BoardName>.cvt file in a platform-dependent manner.

� Make Interoperable: This function is a combination of Package and Extract. The Make Interoperable function makes a copy of the board directory, takes the runtime test objects and makes them interoperable. It deletes the objects, makes modifications, and recompiles the source files. . This operation is much quicker on MS Windows

as theenabl

board� Prepa

directthe ra

� View Ltext fi

� Abortbefor

For more dea summary systems desBetween Uon page 9-4

NOTE

The CboardboardInterExtraexistsprom

© Agilent T 9-5


the Conversion Tool icon on the MS ows desktop.

Start, Programs, Agilent3070, Conversion

T-BASIC Window, type execute l.ksh &” (Not case sensitive and is run in ckground)

orn Shell window, type ctool.ksh & (Not ensitive and is run in the background)

t Conversion Tool main screen, shown in on page 9-6, will start.



ADVICE

To streamline board directory conversion, you may want to use the IPG Test Consultant Management, Clean Up Board Directory, Mark to remove unneeded backup files.

NOTE

Binary files are not packaged or converted. (<filename>.o, etc.) They are recreated during the Extract process.

Start the Conversion Tool

In the UNIX environment, there are several ways to start the Conversion Tool:

� From a user1 login, on the Agilent3070 Programs popup list, click Agilent Conversion Tool.

� In a BT-BASIC Window, type execute “cTool.ksh &” (Case sensitive and is run in the background)

� In Shell Window, type cTool.ksh & (Case sensitive and is run in the background)

In the MS Windows environment, there are also several ways to start the Conversion Tool:

� ClickWind

� ClickTool

� In a B“ctoo

the ba

� In a Kcase s

The AgilenFigure 9-1

© Agilent T 9-6


Figure 9



-1 Agilent Conversion Tool Main Screen

© Agilent T 9-7


Packa is not a Conversion Tool batch mode ble because IPG Test Consultant should be ring the conversion process and IPG Test ltant is not a batch mode tool.

testplan file, user modifications to the an are preserved. Path names and file names odified to be operating system specific

OT run the Conversion Tool against a copy r board directory with a different board

. For example, don’t copy <BoardName> to oardName>. The board name of the ds/<BoardName> is referenced in the re/fixture file and is used during IPG onsultant program execution. If a re.o exists, IPG Test consultant does not

ile the /fixture/fixture file and create a ixture.o file.

sion Tool will use the $AGILENT3070_ROOT t variable when converting board



ge Locate the Board Directory

1 Select the package function from the File menu, Package, or by clicking the Package button. The package process defaults to the $AGILENT3070_ROOT/boards directory.

The Package screen, shown in Figure 9-2 on page 9-9, will appear. The factory default location for board directories is:

� UNIX: /var/hp3070/boards

� MS Windows: C:/Agilent3070/boards

As described in Navigation on page 9-8, you can use this screen to locate ../boards/<BoardName> directories. In this example, the <BoardName> in the boards directory is class_bd. This is a board directory used for training in the Agilent 3070 training class.

A backup directory called <BoardName>.migration_backup/<BoardName> is created by the Conversion Tool.

NOTE

Thereavailarun duConsu

NOTE

In thetestplare m

NOTE

Do Nof youname<NewB

/boarfixtu

Test Cfixtu

compnew f

The Converenvironmendirectories.

© Agilent T 9-8


ist - Not functional

etails - Not functional

OT select anything except a directory which ins board files and directories. If you do, a ing message will result which says This not appear to be a valid board

tory, continue? Normally, click Cancel.

ctory can be packaged, but if the board does not compile with IPG Test Consultant, esults will also not compile.

e <BoardName> subdirectory. Click Package. IPG Test Consultant dialog box shown in -3 will be displayed.



Navigation

Select the board directory containing the <BoardName> you want to package.

Notice the navigation buttons at the top of the Package screen. Their operation is similar to the MS Windows file manager. Their functions are:

� Look in:

Lists the subdirectories to the root. Allows you to navigate to any mounted volumes in UNIX and any drive letters, mapped or physical, in MS Windows.

� Up One Level - Goes up one subdirectory level

� Home - Goes to Home Directory. This may be on a different drive or mounted volume.

� New Folder - Creates a new subdirectory in the current directory called New Folder in MS Windows and NewFolder in UNIX.

To rename this folder in UNIX use the mv NewFolder <BoardName> command and in MS Windows use the File Manager Rename command.

NOTE

Spaces in file or directory names in board directories are not allowed.

� L

� D

NOTE

Do NcontaWarndoes

direc

Any diredirectoryExtract r

2 Select thThe RunFigure 9

© Agilent T 9-9




Figure 9-2 Select the boards/<BoardName> subdirectory

© Agilent T 9-10


ibes how to run the Conversion Tool without Test Consultant during packaging.

un IPG Test Consultant

onfident that the board directory will pass nsultant, click No.

No, a second dialog box indicating that there Test Consultant regeneration problems, and ay not build correctly on the destination appear as shown in Figure 9-4.

Are you sure you don’t want to run IPG Test Consultant?

o continue or No to stop the Conversion select Yes:

y subdirectory in the board directory _directory will be created and a copy of ame> will be copied into it.



Figure 9-3 Run IPG Test Consultant?

Check Board Directory Status?

Even if you have run IPG Test Consultant using software revision 3070 04.00pa, it is recommended that you allow IPG Test Consultant to do a check of the ../boards/<BoardName> status before the packaging.

Yes - Run IPG Test Consultant

If you click Yes, a subdirectory in the board directory <BoardName>.migration_backup/<BoardName> will be created and a copy of the <BoardName> will be copied into it. Copying large board directories and files can take several minutes. Be patient.

Packaging will begin and Agilent IPG Test Consultant screens will be displayed.

If you clicked Yes, go to How to Run IPG Test Consultant on page 9-12. Skip the following section,

which descrrunning IPG

No - Do Not R

If you are cIPG Test Co

If you clickmay be IPGthe board msystem will

Figure 9-4

Select Yes tTool. If you

A temporarmigration

the <BoardN

© Agilent T 9-11


Packaged board file location and name



Because packaging a large board directory and files can take several minutes, a dialog box indicating the need for patience will appear. The dialog box will go away when copying is complete.

A progress dialog box will appear. While the progress bar is displayed, you can Abort. If you abort packaging, you must start packaging from the beginning.

When packaging is complete, the <BoardName>.cvt file will be written in the directory one level up from the ../<BoardName> being packaged. In the default file structure, this will be the /boards directory.

If a <BoardName>.cvt file with the same name exists, you will need to approve removing and replacing it. If you say No, packaging will stop. You will need to remove the previous <BoardName>.cvt file manually.

When packaging is complete, the location and board name dialog box will be displayed as shown in Figure 9-5. The Conversion Tool will also display information about the package process, and show when the board packaging was completed, with a time stamp, as shown in Figure 9-6 on page 9-12.

Figure 9-5

© Agilent T 9-12


PG Test Consultant

ng the Conversion Tool, it will be You will need to navigate in IPG Test



Figure 9-6 Package complete screen.

Packaging without running IPG Test Consultant is complete; go to Transfer on page 9-19.

How to Run I

When runniinteractive.

© Agilent T 9-13


Consultant will check the status of the rectory. You may have to bring the IPG Test nt screen to the front to view the IPG Test nt Messages screen.

e board directory doesn’t have errors. As Figure 9-9 on page 9-16, the result should

ACTIONS WERE PERFORMED BY IPG ONSULTANT ***

ilent IPG Test Consultant by selecting File,

p 5 page 9-17.



Consultant to the directory where the ../<BoardName> resides. See Chapter 1, Agilent IPG Test Consultant, for navigation information.

NOTE

Package will always run against a copy of the boards/<BoardName> directory. Because the directory name for the board is referenced by IPG Test Consultant, an interim directory is created called:

<BoardName>.migration_backup

Contained in the <BoardName>.migration_backup directory will be the <BoardName> subdirectory.

1 Select the $AGILENT3070_ROOT/boards /<BoardName>.migration_backup/<BoardName>

directory, as shown in Figure 9-7 on page 9-14.

For the class_bd example, select /var/hp3070/boards/class_bd.migration_back

up/class_bd/

Select Actions, Develop Board Test.

2 Do a Comprehensive Regeneration as shown in Figure 9-8 on page 9-15.

Select Actions, Begin Batch Development.

3 IPG Testboard diConsultaConsulta

Verify thshown inbe:

*** NO TEST C

4 Close AgExit.

Go to ste

© Agilent T 9-14




Figure 9-7 IPG Test Consultant - Develop Board Test

© Agilent T 9-15




Figure 9-8 IPG Test Consultant - Batch Development

© Agilent T 9-16




Figure 9-9 IPG Test Consultant - Packaging a board without errors

© Agilent T 9-17


age 9-34, for more information on how to e <BoardName>_package.log file.

will appear. The dialog box will go away ng is complete.

dialog box will appear. While the Progress yed, you can Abort. If you abort Packaging, art Packaging from the beginning.

aging is complete, the <BoardName>.cvt written in the directory one level up from the me> directory being packaged. When the ctory paths are used, this will be the /boards



5 If IPG Test Consultant returned errors or performed any compiles, the package result probably has problems as described in Figure 9-10.

You can review the results of the packaging process in the <BoardName>_package.log file. See View

Log on preview th

Figure 9-10 Package Results - continue or fix errors?

If there are IPG Test Consultant compiles or other errors, it is strongly recommended that IPG Test Consultant be run again on the original board directory. Click No. Then fix the problems before running Package again.

If there were no compiles or other errors, click Yes; packaging will begin. Several dialog boxes will appear:

Because copying large board directories and files can take several minutes, a dialog box indicating the need

for patiencewhen copyi

A progress bar is displayou must st

When Packfile will be /<BoardNa

default diredirectory.

© Agilent T 9-18


Relevant Differences Between UNIX and ws Operating Systems on page 9-43.



If a <BoardName>.cvt file with the same name exists, you will need to approve removing and replacing it. If you say No, packaging will stop. You will need to remove the previous <BoardName>.cvt file.

When packaging is complete, the location and board name dialog box will be displayed, as shown in Figure 9-11. The Agilent Conversion Tool will also display information about the package process, and show when the board packaging was completed, with a time stamp, as shown in Figure 9-6 on page 9-12.

Figure 9-11 Package board location and name

The <BoardName>.cvt file is a compressed file containing all of the ../<BoardName> directories text files. It has the same contents whether created from an UNIX or an MS Windows operating system.

The Extract function will make the operating system- dependent changes required to address the differences

described inMS Windo

© Agilent T 9-19


TransfE

the Conversion Tool can be especially l for transferring files between MS Windows llers where the 3070 software is on different rives or board directory paths.

ment controller has the MS Windows 3070 ater software on one drive C:/Agilent3070 ction system has it on another drive, for /Agilent3070, the Extract function has the f determining where the 3070 software is g the $AGILENT3070_ROOT environment d extracting correct file paths.



er Transfer is used to transfer <BoardName>.cvt files to another 3070 controller with the FTP Server enabled.

NOTE

You can Extract the <BoardName>.cvt file in the board directory on the originating system, but it will overwrite the existing /<BoardName> directory. If you choose to do that, you may want to make a backup of the boards/<BoardName> files and directories in another location. A warning message is displayed before the original board directory is removed.

The compressed <BoardName>.cvt file can be transferred to another UNIX or MS Windows 2000 controller and extracted (uncompressed) on that system.

FTP server functionality is enabled on the MS Windows 2000 controllers as configured from Agilent.

FTP, in UNIX or MS Windows, requires a password on the destination system. Anonymous FTP is not enabled on either UNIX or MS Windows 2000, as configured from the factory.

ADVIC

Usingusefucontrohard d

If a develop04.00pa or land a produexample D:capability oloaded, usinvariable, an

© Agilent T 9-20


to the board directory.

t the desired <BoardName>.cvt file, as Figure 9-12.



Transfer Files to a Controller with the FTP Server Enabled (UNIX or Windows 2000)

To transfer a file:

1 Select File, Transfer or click Transfer.

2 Navigate

3 Highlighshown in

Figure 9-12 Select the <BoardName>.cvt file for transfer

© Agilent T 9-21


FTP login dialog box

e data transfer is complete, the FTP session out of the destination controller.

message will be displayed if transfer errors transfer errors occur, contact your system rator.



4 Click FTP. The FTP dialog box, shown in Figure 9-13 on page 9-21, will be displayed.

a Fill in the User Name, and User Password.

Passwords must be established on the destination controller.

b Fill in the FTP Host field. If the FTP Host in a different domain, the domain name will be required. The FTP Host IP address may be used.

c Fill in the FTP Host path. The environment variable will not work with FTP.

d Select either the:

Default UNIX Path

Default Windows path

or enter your board directory path.

The default UNIX path is /var/hp3070/boards/ and the default Windows path is /Agilent3070/boards/.

Click Help for more path information.

e Click Put File.

Figure 9-13

5 When thwill log

An erroroccur. Ifadminist

© Agilent T 9-22


a 3rd party software package on the MS ows machine (Reflection FTP, Hummingbird are, etc.). With MS Windows 2000, FTP can abled.

ing a DAT tape on the UNIX machine and ing it on the MS Windows machine or vice . A DAT tape drive is included on the MS ows controller in a 3070 testhead.

s for moving files between MS Windows without the FTP server enabled include:

the FTP put command on the source ine to an interim UNIX machine, then using P get command on the destination MS

ows machine to pull the file.

network file sharing, i.e., Windows rer, Tools, Map Network Drive.

hardware solutions including DAT tape, zip CDs, etc.

ng files as a mail file attachment (verify that e size is acceptable)

E

dName>.cvt files can be very large. Choose o transfer them carefully and always use format.



Transfer Files to a Controller without the FTP Server Enabled

CAUTION

✸<BoardName>.cvt files must be transferred in binary (not ASCII) format. If you transfer the <BoardName>.cvt file using another method other than the Conversion Tool Transfer, and the Extract on the destination controller fails because of a checksum error or a tar error occurs, try another transfer method.

MS Windows controllers without the FTP server enabled have command line file transfer protocol (ftp) as part of their operating system software. FTP is also included as part of the Korn Shell software in the 3070 04.00pa or later software.

MS Windows systems without the FTP server enabled can use FTP get to move files from and FTP put to move files to an UNIX system. For more information, in Windows Explorer, select Help, Help Topics, type ftp and click ftp utility.

Alternatives for moving files from UNIX to MS Windows without FTP the server enabled include:

� Using the FTP get command on the destination MS Windows machine to pull the file from the UNIX controller.

� UsingWindsoftwbe en

� CreatrestorversaWind

Alternativecontrollers

� Usingmachthe FTWind

� UsingExplo

� Usingdisks,

� Sendithe fil

ADVIC

<Boar

how tbinary

© Agilent T 9-23


Extrac ssful automated conversion assumes that lt locations for various elements, files, and ories have been adhered to by board opment programmers. If modifications to elements have occurred, converting the files equire more manual intervention.

sion Tool compiles in two stages:

s that are designed to preserve existing board re data. These compiles are always done and rs from these compiles will appear in the ion Tool window, shown in Figure 9-20 on 1.

ompile errors that occur during the 1st stage dversely affect 2nd stage compiles.

T-BASIC window doesn't close that tes a compile error; fix the problem before uing.

e step 1 compiles are done, IPG Test ant is started and will handle all of the other g. IPG Test Consultant will report errors compiles it is responsible for.



t The <BoardName>.cvt file created by the Package program is operating system-independent. That is the reason the program may be used to transfer files bidirectionally between UNIX and MS Windows, as between MS Windows Systems, as well as between UNIX systems.

The Extract function on the destination system makes the changes needed to resolve the differences described in the section Relevant Differences Between UNIX and MS Windows Operating Systems.

CAUTION

✸If you have renamed the <BoardName>.cvt file or changed the name during the FTP process the Extract will fail. An example of renaming a file is class_bd.cvt vs. Class_bd.cvt.

This is because the compressed file preserves the actual <BoardName> including uppercase and lowercase.

NOTE

Succedefaudirectdevelthese will r

The Conver

1 Compileand fixtuany erroConverspage 9-3

NOTE

Any cwill a

If a Bindicacontin

2 When thConsultcompilinfrom the

© Agilent T 9-24




NOTE

All Extract compiles MUST run correctly, or have the errors corrected during the Extract, for the board directory conversion to be successful.

NOTE

In the testplan file, user modifications to the testplan are preserved. Path names and file names are modified to be operating system specific

Run Extract

1 Click Extract on the Agilent 3070 Conversion Tool main screen, shown in Figure 9-1 on page 9-6.

2 Select the desired <BoardName>.cvt, as shown in Figure 9-14 on page 9-25, on the destination system. As described in the section Navigation on page 9-8, you can use the select screen to locate and select packaged <BoardName>.cvt files.

The file named <BoardName>.cvt should have been placed in the board directory, one level above the <BoardName> directory to be extracted. For example, the class_bd.cvt file, when extracted will create a subdirectory called class_bd in the /boards subdirectory.

© Agilent T 9-25




Figure 9-14 Select the <BoardName>.cvt file

© Agilent T 9-26


ControlXT Card Warning

ent IPG Test Consultant main screen, shown e 9-18 on page 9-29 will be displayed.

to the directory where your board files ormally boards/<BoardName>. Select Develop Board Test.

Test Consultant Comprehensive ation screen, shown in Figure 9-19 on 0 will be displayed.

at you are in the correct directory.

tions, Begin Batch Development. If you ou may select Begin Interactive Development rough each section.

Test Consultant Message window will he results of IPG Test Consultant, while information to the summary file in the <BoardName> directory.



3 Click Extract.

Because uncompressing large board directories and files can take several minutes, a dialog box indicating the need for patience will appear. The dialog box will go away when uncompressing is complete.

A progress dialog box will appear. While the Progress bar is displayed, you can Abort. If you abort the Extract, you must restart the Extract function from the beginning.

If a non-supported board is found in the ../boards/<BoardName>/config file, a Warning message shown in Figure 9-15 is displayed.

See Cards in the Testhead, Chapter 3, System Configuration, or Chapter 5, Configuration Reference for additional information about required hardware configurations for UNIX and MS Windows 3070 systems.

NOTE

The required boards need to be installed or the config file corrected to match existing required hardware.

Figure 9-15

4 The Agilin Figur

Navigatereside, nActions,

5 The IPGRegenerpage 9-3

Verify th

Select Acdesire, yand go th

An IPG display tsending boards/

© Agilent T 9-27


Restore the testorder file

tract is complete, the location and board log box will be displayed, as shown in -17. Select OK.

tract is complete, the <BoardName> will be written in the directory one level m the subdirectory where the ame>.cvt is located. The default location is rds subdirectory.

lent Conversion Tool will also display ion about the Extract process, and show board directory extraction was completed, e stamp, as shown in Figure 9-20 on

1.



CAUTION

✸If a BT-BASIC Windows does not close during the Extract process, an error has been found during one of the compiles that may cause the board directory conversion to fail.

Using BT-BASIC, locate and fix the error(s) before continuing the Extract

When IPG Test Consultant is complete, a message ========Ending test generation===========

will be the last message. You may have to move the IPG Test Consultant screen to see it.

6 Close IPG Test Consultant by selecting File, Exit.

7 The user will be prompted to restore the original testorder file, as shown in Figure 9-16 on page 9-27.

The programmer may have modified the default testorder on the source system, and the modified testorder should be preserved. The original testorder has been modified by Conversion Tool; all tests are marked permanent. You will almost always want to restore the original.

Select Yes.

If you select No, there is a testorder.bak file that you can mv or rename to restore the original test order.

Figure 9-16

8 When Exname diaFigure 9

When Exdirectorydown fro<BoardN

the /boa

The Agiinformatwhen thewith a timpage 9-3

© Agilent T 9-28




Figure 9-17 Extracted (converted) board location and name

9 A file named conversion.log will be created in the <BoardName> subdirectory. For example, the ../boards/class_bd directory, when converted, will have a file called conversion.log.

10 Go to View Log on page 9-34.

© Agilent T 9-29




Figure 9-18 Extract - Develop Board Test

© Agilent T 9-30




Figure 9-19 Extract - Begin Batch Development

© Agilent T 9-31




Figure 9-20 Extract results screen

© Agilent T 9-32


Make Step 3: Check board directory status?.

Conversion Complete Note with file path



Interoperable To make a board directory interoperable,

1 Select the Make Interoperable function from the Interoperability menu.

2 Browse and highlight the board directory. Select the Interop function key.

3 You will be prompted to check the board directory status with IPG Test Consultant. Select YES as recommended (shown in Figure 9-21.)

4 A copy of the board directory will be created with the file name <board_name>_interop. If you select NO, jump to Step 6. If you select NO and the Make Interoperable function has errors, you must use IPG Test Consultant to proceed.

5 Use IPG Test Consultant to confirm that the copied board directory is developed without errors.

6 Use IPG Test Consultant to complete the operation by confirming board development and recompiling the objects. When finished, you will see the Note in Figure 9-22 stating that conversion is complete. The note will indicate the location of the interoperable board directory with the file extension <board_name>_interop.

Figure 9-21

Figure 9-22

© Agilent T 9-33


Prepa



re for ECO The Prepare for ECO function takes an interoperable board directory and:

� flips the source text files, and � modifies the raw files in preparation for an ECO.

NOTE

The board directory must be interoperable in order to perform the Prepare for ECO function.

To use Prepare for ECO:

1 Select the Prepare for ECO function from the File menu, Interoperability.

2 Browse to an interoperable board directory and double click on it. Select the board you wish to prepare.

3 Select the Prepare function key. This will create a new board directory with the file extension <board_name>_ECO.

4 The Agilent Conversion Tool window will show the status of the preparation. The status will complete with an indication that the board has been prepared successfully.

© Agilent T 9-34


View L other file types, select Files of type: All *.*) in the <BoardName> directory. Of r interest to understanding the conversion re:

and summary~ (a summary and summary f the IPG Test Consultant actions).

n (UNIX and MS Windows) and n.diff (on UNIX)

ecommend that all other text files be ed using BT-BASIC.



og The View Log button may be used to view text files on the system. Multiple files may be opened simultaneously.

Select the desired file, as shown in Figure 9-23 on page 9-35.

1 Two *.log files are created by the Conversion Tool.

<BoardName>_package.log one level above the board directory.

conversion.log in the <BoardName> directory.

The conversion.log has all of the information from the <BoardName>_package.log plus the information from the Extract process appended at the end.

2 To view the <BoardName>.cvt file, select Files of type: (.cvt) one level above the board directory.

NOTE

<BoardName>.cvt files created on MS Windows controllers are ASCII text, and can be opened and searched for troubleshooting purposes in a text editor. <BoardName>.cvt files created on UNIX are compressed TAR files and will need to be uncompressed before they can be used for troubleshooting purposes.

3 To view Files (

particularesults a

summary

backup o

testpla

testpla

NOTE

It is rreview

© Agilent T 9-35




Figure 9-23 View Log

© Agilent T 9-36




NOTE

The Text Editor opened by View Log is operating system-dependent.

UNIX: Text Editor

MS Windows: Notepad

As shown in Figure 9-24 on page 9-37, the conversion.log contains a listing of the directories which were extracted, and the binary (*.o, etc.) files which were not converted. These binary files are recreated during IPG Test Consultant execution on the destination system.

There is also information about:

• Symbolic links

• Illegal file names

• Duplicate file names that would be caused by MS Windows (testorder and Testorder is legal on UX, but will cause overwriting of files on MS Windows).

• Non-default paths. For example, /user/home/<hpuxuser>

• Changes to file names with the old path names commented (!) above the new path names

© Agilent T 9-38


TroubProble

ssful automated conversion assumes that lt locations for various elements, files, and ories have been adhered to by board opment programmers. If modifications to elements have occurred, converting the files equire more manual intervention.

ving issues related to boards/<BoardName> rsion requires 3070 user training and an standing of the functionality of IPG Test ltant. It may also require an understanding board being converted, as well as any mization which has occurred during board opment.

w the Relevant Differences Between and MS Windows Operating Systems on

9-43, and keep them in mind as problems are ssed. Because of the complexity of some s, and the flexibility of the Agilent 3070 are, not all conversion problems can be ssed by the Conversion Tool software.



leshooting ms

The Agilent Conversion Tool, cTool.ksh, uses a Perl script to convert the ASCII (American Standard Code for Information Exchange) text files in the ../boards/<BoardName> directory for cross-platform compatibility.

NOTE

IPG Test Consultant using 3070 04.00pa or later software must run correctly on the source system as a first step in troubleshooting. If the source file is not correct, the converted file will not function correctly.

NOTE


NOTE

Succedefaudirectdevelthese will r

NOTE

ResolconveunderConsuof thecustodevel

General

� RevieUNIXpageaddreboardsoftwaddre

© Agilent T 9-39


ectory you are viewing which other files modified.

e original UNIX system, change the source file names to have unique file names

ut using case sensitivity, and verify that IPG onsultant compiles files correctly.

h for /dev/* files in the <BoardName>.cvt at have meaning in UNIX, but are not able to MS Windows. Resolve them by ng to a standard peripherals on the MS ows controller.

ts not found during cTool.ksh and IPG Test ltant execution will display an Error dialog

howing the file name and expected path, as n in Figure 9-25 on page 9-40. They can in two situations:

ring startup when the Conversion Tool looks IPG Test Consultant, Perl and migrate.pl.

they are not found and the user cannot find files the Conversion Tool exits.

e the file either on the 3070 MS Windows r on the UNIX system, and put it in the on displayed in the dialog box.



NOTE

<BoardName>.cvt files created on MS Windows controllers are ASCII text, and can be opened and searched for troubleshooting purposes in a text editor. <BoardName>.cvt files created on UNIX are compressed TAR files and will need to be uncompressed before they can be used for troubleshooting purposes.

CAUTION

✸Do NOT attempt to edit <BoardName>.cvt files and re-extract.

� Verify that duplicate file names, except for case (capitalization) in the UNIX system, are not causing problems.

Try Extract first and if there are errors, examine the conversion logs.

As a last resort, look through the board directory looking for file, file1, file2, etc.. You might also try opening the <BoardName>.cvt file on the destination system using a text editor and doing a wild card search for file names ending in *1*, *2*, etc. to locate potential name changes. You may also be able to determine from the file name

or dirneed

On thsystemwithoTest C

� Searcfile thapplicpointiWind

Startup

� ScripConsubox sshowoccur

• DuforIf the

LocatCD, olocati

© Agilent T 9-40


rm login, password, hostname or IP address, ath on the destination system.

that FTP works correctly from the Korn or Unix Shell window using command line ommands.

that the FTP server is enabled on the ation MS Windows 2000 controller. See you m Administrator.

w the ../boards/<BoardName> ersion.log on the destination system, g for errors or path names that may give to problem.

ully review the IPG Test Consultant errors in mmary file. They errors may give a clue the source of problems.

r message indicates it cannot find files, then

rm the location of the libraries in the s/<BoardName> under “Library Options” and the path is correct.



You may try reinstalling the software, or you can call your Agilent service and support representative.

Figure 9-25 Startup - missing files

Package

� Watch for errors in package complete screen, shown in Figure 9-6 on page 9-12). Fix the source of the errors.

� Review the ../boards/<BoardName> /_package.log on the source system, looking for errors or path names that may give clues to problem.

Transfer

� Confiand p

� VerifyShell FTP c

� VerifydestinSyste

Extract

� Revie/conv

lookinclues

� Carefthe suabout

If a compile

� Confiboard

exists

© Agilent T 9-41


s

ocal_lib program may be used to move rary files into the boards subdirectory. This ty searches the library paths defined in the nd copies the library sources and objects to a ry called library. Its location is:

t/hp3070/contrib/bin/make_local_lib

s: t3070/contrib/bin/make_local_lib.exe

ib programs are used at the customers own gilent assumes no liability for their use.



� Confirm that the missing files were on the SOURCE system and they are in the expected location, including:

• wirelist or wirelist.o If there is a wirelist.o but no wirelist, try the following command in BT-BASIC:

list object ‘wirelist.o’ over ‘wirelist’

• fixture/fixture or fixture/fixture.o If there is a fixture.o but no fixture, try the following command in BT-BASIC:

list object ‘fixture.o’ over ‘fixture’

• config

• board

• testorder

• testplan

• necessary libraries

• and any other necessary files

� Verify paths to custom libraries outside the boards/<BoardName> subdirectory are hard coded properly in the appropriate files.

The libraries in the board directory and $AGILENT3070_ROOT/standard directory should work without problems.

Library path

The make_lexternal libcontrib utiliboard file alocal directo

UNIX: /op

MS Windowc:/Agilen

NOTE

Contrrisk. A

© Agilent T 9-42


What tConveDoes

Test Consultant has compile problems g the packaging or extraction process, *.o

ay not be created, and the board testplan ot execute properly. Each board directory

be converted individually.

pting batch mode processing of multiple files, including running IPG Test Consultant ause problems.



he rsion Tool

NOTE


NOTE

If a board directory has not run through IPG Test Consultant with software revision 3070 04.00pa or later, it may not convert correctly. Run IPG Test Consultant on the source system board directory before attempting conversion.

NOTE

Successful automated conversion assumes that default locations for various elements, files, custom libraries, and directories have been used by board development programmers. If modifications to these elements have occurred, converting the files will require more manual intervention.

NOTE

If IPGdurinfiles mmay nmust

NOTE

Attemboardwill c

© Agilent T 9-43


Variable

ith 3070 software revision 04.00pa, the t variable $AGILENT3070_ROOT is used to rtability between UNIX, MS Windows, and Windows systems with the software on

ives.

formation about environment variables, see stering Agilent 3070 Systems (Unix), The tory Environment Variable.

values of the $AGILENT3070_ROOT on ware loads are:

: AGILENT3070_ROOT = /var/hp3070

indows: AGILENT3070_ROOT = gilent3070

ontrollers /hp3070 is aliased to 70, so they are the same path.

e that was in /opt/... in UNIX, on MS hen using the default MS Windows setup, is er the <value in $AGILENT3070_ROOT>.

load the 3070 software on the MS Windows r may change the directory path where the installed during the installation process. That d, non-default directory path, is stored in the 3070_ROOT environment variable. That the environment variable in source files,

ding path, critical to having portable board



Relevant Differences Between UNIX and MS Windows Operating Systems

The operating system where the packaged file is extracted determines the characteristics of the boards/<BoardName> files.

Several differences between the operating systems make the Conversion Tool necessary. Each of these differences is explained in more detail in the following sections.

Differences include:

� Board Directory Paths

� File Names

� Device Driver Methods (Peripherals)

Board Directory Paths

On UNIX the paths cannot be changed during the software installation.

On MS Windows, the path can be changed during software installation.

In UNIX and MS Windows, the installation path is stored in the environment variable $AGILENT3070_ROOT.

Environment

Beginning wenvironmenenhance pobetween MSdifferent dr

For more inthe AdminiRoot Direc

The defaultfactory soft

� UNIX

� MS WC:/A

On UNIX c/var/hp30

The softwarWindows, wdirectly und

When usersOS, the usesoftware is user selecte$AGILENTmakes usingnot hard codirectories.

© Agilent T 9-44


ally the needed subdirectories are diately below the board directory and are rted correctly; however, this programming ce may not have been followed by all board ammers.

you will need to hard code these paths after rsion or move the external files into the directory.

ard paths are detected by the Conversion e name, the line number and path will be in ion.log.

rsion, search for “!cTool” in the board locate occurrences of non-standard paths.

standard hardcoded paths exist, such as in vi and setup.avi+pvi files, example paths IX and MS Windows may be in the /... /... example files.

ples where paths may be hard coded can be earching for file id, file name or directory online User manuals.



The Conversion Tool comments the original line containing /var/hp3070 and /hp3070 and replaces it with a line containing the environment variable $AGILENT3070_ROOT in text files under the boards directory. An exception is the BT-BASIC testplans, described below.

Program Language and Hard Coded Paths

BT-BASIC testplans use the environment variable with the btgetenv$ (“AGILENT3070_ROOT”) & “/PathName” statement. This allows testplans created on an MS Windows controller or an UNIX controller, which have been converted, to normally run without modification on either operating system.

Text source files created using program languages other than BT-BASIC may require editing before running IPG Test Consultant if files external to the board directory are needed by the program. Library files which are in default locations are converted without problems. These program languages are:

� VCL (Vector Control Language)� ATL (Analog Test Language)� STL (Serial Test Language)� ITL (InterconnectPlus Test Language)� BSDL (Boundary-Scan Description Language)

As part of program development in VCL, ATL, STL, ITL and BDSL languages, hard coded path names may have been used in the source files.

NOTE

Normimmeconvepractiprogr

If so, conveboard

If non-standTool, the filthe convers

After convedirectory to

Where non-the setup.afor both UN/standard

Syntax examlocated by sname in the

© Agilent T 9-45


re different files or directories in UNIX. ferred to MS Windows, they would ne another, with the contents being the last or moved.

s preserves the uppercase and lowercase on) letters in file and directory names, both eated in and transferred to MS Windows, but e the uppercase/lower case letters.

seful to understand which case on) a file name or directory name occurs . Both Korn Shell and Command Prompt

ill display the uppercase/lowercase letters.

w the case (capitalization) on the MS ows system use the Korn Shell (Start, ams, Agilent3070, Korn Shell). The

and Prompt (MS DOS) window will also y the case but its use is not recommended.

sion Tool treats identically spelled file llows:

first occurrence of class_bd = MS ows class_bd

2nd occurrence of Class_BD = MS ows Class_BD1.



Front-Slashes versus Back-Slashes in Command Lines Containing File Paths

A general rule for commands using a path to a directory or file is to use a forward-slash (/) for commands tied to a 3070 application, and use a back-slash (\) for MS Windows operating system-related commands.

If a command line containing a file path fails to execute, it may be because the slash used is of the wrong type.

Reversing the slash(es) may resolve the issue.

This is because:

� Many Korn shell commands are used in this Windows NT environment, and require front-slashes (/) in command lines containing file paths.

� In Windows NT, when opening a file from the Start, Run... menu, both front-slashes (/) and back-slashes (\) are recognized.

� A command may be performed in or with some relationship to the MS-DOS environment, which can require back-slashes in command lines containing file paths.

File Names

Uppercase / Lowercase Sensitivity

File names and path names in UNIX are case-sensitive. For example, files or directories class_bd and

Class_Bd aWhen transoverwrite oone copied

MS Window(capitalizatiin names crdoes not us

It may be u(capitalizatifirst in a filewindows w

NOTE

To vieWindProgrCommdispla

The Convernames as fo

� UNIXWind

UNIXWind

© Agilent T 9-46


o test the DUT. See Chapter 1, iple-Board Tests & Fixtures, for more s.

ries defined as part descriptions use : (colon) device file name. (See Chapter 7, Flash Programming Steps, for examples.

onversion Tool packages a board directory ames are renamed with the _@_ (at)underscore) character string. During destination operating system determines ter replaces the _@_ characters as follows:

<BoardName>.cvt file 2:r3 becomes 3. During extract:

IX: 2:r3

S Windows: 2%r3

created file names containing a % sign, this ome confusion, but will compile on either example:

nal file name = 70/boards/Test:%failure

g it back to UNIX this would become 070_ROOT/boards/Test::failure

rsion to MS Windows this name would

070_ROOT/boards/Test%%failure.



� UNIX 3rd occurrence of Class_bd = MS Windows Class_bd2

CAUTION

✸Each file is treated by itself, as if other files did not contain the same unique name differentiated only by case. File names usage in files in the same /<BoardName> subdirectory may not occur in the same order, therefore causing unexpected errors.

ADVICE

Unique file and directory names should be created on the UNIX system, excluding case sensitivity, and any files that reference the unique names modified. IPG Test Consultant should be run on the UNIX system prior to running the Conversion Tool.

Colon (:) and (%) Character

UNIX allows the : (colon) character in file and directory path names. It is an illegal character in a file or path name in MS Windows. The following programs in UNIX use the : (colon) character as a part of there program generation process:

� PanelTest and Throughput Multiplier (Uses 1:r3, 2:r3, etc. to differentiate which module is being

used tMultdetail

� Librain theOBP

When the Cillegal file n(underscoreExtract, thewhat charac

In the2_@_r

• UN

• M

If you havemay cause ssystem. For

UNIX origi/var/hp30

After movin$AGILENT3

After convebecome $AGILENT3

© Agilent T 9-47


070_ROOT/dev/ directory for compatibility

e communication is managed by the , Enterprise UNIX Development on oftware (TM).

ot all, of the GPIB devices which were UNIX are available in the 3070 04.00pa ftware release. These GPIB devices, which

n Table 9-1 on page 9-48, are in different cations on the MS Windows controller.



ADVICE

It is recommend that file names or path names containing % signs, or : (colon) not be used in either the UNIX or MS Windows environment.

Spaces and Underscores

File names containing spaces must not be used in either the UNIX or MS Windows environment. They may result in an error message during ITG Test Consultant execution, and will generate an error message when the Conversion Tool detects them.

File names with _ (underscore) are valid in both operating systems. For example, class_bd is valid.

Device Driver Methods (Peripherals)

Communication with peripherals (printers, plotters, power supplies, test equipment, etc.) is not the same for UNIX and MS Windows. However, the software used by the 3070 on the MS Windows system emulates the UNIX environment for GPIB devices, greatly simplifying cross-platform peripherals communication. See BT-BASIC Programming, Chapter 5, Addressing the Bus And Bus Devices, for more information about addressing GPIB devices.

In MS Windows most devices are managed by the operating system using device drivers. Several devices, (mostly GPIB) have been duplicated in the

$AGILENT3

reasons.

GPIB Devices

GPIB devicNutCrackerWindows S

Some, but nsupported inWindows soare shown idirectory lo

© Agilent T 9-48


counter

dmm

dmm_ref

gpio1

hpib1

hp3488

null

ps0

ps1

ps10

ps11

ps2

ps3

ps4

ps5

ps6



..

Table 9-1 GPIB device names and locations

File Name (/dev/...) UNIX MS Windows

counter /dev/counter $AGILENT3070_ROOT/dev/

dmm /dev/dmm $AGILENT3070_ROOT/dev/

dmm_ref /dev/dmm_ref $AGILENT3070_ROOT/dev/

gpio1 /dev/gpio1 $AGILENT3070_ROOT/dev/

hpib1 /dev/hpib1 $AGILENT3070_ROOT/dev/

hp3488 /dev/hp3488 $AGILENT3070_ROOT/dev/

null /dev/null $AGILENT3070_ROOT/dev/

ps0 /dev/ps0 $AGILENT3070_ROOT/dev/









© Agilent T 9-49


ps7

ps8

ps9

scope

synth






scope /dev/scope $AGILENT3070_ROOT/dev/

synth /dev/synth $AGILENT3070_ROOT/dev/

Table 9-1 GPIB device names and locations (continued)

File Name (/dev/...) UNIX MS Windows

© Agilent T 9-50


n

he COM port number.

and /dev/com2 do not appear in the /dev ut are managed by the MS Windows stem.

trip printer (rpr1), because it is used in every testplan, is converted by the

ersion Tool. The other input/output devices equire modifications to the testplan.

ansparent to user)

re n is assigned by



Serial Ports (RS232)

On the MS Windows system several RS232 devices which translated within 3070 applications are managed by the NutCracker, Enterprise UNIX Development on Windows Software (TM).

The stty option available on UNIX is not supported on MS Windows. Instead, use the BT-BASIC control statements. See BT-BASIC Programming, Chapter 6, RS-232 for more information.

These devices do not appear on the $AGILENT3070_ROOT/dev listing but are managed by the MS Windows operating system.

The COM serial ports in the MS Windows operating system are also mapped to /dev files as follows:

/dev/com/

where n is t

/dev/com1 directory, boperating sy

NOTE

The snearlyConvmay r

Table 9-2 Input/Output Devices

Device type UNIX MS Windows (tr

strip printer /dev/rpr1 /dev/com/2

Serial MUX Box /dev/ttym(xx) where xx is the box and the port

/dev/com/3..10

JOT /dev/JOT_PLC

/dev/JOT_BCR_P0

/dev/JOT_BCR_P1

/dev/com/4

/dev/com/5

/dev/com/6

bar code reader /dev/bcr /dev/com/n (whethe user)

© Agilent T 9-51


ansparent to user)

ws Adapter Part Number

01

07

ble



Because the RS232 MUX is a different product on UNIX and MS Windows controllers, the pinouts on the RJ45 connectors on the MS Windows and UNIX serial mux boards are not wired the same.

If you are using serial devices, you must change the RJ45 to DB9 or RJ45 to DB25 adapter to match the appropriate RS232 MUX.

tape drive /dev/rmt/0m /dev/rmt0

null /dev/null /dev/null

tty /dev/tty /dev/tty

console /dev/console /dev/console

lp /dev/lp /dev/lp

Table 9-2 Input/Output Devices (continued)

Device type UNIX MS Windows (tr

Table 9-3 RS232 MUX adapters

Cable adapter type UNIX Adapter Part Number MS Windo

RJ45 -> DB9M E9970-63200 E9970-632

RJ45 -> DB25M E4000-62105 E4000-621

RJ45 -> DB25F E4000-62106 Not availa

© Agilent T 9-52


Post-CFile Cl

ds/<BoardName>_compress.tar.z(x) if ts

rdName>/tmp_migration_board if it

ultant Backup Files

source and destination controller there are in ~, which are backup files. If disk space is sider whether the backup files are still r more information, see Chapter 1, nt Menu.



onversion eanup

After the conversion is complete, when the board directory on the destination controller 3070 system is testing Devices Under Test (DUTs), there are several files that can be removed to recover disk space.

Source Controller

If the source controller is a development controller, the user may choose to keep the board directory for future Engineering Change Order board development.

If you are going to keep the <BoardName> directory, you can remove:

� <BoardName>.cvt

� <BoardName>__package.log

� /migration_directory(x) if it exists. If problems have occurred, there may be multiple copies as designated by the (x).

If no future development for this board directory is going to be done on the source machine, delete:

� <BoardName> original board directory

Destination Controller

Files that can be removed include:

� <BoardName>.cvt

� /<BoardName>/conversion.log

� /boar

it exis

� /<Boa

exists

Test Cons

On both thefiles endingneeded, conrequired. FoManageme

boardconvert tool

Documents