Test Engineering Systems

1. How do I find out what revision of software I am currently running?
   
   

   Open a shell window and type the command version.
   This is an example output of this command:
   Unix
   Agilent 3070 Software Version 3070 05.00pd 1101 UX
   05.00pd is the version of 3070 software you are running.
   1101 UX is the version of unix software you are running.

2. What do I do with the file that you have sent?
   
   

   The file that we send you is a compressed file with a .tar.gz extension. Follow the following steps to extract the data from it.
   Transfer the file to your board directory sever (i.e. /hp3070/boards).
   Open a shell window.
   Type the command gunzip filename.
   After this command is finished a file with the .tar extension should have been created.
   Type the command tar -xvf filename.

3. How do I transfer the file that you sent to my server?
   
   

   Use any file transfer program (FTP) or use window's ftp command.

4. How do I determine what software licenses I have installed on my machine?
   
   

   In a shell window type the command codeward -l. This will list all of the options available, and two columns; one for on and the other for off.

5. How do I compress a board directory?
   
   

   Two common unix commands can be used to compress a board directory. First in a shell window type tar -cvf . Second type the command gzip . This will result in creating a file called <boarddir.tar.gz>

6. Why is there a difference between the board graphics orientation and how the board is orientated on the fixture?
   
   

   When the fixture is designed we try to place the board on the fixture so that it gives us access to the most resources, and to make sure no critical resources are blocked. If you would like to have these two orientations match, please contact us and we will make sure that they match.

7. The file fixture/fixture or wirelist does not exist what do I need to do?
   
   

   You will need to list out the object files to create these two files. You can use bt-basic or a shell window to do this.

8. What happens when I run IPG against the files that you have sent?
   
   

   Many different things can happen when you do this, including rewriting everything that was done previously. It is recommended you contact us before doing this.
   

1. Debug object not found -- when trying to debug a test
   
   

   To fix this you will need to recompile the test. You can either use the compile in a basic window, or the appropriate shell command. mcomp for mixed tests, dcomp for digital tests).

2. Version does not match or Version different than expected — when running the fixture
   
   

   The revision of software that the test was developed is newer than the software that is installed on your controller. In the board directory there should be a file in the bin directory called recomp. Open a shell window and go to your board directory. At the shell prompt type bin/recomp. This will recompile everything to work with the older revisions.

3. When I try to run your 'recomp' script I get an error that 'Execute permission denied'. What do I need to do?
   
   

   In a shell window, change the working directory to the one that contains the recomp script. Next type the command chmod 774 recomp. Then you should be able to run the script without any problems.

4. When I try to run the fixture for the first time, I get the error 'fixture does not match configuration'.
   
   

   This error occurs when something in the board config does not match the testhead config file. Common reasons for this error are different supply types between our facility and your facility. Contact us if you need help with this problem.

5. Too many attempts to discharge board
   
   

   This occurs when a board is being discharge and the system was not able to do it properly. THIS CAN RESULT IN DAMAGE TO THE TESTHEAD. To fix this problem edit the file analog/.discharge. Edit the values next to entry to be about 150m and exit to be about 10m. Contact us if you need help with this problem.

6. File type different than what is expected
   
   

   Each file in the agilent board directory has a unique file type. When the software tried to access or compile a certain file, the file type found was not what it expected. To fix this problem you will need to open a btbasic window in the directory with the file containing the wrong type. Next type the command get <type> filename. They type of file should now be in the basic window next to the process number. If any syntax errors where in the file they should appear across the screen. After fixing any errors type the command re-save to resave the file as the correct type. Some of the different types can be found below and in the manuals under the syntax of the get command:

   • analog: for analog tests in the analog directory and the analog section of a mixed test
   • digital: for digital tests in the digital directory and the digital section of a mixed test
   • basic: a basic program to be run in btbasic example testplan
   • bsdl: bsdl files for JTAG devices
   • config: config file
   • part: part description library
   • testorder: testorder file
   • testjet: testjet test

1. What do I need to program a certain device?
   
   

   To program parallel flash and EEPROM devices a Motorola S record or Intel Hex record is needed. To program serial flash and EEPROM devices the same records are needed but additional work needs to be done with them. To program EPLDs, CPLDs, and other devices contact us to discuss what is needed to program that particular device.

2. I have a new S/hex record for the flash device what do I need to do?
   
   

   Copy the new record file over the old one. It might be necessary to recompile the program and verify tests after this is done. To be on the safe side just recompile the tests to make sure the new data will be programmed into the device.

3. I have a new svf file what do I need to do?
   
   

   The tests associated with this svf will have to be regenerated. Contact us and we can either regenerate them for you or walk you through the process.

4. How do I decrease the flash programming first run test time
   
   

   Programming of flash and serial devices will take longer the very first time that the program in run. This is due to the tester's need to download the information in the s/hex record to the cards. To decrease this test time you can place the statement generate static test in the program and verify tests for the device. After this is done recompile the two tests. What this will do is place the data into the compiled object decreasing the amount of time it takes to load the information to the cards. The drawbacks of this is the compiled object is greater in size, the compile time is longer, and each time the data changes you will need to recompile the tests.

1. What is the autofile number used for?
   
   

   The autofile is used by the test system to identify a fixture and point to where the board directory for that fixture is stored.

2. Where can I find the autofile number for this fixture?
   
   

   To find the autofile number for a particular fixture you can look in many different locations; some include:

   • in the board file
   • in the file fixture/fixture
   • in the file fixture/summary
   • in the file fixture/trace
   • in the file fixture/inserts
   • in the file fixture/wires

3. Where can I find the autofile number for this fixture on the controller?
   
   

   The autofile is located in two directories. The file name is the same as the autofile number. The two directories are:

   • /hp3070/autofile
   • /Agilent3070/autofile

4. When I try to run the fixture as operator it goes to confirmation, how do I fix this?
   
   

   The path located in the Autofile file is not correct or the file does not exist. Edit the file to include the correct path or create the file and place the correct path in it.

5. There is a conflict between the autofile you assigned and another fixture on my system how do I fix this?
   
   

   Contact us and we can discuss the options to fix this type of problem.

6. How can I check to see what autofile the tester is detecting?
   
   

   In a btbasic window with the fixture placed on the testhead and the tester initialized, type the command autofile.

Shell Commands

acomp: compile an analog test

basic: start a bt-basic window.

bcomp: compile the board file

bdeii: run board consultant

bsdl_compile: compile a bsdl file

chk_bcf: check to see if syntax of board file is correct

chk_pdf: check to see if syntax of board_xy file is correct

cpcomp: compile a testjet or polarity check file

dcomp: compile a digital test.

flist: list out the fixture/fixture.o file

fxtcon: run Fixture Consultant

gunzip: uncompress a file.

gzip: compress a file; very useful to use with tar.

ipgtcloop: start IPG.

lcomp: compile a digital library.

mcomp: compile a mixed test.

pcomp: compile the board_xy file

pde: start the Part Description Editor.

qcomp: compile the config file

scomp: compile a shorts or pins file

setuped: start Setup Test Editor.

tar: produces 1 file that contains many files.

tpw: regenerate the testplan.
[Caution: this will rewrite the old testplan and replace any changes that you have made to it]

wlist: list out the wirelist.o file