External Memory Interfaces Agilex™ 7 F-Series and I-Series FPGA IP User Guide

ID 683216
Date 3/29/2024
Document Table of Contents Traffic Generator Status Report

The traffic generator status report (TG Status Report) shows the overall traffic generator status, write overflow status, and per-DQ-pin information.
Figure 249. TG Status Report (Passing Traffic Pattern)

If a failure occurs, the status report displays details about the failure, such as Number of Avalon Read Instructions Issued, Fail Count, and information about the first failure—First Failure Address, First Failure - Read Data, and First Failure - Expected Data. The Write Overflow Status LED turns red if the traffic configuration attempts an invalid Avalon burst length command; this occurs if the current address plus the value of burst length is greater than the total address space. The address at which burst length overflow occurred is also reported. Individual Clear buttons allow you to clear these values independently between successive runs of the traffic generator.

Figure 250. TG Status Report (Failing Traffic Pattern)

The Export TG Status Report button allows you to export the status report as a log file, to the subdirectory from which you launched the System Console.

The PNF signal is logged in raw hex format. For information on reading and interpreting this format, refer to Reading PNF Registers or ISSPs in the Traffic Generator Status topic.

When the traffic generator is running in infinite user mode, you can update the status report only by clicking Generate TG Status Report.

Figure 251. TG Status Report (While Running Infinite Traffic)
Figure 252. TG Status Report (Attempt to Overflow Address Space)

If you configure the traffic generator such that a generated address plus the value of the burst length is greater than the address space, a burst length overflow occurs. The traffic generator prevents this invalid command from being issued by setting the burstlength to the highest valid value for the one command where it would overflow. The toolkit displays the address at which the burst length would have overflowed the address space. You can use the clear button to clear the write overflow status and burst length overflow address between successive runs.