01-12-2021 10:38 AM
I created a kernel and i run it on the board, but i noticed that the execution time of the kernel is not the same showed in the post-cosimulation with vitis hls. How can i perform a profiling of the kernel when running on the board?
01-12-2021 09:12 PM
Hi @Davix ,
In order to enable profiling, you can just add the following in the xrt.ini -
In order to observe the waveforms as well you may add "timeline_trace=true" as well. Both the infos will be captured in a run_summary file which can be observed using the following -
vitis_analyzer <name of the run_summary file>
01-13-2021 01:16 AM
Hi @ViratAgarwal ,
I read this from the vitis document. It says that using Vitis IDE the xrt.ini file is automatically generated, but i cannot find this file in the workspace. How i can solve this problem?
01-13-2021 02:49 AM
Hi @Davix ,
Kindly follow the following steps to set modify the xrt.ini in the Vitis IDE-
1. Create the IDE project and build it for the respective flow.
2. Select Run Configurations in the drop down menu next to the Run button.
3. System Project Debug -> <project_name>-Default ->Main -> Xilinx Runtime Profiling -> Edit -> Select the required option (I guess it will be OpenCL detailed profile summary and timeline trace in your case) -> Apply -> Run.
These settings will be reflected in the generated xrt.ini (Observable in the xrt.ini present in the <Project_name>-Default_<project_name> dropdown) and create a Run summary which includes the data of the timeline trace.
In order to observe the timeline_trace follow the following steps-
1. Go to the Assistant and open the <Project_name> [Host] dropdown
2. Select the dropdown of the flow you are running for -> Double click the Run_Summary (xclbin) option.
3. A Vitis Analyzer window will pop up and all the info in the run summary can be observed using that. The Timeline trace can be observed under the Application Timeline section of the same.
01-13-2021 02:56 AM - edited 01-13-2021 02:58 AM
I'm stuck at point 3 of the first part. When i run it shows an error : "Could not connect to host '192.168.0.1' specified in the target 'Linux Agent'