Toyota's killer firmware

[DougW]

Just got back from a 3 day head cram course at Freescale in Detroit on there automotive multi core micros. I didn't meet a single person that could work on an engine and program this is what is lacking in programming. If you just do black box modules you will always have cross errors that you can't see, somebody has to have common sense somewhere in the loop. That being said turn the damn thing off or hang it on a guard rail don't just scream and sue. Tort reform
DougW

[ft_sjo]

This isn't 1985. It takes dozens, maybe hundreds of developers to produce what's inside the ECU in your car. Manufacturers buy in specialist skills represented as a complete ECU. Companies like Continental, Bosch, Denso etc., they provide a boxed service/product to the OEM, which works out much, much cheaper than doing it in-house.

[DougW]

Originally Posted by ft_sjo

This isn't 1985. It takes dozens, maybe hundreds of developers to produce what's inside the ECU in your car. Manufacturers buy in specialist skills represented as a complete ECU. Companies like Continental, Bosch, Denso etc., they provide a boxed service/product to the OEM, which works out much, much cheaper than doing it in-house.

Yea I get that, that's what I do when I'm not working on engine development or chassis controls but the problem still is there regardless of the current method of producing code. It's important for the programmer to know that an error on spark can kill an engine while a fuel error usually doesn't. What I do and have done since the 80's is connect the gear heads to the nerds, giving respect to both groups talents in the aftermarket. As more control is given to electronics DBW, SBW, BBW etc more testing is done on simulators that are controlled by "SAY IT" software not real world because it cost more time to market and money to run all the test. This is our reality and mistakes will happen so turn the damn car off or hang it on a guard rail.
DougW