| Issue ID | 775297 |
| Internal NHTSA # | 10318345 |
| Manufacurer | TOYOTA MOTOR CORPORATION |
| Brand | TOYOTA |
| Model | CAMRY |
| Model Year | 2010 |
| File date | 01/01/10 |
| Component | UNKNOWN OR OTHER |
| Product type code | VEHICLE |
| Description of the problem | Information redacted pursuant to the freedom of information act (foia), 5 u. S. C. 552(b)(6) from:[xxx] subject:toyota comments: i recall a similar problem with military aircraft, in which the engineers (myself included), could not isolate a system error. It was repeatedly fixed with no success. The problem fell down to a firmware error, on which the software was running. The firmware logic code was a third party provision to the system, and none of the engineers had real access to the logic circuitry. The firmware tested fine, and ran the test code as well, with no errors. It wasn't until the system was fully operational, that the system threw the errors. Since it was the firmware that threw the errors, none of the sensors or any of the system logs caught the problem. The vendor of the firmware "assumed" it was always the user code "the oem" that was at fault, and any log was aimed at monitoring the software execution, and not the firmware processing. In watching the major auto manufacturer come to his knees, it struck me as to how similar, the situation seems in this case, to what we experienced, in the air force. Perhaps there should be some modicum of consideration to the firmware architecture in your investigation, and not just the software. Just a thought for you to have fun with. Davec from nhtsa web site. |
| Vehicle Mileage at Failure | |
| Number of Occurences | 1 |
| Source of the issue | NHTSA WEB SITE |
| City and State | PORTLAND, OR |
| VIN pattern | XXXXXX |
| Was vehicle invloved in a crash? | N |
| Was vehicle involved in a fire? | N |
| Was incedent reported to police? | N |
| Was medical attention required? | |
| Was part original equipment? | |
| No. of injured persons | |
| No. of fatalities | |
| Date of purchase | 07/08/26 |
| Was original owner? | N |
| Anti-lock brakes | N |
| Cruise control | N |
| Number of cylinders | |
| Drive train type | |
| Transmission type | |
| Vehicle speed | |
| DoT tire identifier | |
| Tire size | |
| Location of tire code | |
| Type of tire failure code | |
| Was defective tire repaired? | |
| Date of manufacture | |
| Type of child seat code | |
| Type of restraint | |
| Dealer's name | |
| Dealer's telephone number | |
| Dealer's city | |
| Dealer's state code | |
| Dealer's ZIP code |