What a silly thread this is. Some say making an ECU from a Pi is impossible or at least not sensible. Other say it can be done. The naysayers are told they are "dragged down by pathogens" or otherwise stupid and are losers.
Then we have this from sezyal:
So much nonsense BS and jargon split. There is no such a thing as realtime computer BS or non-realtime ,delayed maybe sleeping CPU! It doesn't matter at all....
Car is a mechanical thing, it doesn't need so fast processing anyways. Data you get from an oxygen sensor won't change in 1ms. Sensors are even not that fast.
So 1Ghz CPU is > DSP, microcontroller, realtime cpu(whoever invented that marketing term)
Which displays some ignorance and needs commenting on in case it leads readers astray.
"real-time" is a thing in computing. It is not just a marketing term. It does have a technical meaning. "real-time" is about the ability of your software to reliably hit timing deadlines. It is not about raw speed. As wikipedia says:
In computer science, real-time computing (RTC), or reactive computing describes hardware and software systems subject to a "real-time constraint", for example from event to system response. Real-time programs must guarantee response within specified time constraints, often referred to as "deadlines".
Systems like Unix/Linux are not designed to provide real-time guarantees. Rather they are designed to optimize throughput for a multi-user, multi-process, system. Often to the detriment of real-time behavior.
Anyway, I suggest the scientific approach. If one feels building an ECU from a Pi is a sensible goal and can even be done, then just try it. Please report back how it goes.