Never mind I2C - now there's I3C

Go To Last Post
7 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

MIPI Alliance wrote:

MIPI I3C is a bus interface for connecting sensors to an application processor. It is a core sensor integration technology that can combine multiple sensors from different vendors in a device to streamline integration and improve cost efficiencies. It gives developers unprecedented opportunity to craft innovative designs for any mobile product, from smartphones, to wearables, to safety systems in automobiles. 

 

MIPI I3C can integrate mechanical, motion, biometric and environmental, and any other type of sensor. It incorporates key attributes of the traditional I2C and SPI interfaces to provide a new, unified, high-performing, very low power solution. The technology is implemented on a standard CMOS I/O. It uses a two-wire interface, which reduces pin count and signal paths to offer system designers less complexity and more flexibility. It can also be used as a sideband interface to further reduce pin count. MIPI I3C supports a minimum data rate of 10 Mbps with options for higher performance high data rate modes, offering a substantial leap in performance and power efficiency compared with previous options.

 

Additional technical highlights include multi-master support, dynamic addressing, command-code compatibility, and a uniform approach for advanced power management features, such as sleep mode. It provides synchronous and asynchronous time-stamping to improve the accuracy of applications that use signals from various sensors over time. It can also batch and transmit data quickly to minimize energy consumption of the host processor. 

MIPI I3C is developed by the MIPI Alliance Sensor Working Group. 

 

http://mipi.org/specifications/i...

 

Sadly, it seems you have to shell-out $$$ in membership fees to see the actual spec.

 

Whitepaper via EE Times (requires login)

http://www.analog-eetimes.com/Le...

 

http://www.analog-eetimes.com/si...

 

 

Update: Whitepapaer direct from MIPI - no login required

http://mipi.org/whitepaper/intro...

Top Tips:

  1. How to properly post source code - see: https://www.avrfreaks.net/comment... - also how to properly include images/pictures
  2. "Garbage" characters on a serial terminal are (almost?) invariably due to wrong baud rate - see: https://learn.sparkfun.com/tutorials/serial-communication
  3. Wrong baud rate is usually due to not running at the speed you thought; check by blinking a LED to see if you get the speed you expected
  4. Difference between a crystal, and a crystal oscillatorhttps://www.avrfreaks.net/comment...
  5. When your question is resolved, mark the solution: https://www.avrfreaks.net/comment...
  6. Beginner's "Getting Started" tips: https://www.avrfreaks.net/comment...
Last Edited: Fri. Jan 13, 2017 - 10:37 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

https://xkcd.com/927/

https://imgs.xkcd.com/comics/standards.png

The mipi paper promises "drastically lower cost" for the 2 pcb traces of i3c compared to i2c...

Is that before or after you pay for the spec & membership fees? (in money or time).

Looks like a lot of marketing crap to me.

Doing magic with a USD 7 Logic Analyser: https://www.avrfreaks.net/comment/2421756#comment-2421756

Bunch of old projects with AVR's: http://www.hoevendesign.com

Last Edited: Fri. Jan 13, 2017 - 01:43 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

It seems there is no "standard" for standards!  q:-)

 

 

 

(Possum Lodge oath) Quando omni flunkus, moritati.

"I thought growing old would take longer"

 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Surely the MIPI Alliance has made a massive difference to the market.

 

Without them,   every manufacturer would use different standards to ensure incompatibility.

Ok,   they might think that it will tie customers to their "brand" but it stifles small start-ups and any product development.

 

Of course,  some protocols/interfaces may not be successful.   If thought goes into the design process,   it gets a good take up.

ARM Cortex is a good example.

 

David.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

ki0bk wrote:

It seems there is no "standard" for standards!  q:-)

Oh yes there is:

 

BS 0:2016 A standard for standards: https://www.bsigroup.com/Documen...

 

https://www.bsigroup.com/en-GB/s...

 

 

Top Tips:

  1. How to properly post source code - see: https://www.avrfreaks.net/comment... - also how to properly include images/pictures
  2. "Garbage" characters on a serial terminal are (almost?) invariably due to wrong baud rate - see: https://learn.sparkfun.com/tutorials/serial-communication
  3. Wrong baud rate is usually due to not running at the speed you thought; check by blinking a LED to see if you get the speed you expected
  4. Difference between a crystal, and a crystal oscillatorhttps://www.avrfreaks.net/comment...
  5. When your question is resolved, mark the solution: https://www.avrfreaks.net/comment...
  6. Beginner's "Getting Started" tips: https://www.avrfreaks.net/comment...
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

awneil wrote:

ki0bk wrote:

It seems there is no "standard" for standards!  q:-)

Oh yes there is:

 

BS 0:2016 A standard for standards: https://www.bsigroup.com/Documen...

 

https://www.bsigroup.com/en-GB/s...

 

 

I stand corrected! 

 

 

(Possum Lodge oath) Quando omni flunkus, moritati.

"I thought growing old would take longer"

 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Somehow, you always get somebody on your standards committee determined to make sure your standard is brain-damaged so nobody will adopt it.

If you don't know my whole story, keep your mouth shut.

If you know my whole story, you're an accomplice. Keep your mouth shut.