I like the idea of using an RTOS to process engine data in conjunction with custom HDL cores for handling spark, fuel, generic pwm and calculating crank angle.
Coming from a Linux background I like the sound of Zephyr RTOS which has big investment by major hardware vendors including RISC-V
Depending on hardware constraints I'd like to take a similar approach to fuel calculations as enginelab and have the ability to graph any two data streams as a map and link them together for a final value.
Decisions still need to be made on how the RTOS feeds the final spark, fuel and gpio requirements back to the fuel, spark and pwm cores as ideally there could be a basic state machine that runs along side the RISC-V core to handle engine control in a limited capacity, similarly to limp mode in OEM control units.
Rust RTOS Tock has got interest from Google on their OpenSK Which is surprising when the manufacturer of the hardware they're using is pushing hard with Zephyr RTOS.
I think this might be a good base rather than waste too much time fudging other code
I like the idea of using an RTOS to process engine data in conjunction with custom HDL cores for handling spark, fuel, generic pwm and calculating crank angle.
Coming from a Linux background I like the sound of Zephyr RTOS which has big investment by major hardware vendors including RISC-V
Depending on hardware constraints I'd like to take a similar approach to fuel calculations as enginelab and have the ability to graph any two data streams as a map and link them together for a final value.
Decisions still need to be made on how the RTOS feeds the final spark, fuel and gpio requirements back to the fuel, spark and pwm cores as ideally there could be a basic state machine that runs along side the RISC-V core to handle engine control in a limited capacity, similarly to limp mode in OEM control units.