At times while developing your project, you might introduce changes in your host or kernel code that will completely alter the contents or quality of the various build and run summaries produced by the tool. Your existing reports and analysis data will be overwritten unless you manually save the relevant files. The Archive Summary command lets you save all relevant files with an open Link Summary or Run Summary.
Select Report Navigator and select Archive Summary. This opens the Archive Summary dialog box as shown below.
menu command, or right-click a summary in theArchive file names must have the extension of link_summary.archive, or run_summary.archive to be recognized by the Vitis analyzer. The contents of the archive depend on the summary report being archived.
The contents of the Link Summary include these file extensions:
- Binary container(s)
- .xclbin
- Kernel(s)
- .xo
- System/platform diagram
- .json
- System estimate
- .xtxt
- Guidance
- .html, .pb
- Timing summary
- .rpt
- Utilization(s)
- .xutil
- HLS synthesis report
- Report
The contents of the Run Summary include these file extensions:
- Run summary
- .run_summary
- System diagram
- .run_summary
- Platform diagram
- .run_summary
- Guidance
- Not required, generated using via perf_analyze and the profile_summary.csv
- Profile summary
- profile_summary.csv
- Application timeline
- timeline_trace.csv
- Waveform report
- .wdb
hwanalyze
to display the trace report. In this case, the tool will prompt
you for the location of the AI Engine
compile_summary, and will update the
run_summary file on disk. If you archive the
run_summary before providing this location, you will not be
able to view the trace report from the archived run_summary. You can also choose to save the .xclbin file extension, any compiled kernel object file extensions (.o and .xo), and the original source file extensions (.cpp, .c, and .cl) used to generate the summary reports.
profile_summary.csv
, and optionally profile_kernels.csv
.vitis_analyzer design.archive
archive_summary -help