[XDP] Fixed runtime summary payload key name#9426
Merged
jvillarre merged 1 commit intoNov 11, 2025
Merged
Conversation
Signed-off-by: Vinod Pangul <146476973+vipangul@users.noreply.github.com>
jvillarre
approved these changes
Nov 11, 2025
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.
Problem solved by the commit
This is double commit of #9425
For Vitis designs, generated runtime summary wasn't generating payload keyname as expected.
Bug / issue (if any) fixed, which PR introduced the bug, how it was discovered
Generated vitis designs summary had a field named payload_16bitEnd instead of payload_16bitEnc.
How problem was solved, alternative solutions (if any) and why they were rejected
Fixed a typo in expected payload keyname to payload_16bitEnc
Risks (if any) associated the changes in the commit
Low
What has been tested and how, request additional testing if necessary
It has been already verified that original test works with the updated key field name.
Documentation impact (if any)