Visible to Intel only — GUID: hko1596229343279
Ixiasoft
1. System Debugging Tools Overview
2. Design Debugging with the Signal Tap Logic Analyzer
3. Quick Design Verification with Signal Probe
4. In-System Debugging Using External Logic Analyzers
5. In-System Modification of Memory and Constants
6. Design Debugging Using In-System Sources and Probes
7. Analyzing and Debugging Designs with System Console
8. Intel® Quartus® Prime Pro Edition User Guide Debug Tools Archives
A. Intel® Quartus® Prime Pro Edition User Guides
1.1. System Debugging Tools Portfolio
1.2. Tools for Monitoring RTL Nodes
1.3. Stimulus-Capable Tools
1.4. Virtual JTAG Interface Intel® FPGA IP
1.5. System-Level Debug Fabric
1.6. SLD JTAG Bridge
1.7. Partial Reconfiguration Design Debugging
1.8. Preserving Signals for Debugging
1.9. System Debugging Tools Overview Revision History
2.1. Signal Tap Logic Analyzer Introduction
2.2. Signal Tap Debugging Flow
2.3. Step 1: Add the Signal Tap Logic Analyzer to the Project
2.4. Step 2: Configure the Signal Tap Logic Analyzer
2.5. Step 3: Compile the Design and Signal Tap Instances
2.6. Step 4: Program the Target Hardware
2.7. Step 5: Run the Signal Tap Logic Analyzer
2.8. Step 6: Analyze Signal Tap Captured Data
2.9. Other Signal Tap Debugging Flows
2.10. Signal Tap Logic Analyzer Design Examples
2.11. Custom State-Based Triggering Flow Examples
2.12. Signal Tap File Templates
2.13. Running the Stand-Alone Version of Signal Tap
2.14. Signal Tap Scripting Support
2.15. Signal Tap File Version Compatibility
2.16. Design Debugging with the Signal Tap Logic Analyzer Revision History
2.4.1. Preserving Signals for Monitoring and Debugging
2.4.2. Preventing Changes that Require Full Recompilation
2.4.3. Specifying the Clock, Sample Depth, and RAM Type
2.4.4. Specifying the Buffer Acquisition Mode
2.4.5. Adding Signals to the Signal Tap Logic Analyzer
2.4.6. Defining Trigger Conditions
2.4.7. Specifying Pipeline Settings
2.4.8. Filtering Relevant Samples
2.4.6.1. Basic Trigger Conditions
2.4.6.2. Nested Trigger Conditions
2.4.6.3. Comparison Trigger Conditions
2.4.6.4. Advanced Trigger Conditions
2.4.6.5. Custom Trigger HDL Object
2.4.6.6. Specify Trigger Position
2.4.6.7. Power-Up Triggers
2.4.6.8. External Triggers
2.4.6.9. Trigger Condition Flow Control
2.4.6.10. Sequential Triggering
2.4.6.11. State-Based Triggering
2.4.6.12. Trigger Lock Mode
2.4.6.11.5.1. <state_label>
2.4.6.11.5.2. <boolean_expression>
2.4.6.11.5.3. <action_list>
2.4.6.11.5.4. Trigger that Skips Clock Cycles after Hitting Condition
2.4.6.11.5.5. Storage Qualification with Post-Fill Count Value Less than m
2.4.6.11.5.6. Resource Manipulation Action
2.4.6.11.5.7. Buffer Control Actions
2.4.6.11.5.8. State Transition Action
2.8.1. Viewing Capture Data Using Segmented Buffers
2.8.2. Viewing Data with Different Acquisition Modes
2.8.3. Creating Mnemonics for Bit Patterns
2.8.4. Locating a Node in the Design
2.8.5. Saving Captured Signal Tap Data
2.8.6. Exporting Captured Signal Tap Data
2.8.7. Creating a Signal Tap List File
2.9.1. Signal Tap and Simulator Integration
2.9.2. Managing Multiple Signal Tap Configurations
2.9.3. Debugging Partial Reconfiguration Designs with Signal Tap
2.9.4. Debugging Block-Based Designs with Signal Tap
2.9.5. Debugging Devices that use Configuration Bitstream Security
2.9.6. Signal Tap Data Capture with the MATLAB* MEX Function
2.9.4.1.1. Partition Boundary Ports Method
2.9.4.1.2. Debug a Core Partition through Partition Boundary Ports
2.9.4.1.3. Export a Core Partition with Partition Boundary Ports
2.9.4.1.4. Signal Tap HDL Instance Method
2.9.4.1.5. Export a Core Partition with Signal Tap HDL Instances
2.9.4.1.6. Debug a Core Partition Exported with Signal Tap HDL Instances
3.1.1. Step 1: Reserve Signal Probe Pins
3.1.2. Step 2: Assign Nodes to Signal Probe Pins
3.1.3. Step 3: Connect the Signal Probe Pin to an Output Pin
3.1.4. Step 4: Compile the Design
3.1.5. (Optional) Step 5: Modify the Signal Probe Pins Assignments
3.1.6. Step 6: Run Fitter-Only Compilation
3.1.7. Step 7: Check Connection Table in Fitter Report
5.1. IP Cores Supporting ISMCE
5.2. Debug Flow with the In-System Memory Content Editor
5.3. Enabling Runtime Modification of Instances in the Design
5.4. Programming the Device with the In-System Memory Content Editor
5.5. Loading Memory Instances to the ISMCE
5.6. Monitoring Locations in Memory
5.7. Editing Memory Contents with the Hex Editor Pane
5.8. Importing and Exporting Memory Files
5.9. Access Two or More Devices
5.10. Scripting Support
5.11. In-System Modification of Memory and Constants Revision History
6.1. Hardware and Software Requirements
6.2. Design Flow Using the In-System Sources and Probes Editor
6.3. Compiling the Design
6.4. Running the In-System Sources and Probes Editor
6.5. Tcl interface for the In-System Sources and Probes Editor
6.6. Design Example: Dynamic PLL Reconfiguration
6.7. Design Debugging Using In-System Sources and Probes Revision History
7.1. Introduction to System Console
7.2. Starting System Console
7.3. System Console GUI
7.4. Launching a Toolkit in System Console
7.5. Using System Console Services
7.6. On-Board Intel® FPGA Download Cable II Support
7.7. MATLAB* and Simulink* in a System Verification Flow
7.8. System Console Examples and Tutorials
7.9. Running System Console in Command-Line Mode
7.10. Using System Console Commands
7.11. Using Toolkit Tcl Commands
7.12. Analyzing and Debugging Designs with the System Console Revision History
7.5.1. Locating Available Services
7.5.2. Opening and Closing Services
7.5.3. Using the SLD Service
7.5.4. Using the In-System Sources and Probes Service
7.5.5. Using the Monitor Service
7.5.6. Using the Device Service
7.5.7. Using the Design Service
7.5.8. Using the Bytestream Service
7.5.9. Using the JTAG Debug Service
Visible to Intel only — GUID: hko1596229343279
Ixiasoft
2.12. Signal Tap File Templates
Signal Tap file templates provide preset settings for various trigger conditions, interfaces, and state-based triggering flows. The following Signal Tap file templates are available whenever you open a new Signal Tap session or create a new .stp file.
Right-click any template in the New File from Template dialog box, and then click Set as the default selection to always open new .stp files in that template by default.
Settings Default Signal Tap File Template
Note: Refer to the New File from Template dialog box for complete descriptions of all templates.
Template | Summary Description |
---|---|
Default | The most basic and compact setup that is suitable for many debugging needs |
Default with Hidden Hierarchy and Data Log | The same setup as the Default template, with additional Hierarchy Display and Data Log windows for trigger condition setup. |
State-Based Trigger Flow Control | Starts with three conditions setup to replicate the basic sequential trigger flow control. |
Conditional Storage Qualifier | Enables the Conditional storage qualifier and Basic OR condition. This setup provides a versatile storage qualifier condition expression. |
Transitional Storage Qualifier | Enables the Transitional storage qualifier. The Transitional storage qualifier simply detects changes in data. |
Start-Stop Storage Qualifier | Enables the Start/Stop storage qualifier and the Basic OR condition. Provides two conditions to frame the data. |
State-Based Storage Qualifier | Provides more sophisticated qualification conditions for use with state machine expressions. You must use the State-Based Storage Qualifier template in conjunction with the state-based trigger flow control |
Input Port Storage Qualifier | Enables the Input port storage qualifier to provide total control of the storage qualifier condition by supporting development of custom logic outside of the Signal Tap logic hierarchy. |
Trivial Advanced Trigger Condition | Enables the Advanced trigger condition. The Advanced condition provides the most flexibility to express complex conditions. The Advanced trigger condition scales from a simple wire to the most complex logical expression. This template starts with the simplest condition. |
Trigger Position Defined Using Sample Count | Supports specifying an exact number of samples to store after the trigger position, using the State-Based Trigger Flow Control template as a reference. |
Cross-triggering Between STP Instances | Enables "Cross-triggering by using the Trigger out from one instance as the Trigger in of another instance, when using multiple Signal Tap instances. |
Setup for Incremental Compilation | Specifies a fixed input width for signal inputs. This technique allows efficient incremental compilation by reducing the amount of Signal Tap logic change, and by adding only post-fit nodes to tap. |
Define Trigger Condition in RTL | Supports defining a custom trigger condition in the RTL language of your choice. |
Template | Summary Description |
---|---|
Capture Avalon Memory Mapped Transactions | Allows you to use the storage qualifier feature to store only meaningful Avalon® memory-mapped interface transactions. |
Simple Avalon Streaming Interface Bus Performance Analysis | Supports recording of event time for analysis of the data packet flow in an Avalon® streaming interface. |
Use Counters in the State-based Flow Control to Collect Stats | Use counters to track of the number of packets produced (pkt_counter), number of data beats produced (pkt_beat_counter), and number of data beats consumed (stream_beat_counter). |
Template | Setup Description |
---|---|
Trigger on an Event Absent for Greater Than or Equal to 5 Clock Cycles | Requires setup of one basic trigger condition in the Setup tab to the value that you want. |
Trigger on Event Absent for Less Than 5 Clock Cycles | Requires setup of one basic trigger condition in the Setup tab to the value that you want. |
Trigger on 5th Occurrence of a Group Value | Requires setup of one basic trigger condition in the Setup tab to the value that you want. |
Trigger on the 5th Transition of a Group Value | Requires setup of an edge-sensitive trigger condition to detect all bus transitions to the desired group value. Requires edge detection for any data bus bit logically ANDed with a comparison to the desired group value. An advanced trigger condition is necessary in this case. |
Trigger After Condition1 is Followed by Condition2 | Requires setup of three basic trigger conditions in the Setup tab to the values you specify. The first two trigger conditions are set to the desired group values. The third trigger condition is set to capture some type of idle transaction across the bus between the first and second conditions. |
Trigger on Condition1 Immediately Followed by Condition2 | Requires setup of two basic trigger conditions in the Setup tab to the group values that you want. |
Trigger on Condition2 Not Occurring Between Condition1 and Condition3 | Requires setup of three basic trigger conditions in the Setup tab to the group values that you want. |
Trigger on the 5th Consecutive Occurrence of Condition1 | Requires setup of one basic trigger condition in the Setup tab to the value you want. |
Trigger After a Violation of Sequence From Condition1 To Condition4 | Requires setup of four basic trigger conditions to the sequence values that you want. |
Trigger on a Sequence of Edges | Requires setup of three edge-sensitive basic trigger conditions for the sequence that you want. |
Trigger on Condition1 Followed by Condition2 After 5 Clock Cycles | Requires setup of two basic trigger conditions to the group values that you want. |
Trigger on Condition1 Followed by Condition2 Within 5 Samples | Requires setup of two basic trigger conditions to the group values that you want. |
Trigger on Condition1 Not Followed by Condition2 Within 5 Samples | Requires setup of two basic trigger conditions to the group values that you want. |
Trigger After 5 Consecutive Transitions | Requires setup of a trigger condition to capture any transition activity on the monitored bus. This example requires an Advanced trigger condition because the example requires an OR condition. |
Trigger When Condition1 Occurs Less Than 5 Times Between Condition2 and Condition3 | Requires setup of three edge-sensitive trigger conditions, with each trigger condition containing a comparison to the desired group value. |