4 ms·
That's got to include stuff like the stereo and navigation systems, which seems like cheating. The engine-management and safety-related systems are bound to be
by Lagged2Death 14y ago
That's got to include stuff like the stereo and navigation systems, which seems like cheating. The engine-management and safety-related systems are bound to be much smaller, and certainly don't need to me so large.
- TheAmazingIdiot 14y agoMy dad is an acoustical and electrical engineer who works for heavy vehicle industries. On one project, a burner controller, he used a PIC microcontroller. I think the capacity of onboard storage was 48k. He didn't add any extra storage. I could be slightly wrong about the exact specs. I do arduino mainly.
- JonnieCache 14y agoThey are attack surfaces. Everything in the car is networked. Look at the paper: you can attack the engine through the gps. Maybe that was a different paper but I think it's in there.
- Lagged2Death 14y agoThey are attack surfaces ... you can attack the engine through the gps. Sure, but the "attack surface" of the engine management firmware itself isn't enlarged by the presence of an insecure GPS system, is it? I don't know if the people developing engine management firmware think about fire-walling themselves off from the rest of the in-car network. Certainly, they should. If they do, then the size of the code in the rest of the car doesn't seem relevant in terms of securing the really important stuff.