If I Only Changed the Software, Why is the Phone on Fire?: Embedded Debugging Methods Revealed...
This new book manages the unthinkable- it conveys crucial technical information to engineers without boring them to tears! In this unique reference, expert embedded designer Lisa Simone provides the solutions to typical embedded software debugging problems from a fresh new perspective. She introduces a team of engineers who readers will recognize from their own workplaces, and then confronts them with real-world debugging scenarios of progressive complexity, drawing the reader into the "mysteries” with their new fictional colleagues, and guiding them step-by-step toward successful solutions.
Table of Contents
Introduction
Chapter 1: The Case of the Irate Customer: Debugging Other People's Code, Fast
Chapter 2: The Newest Employee: Learning the Embedded Ropes Through Code Inheritance
Chapter 3: It Compiles with No Errors; It Must Work! Integrating Changes in a Larger System
Chapter 4: The Case of Thermal Runaway: Rare Transient Bugs are Still Bugs
Chapter 5: The Case of the Creeping Slider Carriage and the Case of the Hesitating Clock: Alternate Methods of Understanding System Performance
Chapter 6: If I Only Changed the Software, Why is the Phone on Fire?
Chapter 7: The Case of the Rapid Heartbeat: Meeting the Spirit of the Requirement
Chapter 8: What Kind of Error Message is "lume Fault"? When all of the Symptoms Seem Impossible
Chapter 9: When It's Not Hardware, It's Software. And Vice Versa. Blurring the Interface.
Chapter 10: Li Mei's List of Debugging Secrets
·Unique format casts the reader as "technical detective" by presenting a new mystery in every chapter
·Not another dry technical book! Conversational tone and intriguing quandaries draw the reader into the action, while teaching crucial debugging skills
·The final chapter, a summary of the smart debugging techniques introduced throughout the book, is a quick reference to help solve future problems
Why Read This Book
You will read real-world, step-by-step debugging case studies that show how to isolate root causes at the hardware/software boundary, use instrumentation effectively, and reduce time-to-resolution for field failures. The narrative style makes techniques memorable while giving you pragmatic checklists and approaches you can apply on your next impossible bug.
Who Will Benefit
Firmware engineers and embedded systems developers who need to diagnose intermittent, timing, and hardware-interaction bugs faster and with less trial-and-error.
Level: Intermediate — Prerequisites: Comfort with C and basic microcontroller concepts, basic electronics (signals, power, IO), and familiarity with simple debugging tools (serial printf, debuggers, oscilloscope basics).
Key Takeaways
- Apply systematic root-cause analysis and stepwise isolation for embedded faults.
- Use oscilloscopes, logic analyzers, and in-circuit debug hardware effectively to observe hardware/software interactions.
- Design and add lightweight instrumentation (traces, assertions, watchdogs) to capture non-deterministic failures.
- Identify and fix timing, interrupt, and concurrency bugs common in firmware.
- Create reproducible test cases and regression checks to prevent regressions and speed future debugging.
- Communicate and triage field problems using structured approaches that preserve evidence and minimize invasive changes.
Topics Covered
- Introduction — the case-study approach
- The Case of the Irate Customer: Debugging other people's code, fast
- The Newest Employee: Learning the embedded ropes
- Intermittent Failures and the Art of Reproducibility
- Hardware/Software Interfaces: Power, IO, and Signals
- Timing, Interrupts, and Concurrency Troubles
- Instrumentation: Logging, Traces, and Assertions
- Tools of the Trade: Oscilloscopes, Logic Analyzers, JTAG and ICE
- Root Cause Analysis and Fault Isolation Strategies
- Field Debugging, Burn-in, and Test Harness Design
- Teamwork, Communication, and Managing Customer Incidents
- Checklists, Templates, and Practical Debugging Recipes
Languages, Platforms & Tools
How It Compares
Similar in practical focus to Elecia White's Making Embedded Systems but more explicitly case-study and debugging-oriented; overlaps with the problem-solving advice in Diomidis Spinellis' Effective Debugging but is targeted to embedded hardware/firmware.
Related Books
