Verigy Lab 4 SW Overview

SW Architecture Module: Labs
Version 1.0, Sept 2006
Revision History
Date
Change / Description
Source / Author
Revision
4/Sep/06
Document Creation, derived from

PinScale delta training, version 1.8
Domenico Chindamo
1.0
Table of Contents
Revision History....................................................................................................... 2
Lab: Device license files ............................................................................................ 4
1. Offline Usage ................................................................................................... 4
2. Online Usage ................................................................................................... 6
Answers to questions ............................................................................................. 8
Lab: Device license files

Learning objective:
This lab will familiarize you with the device file concept. The model file concept evolved from
tester-centric, a representation of the available HW, to cost-saving-centric, a representation
of the license requirements for testing the device. The device license goes a step further,
because it overrides some entries of the model file, according to the licenses needed to run
the test of a particular DUT. The license file share the same syntax of the model file.
By changing various device license file entries related to the test system (section GLOBAL)
or to the digital I/O channels (section IOCHANNEL), you can observe the results on the
available system resources when starting SmarTest offline and online. Some of the most
relevant entries are as follows:
- per system only:
unified or compatible memory mode
timing bundles (combinations of waveforms and number of edges)
multiport
gigamem
RF noise figure
multisite
(model file only)
memory test (model file only)
- per digital card only:
HW type
- per pin:
sequencer/data rate
memory size
differential operation
ppTIA
Getting started:
The instructor gives you a template device license file model_license.training.
1. Offline Usage
1. Copy the given file to the default location for device license files, or use the
appropriate Linux environment variable V93000_LICENSING to point to the device
license file:
export V93000_LICENSING=/<dev_license_path>/model_license.training
Note that this change is effective only in the terminal window where you typed it,
therefore you need to repeat the operation in case you use several windows.
Similarly the Linux computer do not keeps track of it when logging out.
2. Check the Flexlm license manager status. Normally the system administrator
arranges such that this task is accomplished at Linux booting time.
lmutil lmstat -c </opt/flexlm/LicenseFile.lic>
lmutil is a License Management utility. It is provided by MacroVision to Verigy as

part of the FLEXlm package, so to manage the licenses necessary to a particular
SmarTest run. Specifying argument lmstat the user gets information about the
status of the license, whose pathname is detailed in the subsequent -c argument.
Make sure the vendor daemon socbu is up and running.
3. Start SmarTest in offline mode by typing HPSmarTest o & or, if available, its alias
93koff in the same terminal window. Either use any existing setup or create a new
device or use. In this lab we are not going to touch any element of SmarTest.
4. Change various entries in the given device license file (e.g. installed HW type in
different slots, sequencer/data rate, memory mode or size, timing bundles, etc.),
and observe the resulting available configuration in the ui_report window. Each time
you need to exit and enter again in SmarTest as per step 3 or click on Change
Device in the main SmarTest toolbar.
Figure 1 Change Device button

GLOBAL
# gigamem = 3
# 0 - <number_of_io_channels>; default 0
# noise_figure = ON
# ON | OFF;
default is OFF
# rapid_source_synch = 2
# 0 - <number_of_sites>;
default 0
# device_maintenance = ON # ON | OFF;
default OFF
timing_bundle = w256-d8-r8 # timing bundle;
default 0 waveforms, 0 edges
# multiport = ON
# ON | OFF;
default ON for SOC; OFF for HSM
IOCHANNEL
10101-10116:HW = PS800, speed = 800 Mbps , smem = 2M, vmem = 28M, diff, ppTIA
#10301-10316:HW = PP400, speed = 400 Mbps , smem = 32M
#10502-10516:HW = PS3600, speed = 800 Mbps, smem = 16M, diff, ppTIA
Figure 2 Example device license file
5. Use the Change Device main tool bar button open the Edit Device dialog and
select the file-name in the licensing file drop down list. Save the modification by
clicking enter device. This way what you have just entered goes to the
.technology file.
6. Observe the ui_report window. The change is not effective because the
$V9300_LICENSING has higher priority for device licensing.
7. Help yourself for the license file syntax. Go to the ui_report window and choose Help
> Browsable documentation. Navigate through the pages to find the licensing
per device topic.
Question 1: how can you do to make the change in step 7 effective?
Question 2: speed is not checked in terms of MHz but Mbit-per-second. Why?

Question 3: Why is it possible to specify different memory sizes?
2.
Online Usage
Allowed entries for the online lab depends on the the particular V93000 configuration
and installed licenses you are using. Check with the instructor.
8. Start SmarTest in online mode by typing HPSmarTest & or, if available, its alias
93k in the same terminal window.
9. As in step 4, change various entries in the device license file and observe the results
when starting SmarTest in online mode. Note the difference between
maximum possible configuration: installed HW in the system

requested configuration: system capabilities as specified in license file
available configuration: system capabilities after licenses are granted
Figure 3
Example ui_report window output in online mode
Question 4: Each time SmarTest is started online the actual tester configuration
(installed HW) is logged in a file. Where does this file reside?
Question 5: When are the licenses checked back in the license server? What happens
at that time?
Answers to questions
Answer 1:
As per step 1, open a new terminal; open SmarTest in this terminal and repeat step 7.
For making the changes of step 1 permanent, it is needed to update the environmental
variables set at your login. For doing that task you would need to edit your .bash_profile
file, in your home directory and add a line for V93000_LICENSING. In this case it is
necessary to hardcode the < dev_license_path >.
Answer 2:
Because the V93000 has the capability to apply up to 8 edges for each cycle, using a
compression method called X-mode. Thus the MHz the DUT perceives can be up to 8X
higher than the MHz applied from the V93000. On the contrary the Mbps gives a fair way of
operating.
Answer 2:
Because the V93000 has a per-pin architecture, thus each pin has its own vector, sequencer
or unified memory behind it.
Answer 4:
Look in: /var/opt/hp93000/soc/model_template
Answer 5:
When you exit SmarTest the licenses are available for another user. The license manager
concept allows he/she to be co-located in the same test-floor or based in at another location
within your company. Check with your system administrator about the policy.

Verigy Lab 4 SW Overview

Uploaded by

Copyright:

Available Formats

Verigy Lab 4 SW Overview

Uploaded by

Document Information

Original Description:

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

Verigy Lab 4 SW Overview

Uploaded by

Copyright:

Available Formats

SW Architecture Module: Labs

Version 1.0, Sept 2006

Document Creation, derived from

Lab: Device license files

lmutil lmstat -c </opt/flexlm/LicenseFile.lic>

lmutil is a License Management utility. It is provided by MacroVision to Verigy as

Figure 1 Change Device button

Question 2: speed is not checked in terms of MHz but Mbit-per-second. Why?

maximum possible configuration: installed HW in the system

Example ui_report window output in online mode

You might also like