Earlier this week NXP published an "I3C Interface Devices" page on their website. This is not a very profound occurrence, although it does in fact confirm their upcoming line of I3C-capable temperature sensors.
On a deeper level, this continues to signal NXP's commitment to invest in building out the I3C ecosystem of supported devices. As of the writing of this article, many manufacturers don't have a separate category for I3C products -- it gets buried on their device datasheets, or at most, surfaced as a simple bullet point that it's a supported communication interface on a given device. This has been our primary motivation for maintaining a list of I3C-capabel devices, since it's so hard actually searching for devices based on whether or not they support I3C. I really hope that other device manufactures follow suit.
Awkwardly enough, though, the I3C Devices page makes no reference to their I3C-capable Microcontrollers and Microprocessors. I understand those don't necessary fit in with the "interface devices", but in my opinion, that's a huge, missed opportunity to direct folks to their iMXRT600 and RT500-series, LPC5500-series devices that have I3C peripherals.
Read More from I3C Cafe...
Proactive standardization of a USB-to-I3C Bridge paves the way for a cohesive I3C ecosystem without the quirks of manufacturer-specific implementations.
NXP acknowledges upcoming I3C-capable line of temperature sensors and make their I3C products easier to find. Kudos to their marketing team!
MIPI® and I3C® are registered trademarks owned by MIPI Alliance. I3C BasicSM, Debug for I3CSM, I3C HCISM and DisCo for I3CSM are service marks of MIPI Alliance. I3C Cafe is an independent publication (blog) and is not affiliated with nor sponsored or endorsed by the MIPI Alliance. Saleae® and Saleae Logic® are registered trademarks owned by Saleae Inc.