Hardware Podcasts

Tales from the Bringup Lab

Oxide and Friends · 7 Dec 2021 · 1h 42m · Episode 25

What this episode covers

Nathanael Huffman, Eric Aasen, and Rick Altherr of Oxide Computer Company recount the bring-up of their server board, detailing the debugging of an AMD SP3 Milan processor. They describe fixing a 'zombie board' caused by a schematic error in the power supply, resolving an I2C level shifter issue, and overcoming an infinite reset loop. The breakthrough came when Eric Aasen identified a firmware bug in the SDLE load simulator's handling of VOTF packets, followed by a final fix for swapped SPI data pins and broken test cables.

Most relevant to

early-stage companies

Topics

Mentioned

Companies
Oxide Computer Company, AMD, Renesas
Chips
SP3, Milan, iCE40, FTDI
Tools
SDLE, FLIR

Related episodes from other shows

Other shows on the same ground, closest first.

  • Embedded.fm · 59m

    203: Save My Board

    Charlie Ladd, a principal electrical engineer with experience in medical, FAA, and consumer products, discusses bridging the gap between hardware and firmware. He details his work on an oil quality sensor for VSI Oil and emphasizes the importance of designing for failure, using redundancy, and providing clear documentation like 'PickIO' spreadsheets and 'Theory of Ops' to help firmware engineers debug boards safely. Ladd also shares insights on the evolution of the industry, the value of mentorship, and how to stay current with new components through trade magazines and development boards.

    Embedded firmwarePCB design & layout
    9 chapters

  • The Spark Gap · 38m

    The Spark Gap - Episode 27

    Hosts Carl and Corey share embedded electronics horror stories, including Corey’s PCB layout error where a tool connected line and neutral, and Carl’s experience with a potato gun fireball. They discuss common design pitfalls such as incorrect through-hole sizing, voltage level mismatches between an FPGA and a 1.8V chip, and the leakage currents of unpowered ICs like FTDI chips. The conversation emphasizes the importance of reading datasheets, verifying Gerber files, and understanding power-up sequencing to avoid bricking components or causing shorts.

    PCB design & layoutDebugging & failure analysis
    8 chapters

  • Embedded.fm · 51m

    405: Bacta Tank for Your Brain

    Elecia White and Christopher White discuss Elecia's recent burnout while teaching her Making Embedded Systems course on Classpert, and Christopher's debugging of a subtle SPI + FreeRTOS bug on a Cypress PSoC chip. They also cover Elecia's recommendations for the book 'Thanks for the Feedback', the Wokwi simulator for Raspberry Pi Pico, and listener projects like Serial Wombat and Cyanobyte.

    Debugging & failure analysisFounder wellbeing
    6 chapters

  • The Amp Hour · 1h 15m

    Wrong Hardware, Wrong Software - Fugacious Fan Funding

    Dave Jones and Chris Gammell discuss the challenges of hardware development, including Chris's experience with a Texas Instruments high-voltage motor control kit that failed due to missing power factor correction, and a SparkFun MicroView firmware recall. They also analyze the economics of crowdfunding 3D printers, the triboelectric noise in cables, and recent industry acquisitions like Infineon buying International Rectifier.

    Crowdfunding & preordersMicrocontrollers & dev platforms
    9 chapters

  • Embedded.fm · 1h 01m

    38: Blame the Monkey

    Elecia White and producer Chris White discuss strategies for debugging 'insurmountable' problems in embedded systems, ranging from race conditions and stack overflows to non-reproducible hardware issues. They advocate for methodical approaches such as drawing system diagrams, writing detailed emails to clarify thoughts, and using the scientific method to isolate variables. The conversation also covers the importance of logging, reverting to known good code, and knowing when to walk away or accept a bug as a feature.

    Debugging & failure analysisEmbedded firmware
    8 chapters

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