|Trace packets are being dropped on certain streams. (This can be determined by observing black bars on event trace streams in the Vitis Analyzer GUI.)
|Option 1: Increase the number of trace streams coming out of AI Engine using the option below in
Option 2: Enable periodic event trace offload feature during run time in XRT flow. An example of xrt.ini file where,
Note: The periodic event trace offload feature is supported in XRT flow only and event trace port has to be PLIO in build.
|Kernel function names are not visible from trace.
|This could be because the kernel is inlined
either by the compiler or via an attribute. Apply
--xlopt=0 to compile the design or
specify kernel functions with
__attribute__((noinline)) attribute to disable kernel
|Kernels start time are off by more than one hundred cycles.
--broadcast-enable-core=true option to the compiler to
ensure the design starts all kernels in a few clock cycles
|Tool issues a warning message indicating trace buffer is full.
|Increase event trace buffer size.
For the XSDB flow, specify larger value with the
-depth option in the
AI Engine trace start
For the XRT flow, update
xrt.ini file and
Note: The following warning message is issued by both XSDB and XRT when the trace buffer is full.
|Need to know if the PL is sending or receiving data to/from the AI Engine as expected.
Add monitors on PL kernels and their memory-mapped AXI4 masters.
For example, to monitor every kernel master, add the following:
Running on hardware, add the following lines in
running the application on hardware,