The Spark Gap - Episode 18

The Spark Gap · 15 Oct 2014 · 47m

What this episode covers

Hosts Karl and Corey provide a technical overview of four common serial communication protocols used for chip-to-chip communication: UART, SPI, I2C, and CAN bus. They compare the protocols based on their wiring requirements, speed capabilities, duplexing modes, and signal integrity characteristics, noting that UART is simple but asynchronous, SPI is fast but point-to-point, I2C is multi-device but power-hungry due to pull-up resistors, and CAN bus offers robust differential signaling for noisy environments. The discussion highlights specific engineering trade-offs, such as the capacitance limits of SPI, the voltage level translation challenges in I2C, and the bus arbitration mechanics of CAN.

Mentioned

Companies
FTDI, NXP, Analog Devices
Also
UART, SPI, I2C, CAN bus, RS 422, RS485, LVDS

Other shows on the same ground, closest first.

  • The Amp Hour · 1h 05m

    A Noisy Rude Bus

    Hosts Chris Gammell and Dave Jones discuss the nuances of serial bus standards, specifically contrasting the chaotic, proprietary nature of CAN bus in automotive applications with the more standardized I2C and its successor I3C. They explore the practical engineering skills required for physical product development, such as using strain gauges and accelerometers for vibration and stress testing, and emphasize the importance of moving prototypes off the bench to test in real-world conditions. The conversation also touches on the impact of AI on engineering careers, the logistics of manufacturing in Mexico, and the technical details of new Nordic microcontrollers and Ray-Ban smart glasses.

  • Embedded.fm · 46m

    2: My Little Pony Stopped Outputting

    Alicia White of Logical Elegance and Jen Castillo compare multimeters and install a Saleae Logic USB Logic Analyzer to debug an SPI communication issue. White explains her company's budget constraints for purchasing an oscilloscope, leading to the decision to use the Saleae device for protocol analysis. They discuss the specific features of various multimeters, including models from Fluke, TPI, and Radio Shack, before successfully identifying a wiring error with the logic analyzer.

  • Embedded.fm · 1h 18m

    362: Permutations of Underscores

    Elecia White and Christopher White discuss Christopher's experience using Python and the `ctypes` library to interface with hardware via a CAN bus, highlighting the challenges of parsing split-bit fields. They analyze the Raspberry Pi Pico's programmable I/O features and debate the trade-offs between Arduino, Mbed, and bare-metal ecosystems regarding developer lock-in. The conversation concludes with advice on managing remote work, distinguishing between self-care and self-soothing, and strategies for knowing when to stop coding to avoid technical debt.

  • The Amp Hour · 1h 05m

    Mute Button Discipline

    Dave Jones and Chris Camel discuss the quirks of online circuit simulators like Falstad and LTSpice, specifically the confusing use of 'beta' for MOSFETs. They analyze Derek Muller's (Veritasium) follow-up video on energy flow in transmission lines, debating Poynting's theorem versus the lumped element model. The conversation shifts to embedded systems debugging with SEGGER tools, the ongoing microcontroller supply chain crisis, and the challenges of adopting open-source solar microinverters.

  • The Amp Hour · 1h 06m

    Pseudo Code...Pseudo Good

    Dave Jones and Chris Gammell discuss the engineering challenges of the Artemis moon landing program, citing Destin from Smarter Every Day's critique of NASA's reliance on politics over engineering. They then dive into a specific hardware design problem involving the Nordic nRF9160 and ESP32-C3 microcontrollers, where shared peripheral constraints forced a creative solution using SPI bus chip selects. The conversation concludes with an analysis of Siglent's new high-bandwidth oscilloscope ASIC and the complexities of smart home automation using Home Assistant and ESPHome.

The summary, chapters and topics are generated from the episode’s audio by this directory, not written by The Spark Gap. The episode itself belongs to its publisher.