Thanks for the information. That's damn impressive.
I worked for Ford for 4 year in powertrain doing "high-level drivers" for the fuel subsystem - injectors, fuel pump, etc. I initially did a few code changes on their PTEC module which had a PowerPC core, then I they switched over to Black Oak. It still had the PowerPC core, with the addition of TPU-A and TPU-B, which handled engine position, fuel and spark as well a few miscellaneous items. It was interesting migrating the code over to a new module and creating the API to work with the TPU. The Black Oak had an addition process to handle electronic throttle controller - HC12. After I left for about 11 years I worked with HC12 and HC12s. Finally we maxed it out and moved to a 32-bit processor Infineon Tri-Core. The thing is, it doesn't have 3 cores. Just 1. It took 2 guys a year or so to get the drivers configured, so we could start adding base and function software. BTW this is a transfer case controller. Since our OEM required us to move to global A, a ton more diagnostics had to be added - 137 diagnostic trouble codes. Next we move to global B, which means we have to AutoSAR compliant as well as all other ECU suppliers. Job security.
Anyway, being around embedded systems for my entire career I know the work that goes into development for the hardware design, configuring all the low-level drivers, writing the application code and implementing variants to accommodate different sensor inputs.
Hopefully Santa gets me a TT ECU-GN for Christmas.
