Download PG3A User`s Manual

The Moving Pixel Company PG3A User’s Manual – Doc. Rev. 1.09 -- 11/7/08
Block1 loops until Evt1 is true, then the sequence branches to Line2. Block2 loops until
Evt2 is true, then the sequence branches to Line3. Since Line2 is a branch destination,
the branch hold off restriction applies and no branch may be specified for at least 12
vectors. Thus, if Block2 is 12 vectors or longer, the compiler will allow it. Otherwise, an
error will be flagged.
4.7 Running the PG
Putting it all together, a typical PGApp session begins with the following steps:
1) Launch PGApp, either explicitly connecting to PG module(s) through the
connection dialog or implicitly connecting to PG module(s) from the previous
session.
2) Open the Channel Setup page. Define and name logical groups, assigning probe
channel bits to each group. These groups are presumably relevant to the specific
SUT, i.e. Address, Data, Control, etc.
3) Optionally, open the Signals Setup page to configure the routing for the external
event signal source and SignalOut signal destination.
4) Use the Block Definition page to create blocks of data vectors. For each block,
name it, give it a length, and use the Listing or Waveform window to enter its
data.
5) Optionally, use the Event Definition page to define logical events for sequence
flow control.
6) Use the Sequence Definition page to set up the program for block output, looping,
waiting, and branching as appropriate. If SignalOut is to be used, set its state
during the output of each sequence line.
7) Now, configure the PG module using the Module Setup page. Define clocking
and event parameters and PG behavior when running and stopped.
8) Finally, use the Probe Setup page to configure the PG probes, specifically output
level, data delays, and strobe shape.
Once the program has been defined and the hardware configured, clicking the Arm/Run
button on the main window toolbar kicks off the PG. 7 The following tasks occur during
run:
Compilation – First, the compiler is invoked to process the block, sequence, and event
definitions and check for errors. Progress dialogs are brought up to show what phase of
compilation the compiler is in. When complete, the Output window is brought up to list
any warnings and errors that occur during compilation.8
Download – If no errors occur, then sequence and vector data are downloaded to the PG
module, with status shown via a progress dialog. Download time is variable depending
7
The Run button is labeled “Arm” if a run trigger is specified in the Signals Setup page of the Setup
window and “Run” otherwise.
8
Note that if the Output window was brought up automatically, the Output window is also dismissed
automatically if no errors occur. To bring up the Output window manually, for example to see warnings,
you can manually bring up the Output window using the View->Output menu option.
- Page 42 -