There are just a few hardware tools currently on the market for I3C development -- the bulk of which are tailored for the tall task of IP verification and silicon-validation. However as I3C-capable devices make their way onto dev kits and into the hands of firmware developers and embedded systems teams, a market for tools more suitable for traditional development and debugging will grow and test equipment vendors will follow. This page intends to track the release of suitable tools for I3C development.
Products in this category can be used to emulate I3C devices and behave as an I3C controller or I3C Target. These devices typically include the ability to intentionally inject errors in order to test how other devices handle the test cases. Usually, they also have software support which can provide careful timing analysis to ensure behavior is in accordance with the specification even at the physical layer. Products in this category also serve as a case study for why companies shouldn't let their engineers name the products ;-)
Products in this category can be used to observe / record the transactions on an I3C bus, decode the data, and provide a level of analysis suitable for firmware development and debugging. However, these devices are unable to actively participate on the I3C bus -- it cannot perform the functions of an I3C controller nor as an I3C target. These can be used to aid in timing analysis, but the primary use is for observing the data being transferred on the bus, and not necessarily the performance of the physical layer of the protocol.
* At this time, the Saleae Logic software does not include a protocol decoding support for I3C. We at Binho have developed an I3C Basic Protocol Analyzer Plugin for Saleae Logic which is available for purchase separately. Several licensing tiers are available. You can find the details on our I3C Basic Protocol Analyzer Plugin page.
Read More from I3C Cafe...
The iMX RT Crossover Microcontrollers are an interesting beast. They've got some interesting bells and whisltes, but the real reason that I'm writing about them today is due to the fact that the RT500 and RT600 series devices feature I3C peripherals.
Aside from I3C-capable Controllers and Targets, another category of devices that are imperative for successful and wide-spread industry adoption of the I3C protocol are interface devices such as switches/muxes, buffers/level-shifters, etc. Diodes Inc. recently announced[pdf] their first I3C interface device, the PI3CSW12, a 1:2 Mux/DeMux with Output Enable control signal.
While we're eagerly awaiting STMicro to introduce their first micronctroller which features an I3C peripheral, their MEMS sensors team has already launched several devices to mass production. This gives me even more hope that their first micrcontroller with I3C support is just barely over the horizon.
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.