Add I3C decoder #128
Open
Add I3C decoder #128
Conversation
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
Support decoding I2C legacy, I3C Standard Data Rate (SDR) and I3C In-Band interrupt (IBI) transfers. For IBI, does support Mandatory Data Byte (MDB) and extra bytes. Does not support decoding Common Command Code (CCC), MDB values. An IBI and I2C read transfer are ambiguous, therefore, collect addresses from I3C SDR transfers to differentiate subsequent IBI from I2C read.
Detect CCCs, and if is a CCC ENTDAA, follow state machine flow that extracts the PID, BCR, DCR and assigned DA.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Tries to decode most I3C SDR and I2C legacy transfers.
As an observer, there is some "ambiguity", so the decoder will collect known i3c address to mark further transfers as i3c instead of i2c.
In particular, I am pretty sure a
will be detected as either an i2c or i3c ibi transfer.
even with looking forward, I think there is no reliable way of differentiate an IBI from a Read Transfers without 7'h7E Address.
Making this initial version public since resolves the most common pain-point of decoding i3c:
the transition and parity-bit that differ in logic from usual i2c ack/nack.
So, even though not perfect, maybe useful for most use cases.
Based on the i2c decoder.
aux:
https://github.com/gastmaier/sigrok-test/tree/decoder-i3c
https://github.com/gastmaier/sigrok-dumps/tree/decoder-i3c