TPM compatiblity and state machine improvements #3
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
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.
This changes fixes issues with some TPM:
#2
and 2 other here:
denandz/lpc_sniffer_tpm#2
denandz/lpc_sniffer_tpm#3
It has been tested with a TPM that were working before (AT97SC3205 from Dell Optiplex 745) and 2 TPM that were not working before: STM N18FPVMT found in Dell Optiplex 980 and a SLB9635B found in SuperMicro motherboard.
The main changes is logging of message going from address 24 to 27. I've also done a rewrite of the state machine to comply with LPC/TPM protocol.