AN 955: Programmer’s Configuration Debugger Tool

Download PDF
ID 691274
Date 4/01/2024
Public
Document Table of Contents
Document Table of Contents x
1. Programmer’s Configuration Debugger Tool 2. Debugging Tool Components 3. Document Revision History for AN 955: Programmer’s Configuration Debugger Tool
1. Programmer’s Configuration Debugger Tool x
1.1. Launching Debugger Tool
2. Debugging Tool Components x
2.1. Parsing Programming Files 2.2. Getting Device Information 2.3. Debugging QSPI Flash 2.4. QSPI Controller Settings and SFDP Values 2.5. Debugging Remote System Update 2.6. Voltage Sensor Monitoring 2.7. Temperature Sensor Monitoring 2.8. Hard Processor System (HPS) Cold Reset 2.9. Debug Log 2.10. SDM Mailbox Command
2.1. Parsing Programming Files x
2.1.1. Reading Programming File Information 2.1.2. Parsing Program Files Command Option 2.1.3. Programming File Formats
2.1.3. Programming File Formats x
2.1.3.1. SOF File Information 2.1.3.2. RBF File Information 2.1.3.3. PMSF File Information 2.1.3.4. JIC File Information 2.1.3.5. RPD File Information 2.1.3.6. POF File Information
2.2. Getting Device Information x
2.2.1. Reading Device Information from SDM-Based Devices 2.2.2. Reading Device Information from Legacy Devices
2.3. Debugging QSPI Flash x
2.3.1. Performing QSPI Flash Debugging
2.4. QSPI Controller Settings and SFDP Values x
2.4.1. Reading the QSPI Controller Settings and SFDP Values
2.4.1. Reading the QSPI Controller Settings and SFDP Values x
2.4.1.1. QSPI Flash Debugging Use Cases
2.5. Debugging Remote System Update x
2.5.1. Performing Remote System Update Debugging
2.6. Voltage Sensor Monitoring x
2.6.1. Reading Voltage Measurement
2.7. Temperature Sensor Monitoring x
2.7.1. Reading Temperature Measurement
2.8. Hard Processor System (HPS) Cold Reset x
2.8.1. Performing Hard Processor System (HPS) Cold Reset
2.9. Debug Log x
2.9.1. Getting the Debug Log
2.10. SDM Mailbox Command x
2.10.1. Sending SDM Mailbox Command 2.10.2. Command Options for Sending SDM Mailbox Command
1. Programmer’s Configuration Debugger Tool
2. Debugging Tool Components
3. Document Revision History for AN 955: Programmer’s Configuration Debugger Tool

2.9. Debug Log

You can retrieve the debug log from the device using the debugger tool and command line interface. The debug log contains human-readable information to resolve common problems such as missing or incorrect clock settings and errors during initialization of voltage regulators.

The debugger tool detects the supported debug levels based on the firmware that is loaded into the device. Production firmware supports debug level 0 and 1. Beta firmware supports up to level 2 debug level.

The debugger tool can read the debug log based on the level selected and write it to an output text file. The captured log text filename is displayed in the session log. The file format is debug_log-<date>-<time>.txt. To retrieve the debug log, connect the device via JTAG interface. The device must be configured with firmware version 23.1 or later.

Upon configuration failure, customer may get the debug log from the tool and contact Intel Support and quote ID #15012866170 to debug further based on the debug log.

Example of command line to capture the debug trace log level 1 from the device: 
quartus_pgm -c 1 -m jtag --debug_trace=<file_name.txt> --trace_level=1

Section Content
Getting the Debug Log

Level Two Title