WHY I3C BASIC IS PREFERRED MORE?
The I3C communication protocol (pronounced eye-three-see) is a MIPI Alliance standard developed by Sensor Working Group. The name refers to the bus's resemblance to I2C, as it uses the identical two-wire SCL and SDA lines and is backward compatible with I2C. (with some caveats). To get the full I3C standard, you must be a member of MIPI. However, the MIPI Alliance website offers a free download of a publicly available subset of the full specification called MIPI I3C Basic.
MIPI I3C v1.0 was the first public release of the I3C standard by the MIPI Alliance in late 2017. Members of the MIPI Alliance had access to the standard prior to its official release. In October of 2018, MIPI I3C Basic v1.0 was released. In December of 2019, MIPI I3C v1.1 was released. According to the MIPI I3C Basic specification, I3C consumes significantly less energy and has a faster bus speed than I2C. The ability of I3C to transition from open-drain to push-pull drive in certain modes enables the speed advantage over I2C. I2C operates with an open-drain drive at all times, limiting the signal's rising time (the signal is pulled high by a "slow" resistor). Once the initial bus arbitration has occurred, I3C can move from open-drain to push-pull communication, allowing for substantially faster communication (up to rates comparable with SPI).
External pull-up resistors are not required for I3C; the pull-up resistors are provided by the I3C master (s). I2C devices can communicate with I2C and I3C nodes at I2C bit rates when attached to an I3C bus. When an I3C node communicates with another I3C node, the standard permits the bit rate to rise. I2C slaves are supported on an I3C bus, but not I2C masters (the master on an I3C Basic must be an I3C device). To know more about the functionality of I3C Basic & for IP Cores with deep system-level capabilities, connect with us at www.digitalblocks.com
Comments
Post a Comment