[ate] extract personalization FW hash from perso blob#239
Merged
timothytrippel merged 1 commit intolowRISC:mainfrom Jun 22, 2025
Merged
[ate] extract personalization FW hash from perso blob#239timothytrippel merged 1 commit intolowRISC:mainfrom
timothytrippel merged 1 commit intolowRISC:mainfrom
Conversation
moidx
approved these changes
Jun 21, 2025
The personalization firmware includes the hash of itself in the perso blob it sends to the host. We update the ATE DLL to parse this data and write it to the registry along with the other DUT data. Signed-off-by: Tim Trippel <[email protected]>
timothytrippel
force-pushed
the
extract-perso-fw-hash
branch
from
ab14e4b to
cb7f6b3
Compare
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.
The personalization firmware includes the hash of itself in the perso blob it sends to the host. We update the ATE DLL to parse this data and write it to the registry along with the other DUT data.
Note: this depends on #237; only review the last commit.