ChipScope Pro Software and Cores User Guide
71
UG029 (v14.3) October 16, 2012
ChipScope Pro Analyzer Features
Repetitive Trigger Run Mode
The repetitive trigger run mode is similar to the single trigger run mode, with one
following exception:
In repetitive trigger run mode, instead of stopping after triggering and
uploading/displaying captured data, the ChipScope Pro Analyzer tool automatically re-
arms the ILA core trigger. The captured data from the previous trigger event continues to
be displayed in the data viewers (waveform, listing, bus plot) as long as the subsequent
trigger has not occurred. After the subsequent trigger occurs and the data capture buffer
becomes full, the data viewers update to show this new data. This process repeats until the
you manually stop the trigger.
Repetitive Trigger Logging
The captured data from each repetitive trigger run can be logged to a file. To do this, select
Trigger Setup > Setup Repetitive Trigger Logging
to open the setup dialog window. Use
the
Browse
button to select the location for the log files. Each file created by the ChipScope
Pro Analyzer tool includes a sequence number that corresponds to the repetitive trigger
run iteration. Use the
Overwrite any existing files
check box to overwrite previous data
log files.
The format for the data log files can be set to one of three available formats: value change
dump (VCD) format, tab-delimited text format (ASCII), or the Agilent Technologies Fast
Binary Data Format (FBDF). To select a format, click its radio button.
Use the
Signals to Export
combo box to select the set of signals and/or buses to export. The
signals that can be exported include:
•
Signals and buses for that particular core
•
Signals and buses present in the waveform viewer for the core
•
Signals and buses in the listing viewer for the core
•
Signals and buses in the bus plot viewer for the core
Logging or exporting of signals during Single Trigger Run Mode is described in the
section of this user guide.
Startup Trigger Run Mode
The startup trigger run mode allows you to set up the ILA core to trigger on events that
occur after FPGA device startup without having to use the ChipScope Pro Analyzer tool to
arm the ILA core. Using the Startup Trigger Run Mode requires you to follow three steps:
1.
Specify the trigger settings and save the startup trigger setup (CTJ) and design
constraint (UCF) files.
2.
Re-implement your design with the startup trigger setup design constraint file.
3.
Use the ChipScope Pro Analyzer in Startup Trigger Run Mode to configure the device
then upload and display the data that was captured after the trigger occurred.
To specify the trigger settings for use with trigger run mode, you must first set the Trigger
Run Mode to
Single
. You then set up the match functions, trigger condition, and capture
setup to your desired settings. After you have your trigger settings the way you want
them, you use the
Trigger Setup > Save Trigger Startup Files
menu option to specify the
required files:
•
The NGD design file that corresponds to the design that is currently running in the
FPGA device under test.
