Next week, MIPI Debug Working Group Chair Enrico Carrieri and working group member Matthew Schnoor will take an in-depth look at the recently released MIPI Debug for I3CSM v1.0, which allows system designers to dynamically debug and test application processors, power management integrated circuits, modems and other power-managed components.
JEDEC Solid State Technology Association (JEDEC) and MIPI Alliance have enjoyed a long liaison relationship of collaboration, as the two organizations serve some similar but also different applications and ecosystems. When we work together closely—as in development of JEDEC’s newly announced JESD79-5 DDR5 (Double Date Rate 5) standard—it results in better outcomes and broader market opportunities for all of our combined stakeholders.
Interested in an in-depth discussion of the I3C ecosystem and a look at the new features in MIPI I3C® v1.1? Join I3C Working Group Chair Ken Foust (Intel) for MIPI's second webinar of 2020, "Beyond Sensors: What's New in MIPI I3C v.1.1," on Wednesday, 12 February (08:00 Pacific).
Q: What makes the newly released MIPI I3C® v1.1 different from v1.0, and why is it important to developers?
I see Version 1.0 as setting a new baseline. We came together to make an interface that would dramatically simplify the integration of sensors and address many of the key pain points that all of us in the industry were dealing with when working with I2C and SPI interfaces. We think we accomplished that with v1.0—anywhere sensors are used, MIPI I3C belongs. Now v1.1 is the first update to build on that foundation.
The MIPI Discovery and Configuration (MIPI DisCoSM) Base Specification, which simplifies the software integration of external devices in mobile and mobile-influenced systems, now forms the basis of a new specification for integrating MIPI I3C® components.
The growing range of DisCo specifications define the properties of MIPI devices and components, and conveys those properties to operating systems in an architecturally defined manner. The DisCo Base Specification, along with class specifications for various MIPI interfaces, eliminates much of the work of developing and implementing drivers for external devices. For system developers, this can shorten time to market and cut system development cost.
Several months ago, MIPI I3C BasicSM, a subset of the MIPI I3C bus interface, was made available to the broader developer community without MIPI membership to foster greater interoperability and innovation in industries beyond mobile, including IoT and automotive.