Repository navigation
Conversation
Signed-off-by: Paul Schumacher <paul.schumacher@amd.com>
Signed-off-by: Meghna Kondapalli <meghnak@xcomeghnak40x.amd.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
On VCK190, interface tile trace started on TRUE, which is asserted every cycle. At the end of the run, XDP flushes trace by generating the stop event, but TRUE immediately restarted trace and emitted a new start packet that got cut off at the end of the stream. hwanalyze can't decode a trace file that ends in a partial start packet, so it stopped decoding that file and those interface tiles never appeared in the decoded output (ERROR: PROF-HW-5.07).
This change starts AIE1 interface tile trace on USER_EVENT_2 instead, generated once after all tiles are configured, so trace can't restart after the flush. VEK280 will keep TRUE because it has no free user event and we were only seeing this issue on a VCK190.