• Obecnie brak na stanie
If I Only Changed the Software, Why is the Phone on Fire?: Embedded Debugging Methods Revealed
search
  • If I Only Changed the Software, Why is the Phone on Fire?: Embedded Debugging Methods Revealed
ID: 173001
Lisa Simone
Wycofany
 

Wysyłka gratis

darmowa wysyłka na terenie Polski dla wszystkich zamówień powyżej 500 PLN

 

Wysyłka tego samego dnia

Jeśli Twoja wpłata zostanie zaksięgowana na naszym koncie do godz. 11:00

 

14 dni na zwrot

Każdy konsument może zwrócić zakupiony towar w ciągu 14 dni bez zbędnych pytań

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

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
173001

Produkty z tej samej kategorii (16)