Toyota’s killer firmware: Bad design and its consequences – 10/28/13
The Center for Auto Safety is the nation’s premier independent, member driven, non-profit consumer advocacy organization dedicated to improving vehicle safety, quality, and fuel economy on behalf of all drivers, passengers, and pedestrians.
by Michael Dunn
On Thursday October 24, 2013, an Oklahoma court ruled against Toyota in a case of unintended acceleration that lead to the death of one the occupants. Central to the trial was the Engine Control Module’s (ECM) firmware.
Embedded software used to be low-level code we’d bang together using C or assembler. These days, even a relatively straightforward, albeit critical, task like throttle control is likely to use a sophisticated RTOS and tens of thousands of lines of code.
With all this sophistication, standards and practices for design, coding, and testing become paramount – especially when the function involved is safety-critical. Failure is not an option. It is something to be contained and benign.
So what happens when an automaker decides to wing it and play by their own rules? To disregard the rigorous standards, best practices, and checks and balances required of such software (and hardware) design? People are killed, reputations ruined, and billions of dollars are paid out. That’s what happens. Here’s the story of some software that arguably never should have been.
Click here to read the full story from the EDN Network