Refer to aiecompiler_trace_plio_options.cfg for the configuration:
[aie]
event-trace=runtime
broadcast-enable-core=true
num-trace-streams=16
event-trace-port=plio
trace-plio-width=128
xlopt=0
Here are some options definitions:
event-trace=runtime: Trace events are specified at runtime. This is the only possible option for hardware tracing.broadcast-enable-core=true: Ensures that the enable core signals are broadcasted so that all kernels start within a few clock cycles of each other.event-trace-port=gmio/plio: Selects the port type used for event tracing. GMIO is generally used for designs with limited PL resources, while PLIO is preferred for designs with sufficient PL resources.num-trace-streams=16: Sets the number of trace streams within the AI Engine array to be used for event tracing. The default is four streams, and the maximum is 16. Increasing the number of streams can reduce contention within the trace data path, especially in designs with a large number of active kernels. The drawback is that it would use more resources, making it more difficult for the router to route the AI Engine design by itself.trace-plio-width=128: Specifies the width of the PLIO trace interface.xlopt=0: Disables extra optimizations that could interfere with event tracing. Typically the compiler avoids inlining the kernels within the main function. This allows you to see each kernel as a separate entity in the trace and have a clear view of all iterations.