EYE on NPI - NXP P3S0200GM I3C Switch with Hardware Select and Enable episode artwork

EPISODE · May 12, 2022 · 12 MIN

EYE on NPI - NXP P3S0200GM I3C Switch with Hardware Select and Enable

from Adafruit Industries · host Adafruit Industries

This week's EYE ON NPI has an extra I bonus feature - we're featuring the NXP P3S0200GM I3C Switch with Hardware Select and Enable. (https://www.digikey.com/short/td77904f) You might be thinking we made a typo there, as you may be familiar with I2C but have you heard of I3C? Yep, that's three I's for ya, and you'll probably start seeing more sensors, devices and microcontrollers that support I3C which is an extension of I2C with many improvements. I2C is a sensor interface you are probably well familiar with, just about every microcontroller has I2C hardware support, and about half of peripheral devices and sensors use I2C for data transfer or configuration. I2C is easy to wire up: you only need two data lines. It's a fairly simple overall communication system: each devices has a 7-bit address, with 1 bit for read/write commands, then data is sent after. You can put multiple devices on one I2C bus as long as the addresses don't collide, (https://learn.adafruit.com/i2c-addresses) great for low-pin-count setups or chaining. And, hey did you know that NXP invented I2C? Philips, which then became NXP, originally published version 1.0 the I2C specification in 1992 in app note UM10204 (https://www.nxp.com/docs/en/user-guide/UM10204.pdf) - and because it was a well-written, open, and royalty/license-free standard, the entire industry joined in. But, there are a few things about I2C that can drive folks a little batty. First up is the speed limitations. I2C uses pull-ups for raising the voltage on the 'open drain' connections, but it takes time to charge and drain the capacitance of lines and gate inputs through a resistor. I3C does not use external resistors, instead there's an active pull-up that transitions between Open-Drain and Push-Pull mode. (https://www.mipi.org/node/2604) This reduces power usage and allows I3C to run at a spicy 12MHz, well in line with SPI speeds. Next up, there's bus contention - woe is the engineer who has to deal with clock stretching on a bus, or missed clocks. I3C thankfully does not permit clock stretching! (https://www.mipi.org/node/1247) peripherals cannot take control of the clock by keeping it pulled down. Instead all devices must respect the clock. "But!" you are saying "what if I'm designing a peripheral and over I3C we get a sensor wakeup or read request, and I'm not ready to immediately answer in time?" Normally you'd have to have to either use polling for a data-ready bit (yuck, uses a lot of power, bandwidth and time) or you can use an IRQ pin. But if you're using IRQ pins then you've just lost the benefits of having a shared 2-wire bus! Well there's another nifty capability in I3C for in-band interruption management where the controller can hand off the bus to peripherals to notify when they are ready to be listened to. There's a great document from NXP showing the high and low level implementation / trace details of I3C vs I2C that we recommend you check out here (https://community.nxp.com/pwmxy87654/attachments/pwmxy87654/tech-days/256/1/AMF-DES-T2686.pdf) As you start adding I3C controllers and targets into your embedded systems, you may still find yourself dealing with address collisions, or maybe you want to have two controllers connect to one peripheral. Since I3C has a stricter timing requirement for dealing with the high speeds it can perform at, you'll want a switching chip that is designed for I3C. That's where the NXP P3S0200GM I3C Switch will come to your rescue. (https://www.digikey.com/short/td77904f) It's from NXP who helped bring I3C to market so you know it's going to work exactly as the specification intends and will also be back-compatible with I2C devices. And, best of all, the NXP P3S0200GM I3C Switch (https://www.digikey.com/short/td77904f) is in stock now for immediate shipment from Digi-Key, perfect for placement into your next design. Even if you're only using I2C right now, you'll be future-proof ready for when sensor and chip revisions start coming out with I3C support. Order today and you'll be switchin' by tomorrow afternoon.

This week's EYE ON NPI has an extra I bonus feature - we're featuring the NXP P3S0200GM I3C Switch with Hardware Select and Enable. (https://www.digikey.com/short/td77904f) You might be thinking we made a typo there, as you may be familiar with I2C but have you heard of I3C? Yep, that's three I's for ya, and you'll probably start seeing more sensors, devices and microcontrollers that support I3C which is an extension of I2C with many improvements. I2C is a sensor interface you are probably well familiar with, just about every microcontroller has I2C hardware support, and about half of peripheral devices and sensors use I2C for data transfer or configuration. I2C is easy to wire up: you only need two data lines. It's a fairly simple overall communication system: each devices has a 7-bit address, with 1 bit for read/write commands, then data is sent after. You can put multiple devices on one I2C bus as long as the addresses don't collide, (https://learn.adafruit.com/i2c-addresses) great for low-pin-count setups or chaining. And, hey did you know that NXP invented I2C? Philips, which then became NXP, originally published version 1.0 the I2C specification in 1992 in app note UM10204 (https://www.nxp.com/docs/en/user-guide/UM10204.pdf) - and because it was a well-written, open, and royalty/license-free standard, the entire industry joined in. But, there are a few things about I2C that can drive folks a little batty. First up is the speed limitations. I2C uses pull-ups for raising the voltage on the 'open drain' connections, but it takes time to charge and drain the capacitance of lines and gate inputs through a resistor. I3C does not use external resistors, instead there's an active pull-up that transitions between Open-Drain and Push-Pull mode. (https://www.mipi.org/node/2604) This reduces power usage and allows I3C to run at a spicy 12MHz, well in line with SPI speeds. Next up, there's bus contention - woe is the engineer who has to deal with clock stretching on a bus, or missed clocks. I3C thankfully does not permit clock stretching! (https://www.mipi.org/node/1247) peripherals cannot take control of the clock by keeping it pulled down. Instead all devices must respect the clock. "But!" you are saying "what if I'm designing a peripheral and over I3C we get a sensor wakeup or read request, and I'm not ready to immediately answer in time?" Normally you'd have to have to either use polling for a data-ready bit (yuck, uses a lot of power, bandwidth and time) or you can use an IRQ pin. But if you're using IRQ pins then you've just lost the benefits of having a shared 2-wire bus! Well there's another nifty capability in I3C for in-band interruption management where the controller can hand off the bus to peripherals to notify when they are ready to be listened to. There's a great document from NXP showing the high and low level implementation / trace details of I3C vs I2C that we recommend you check out here (https://community.nxp.com/pwmxy87654/attachments/pwmxy87654/tech-days/256/1/AMF-DES-T2686.pdf) As you start adding I3C controllers and targets into your embedded systems, you may still find yourself dealing with address collisions, or maybe you want to have two controllers connect to one peripheral. Since I3C has a stricter timing requirement for dealing with the high speeds it can perform at, you'll want a switching chip that is designed for I3C. That's where the NXP P3S0200GM I3C Switch will come to your rescue. (https://www.digikey.com/short/td77904f) It's from NXP who helped bring I3C to market so you know it's going to work exactly as the specification intends and will also be back-compatible with I2C devices. And, best of all, the NXP P3S0200GM I3C Switch (https://www.digikey.com/short/td77904f) is in stock now for immediate shipment from Digi-Key, perfect for placement into your next design. Even if you're only using I2C right now, you'll be future-proof ready for when sensor and chip revisions start coming out with I3C support. Order today and you'll be switchin' by tomorrow afternoon.

NOW PLAYING

EYE on NPI - NXP P3S0200GM I3C Switch with Hardware Select and Enable

0:00 12:40

No transcript for this episode yet

We transcribe on demand. Request one and we'll notify you when it's ready — usually under 10 minutes.

API Intersection Stoplight Building a successful API requires more than just coding. It starts with collaborative design, focuses on creating a great developer experience, and ends with getting your company on board, maintaining consistency, and maximizing your API’s profitability.In the API Intersection, you’ll learn from experienced API practitioners who transformed their organizations, and get tangible advice to build quality APIs with collaborative API-first design.Jason Harmon brings over a decade of industry-recognized REST API experience to discuss topics around API design, governance, identity/auth versioning, and more.They’ll answer listener questions, and discuss best practices on API design (definition, modeling, grammar), Governance (multi-team design, reviewing new API’s), Platform Transformation (culture, internal education, versioning) and more.They’ll also chat with experienced API practitioners from a wide array of industries to draw out practical takeaways and insights you can use.H TV Podcast Industries Chris Jones, Derek O'Neill and John Harrison. TV Podcast Industries TV Podcast Industries is a podcast that provides discussions and reviews of various TV shows, including recent popular series like Alien Earth, The Sandman, The Last of Us, The Boys, and Daredevil Born Again. They also cover shows such as Ironheart, Star Trek: Picard, The Rings of Power, and many more, spanning both Marvel and DC universes, as well as other genres. Heart to Heart Podcast One on One / Next Level Studios In the Heart to Heart Podcast, we talk to some of our favorite & most interesting people in the entertainment industry so you can feel empowered and learn that even in the most challenging of industries, where there’s a will there’s a way.Whether you’re an actor, a writer, a casting director, a talent rep, or just someone interested in the behind the scene happenings of the entertainment industry, this podcast will have something for you. NOW, this isn’t just another How To podcast for actors. Plenty of those shows already exist. In Heart to Heart, every guest will share stories inspired by their sometimes winding path to success on their own terms. Revisionist History Pushkin Industries Revisionist History is Malcolm Gladwell's journey through the overlooked and the misunderstood. Every episode re-examines something from the past—an event, a person, an idea, even a song—and asks whether we got it right the first time. From Pushkin Industries. Because sometimes the past deserves a second chance.To get early access to ad-free episodes and extra content, subscribe to Pushkin+ in Apple Podcasts or at pushkin.fm/plus.iHeartMedia is the exclusive podcast partner of Pushkin Industries.

Frequently Asked Questions

How long is this episode of Adafruit Industries?

This episode is 12 minutes long.

When was this Adafruit Industries episode published?

This episode was published on May 12, 2022.

What is this episode about?

This week's EYE ON NPI has an extra I bonus feature - we're featuring the NXP P3S0200GM I3C Switch with Hardware Select and Enable. (https://www.digikey.com/short/td77904f) You might be thinking we made a typo there, as you may be familiar with I2C...

Can I download this Adafruit Industries episode?

Yes, you can download this episode by clicking the download button on the episode player, or subscribe to the podcast in your preferred podcast app for automatic downloads.
URL copied to clipboard!