You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a link to the OpenTitan documentation, but the documentation linked to describes a more recent version of the OpenTitan I2C IP. The actual implementation in this repository appears to come from somewhere around commit 02e36dfabcde185bec3fbe7 in the OpenTitan repository which has a slightly different register interface, particularly in how the NACK'd writes can be detected.
Also, the documentation says that registers 0x00 - 0x10 are not accessible, which is incorrect. We have been able to read meaningful values from register 0x00 (INTR_STATE) (and in fact, it seems to be the only way to detect NACKs in this particular version, since CONTROLLER_EVENTS doesn't exist.
The text was updated successfully, but these errors were encountered:
Thanks for raising this. You're right, the OpenTitan IP block has seen quite a few updates recently. It's probably worth integrating the new IP from upstream to not have to maintain the old version of the documentation here.
The information in https://lowrisc.github.io/sonata-system/doc/ip/i2c.html does not accurately reflect the I2C implementation used in this repository.
There is a link to the OpenTitan documentation, but the documentation linked to describes a more recent version of the OpenTitan I2C IP. The actual implementation in this repository appears to come from somewhere around commit
02e36dfabcde185bec3fbe7
in the OpenTitan repository which has a slightly different register interface, particularly in how the NACK'd writes can be detected.Also, the documentation says that registers
0x00
-0x10
are not accessible, which is incorrect. We have been able to read meaningful values from register0x00
(INTR_STATE
) (and in fact, it seems to be the only way to detect NACKs in this particular version, sinceCONTROLLER_EVENTS
doesn't exist.The text was updated successfully, but these errors were encountered: