Hardware Event Trace - 2021.2 English

Versal ACAP AI Engine Programming Environment User Guide (UG1076)

Document ID
UG1076
ft:locale
English (United States)
Release Date
2021-12-17
Version
2021.2 English

The following table contains all the possible events produced during hardware event tracing. If looking at the ctf data produced by hwanalyze the description provides information about the event being called.

An example of how to read the event is if the functions event is selected only the FUN_CALL and FUN_RETURN are produced and provide details about the tile the function resides on and the program counter (PC), and whether the event is calling the function, or if the function is being called.

Table 1. Hardware Event Trace
Event Name Values Description
FUN_CALL <col, row, PC, val, info>

PC: function call instruction PC

Val: 0 or 2

Info:

calling function name with val 0

called function name with val 2

FUN_RETURN <col, row, PC, val, info>

PC: function return instruction PC

Val: 0 or 2

Info:

Returning function name with val 0

Returned function name with val 2

MEM_STALL <col, row, val, info>

Val: 23 (fixed)

Info:

Function name

MEM_STALL_RELEASE <col, row, val, info>

Val: 2 (fixed)

Info:

Function name

STREAM_STALL <col, row, val, info>

Val: 24 (fixed)

Info:

Function name

STREAM_STALL_RELEASE <col, row, val, info>

Val: 2 (fixed)

Info:

Function name

CASCADE_STALL <col, row, val, info>

Val: 25 (fixed)

Info:

Function name

CASCADE_STALL_RELEASE <col, row, val, info>

Val: 2 (fixed)

Info:

Function name

LOCK_STALL <col, row, val, info>

Val: 26 (fixed)

Info:

Function name

LOCK_STALL_RELEASE <col, row, val, info>

Val: 2 (fixed)

Info:

Function name

DMA_S2MM_RUNNING <col, row, ch, val>

Ch: channel ID

Val: 0 (activity ends)

1 (activity starts)

DMA_MM2S_RUNNING <col, row, ch, val>

Ch: channel ID

Val: 0 (activity ends)

1 (activity starts)

OVERRUN <col, row> Overrun occurred in tile <col, row>