opentitantool: option for parsing BFV codes #25816
Merged
Conversation
This file contains 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
Given the hex value reported in the `BFV: xxxxxxxx` entry of the crash log, print the symbolic name of the error. Usage example: > bazel run //sw/host/opentitantool:opentitantool -- --rcfile-= bfv 50540d 0c4f5705 123 ... 0050540d: kErrorPersoTlvInternal 0c4f5705: kErrorOwnershipKeyNotFound 00000123: unknown error code Signed-off-by: Vadim Bendebury <vbendeb@chromium.org> (cherry picked from commit ee783ac)
timothytrippel
approved these changes
Jan 8, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Given the hex value reported in the
BFV: xxxxxxxxentry of the crash log, print the symbolic name of the error.Usage example:
Signed-off-by: Vadim Bendebury vbendeb@chromium.org
(cherry picked from commit ee783ac)