custom board canned tune process would need board-specific x86 binary (simulator or unit_tests) #6195
This commit is contained in:
parent
a40724304d
commit
fbdad77e58
|
@ -161,6 +161,12 @@ void onBurnRequest() {
|
|||
incrementGlobalConfigurationVersion("burn");
|
||||
}
|
||||
|
||||
/**
|
||||
* this hook is about https://github.com/rusefi/rusefi/wiki/Custom-Firmware and https://github.com/rusefi/rusefi/wiki/Canned-Tune-Process
|
||||
*
|
||||
*/
|
||||
__attribute__((weak)) void boardTuneDefaults() { }
|
||||
|
||||
// Weak link a stub so that every board doesn't have to implement this function
|
||||
__attribute__((weak)) void boardOnConfigurationChange(engine_configuration_s* /*previousConfiguration*/) { }
|
||||
|
||||
|
@ -682,6 +688,11 @@ void resetConfigurationExt(configuration_callback_t boardCallback, engine_type_e
|
|||
*/
|
||||
setDefaultEngineConfiguration();
|
||||
|
||||
/**
|
||||
* custom board engine defaults. Yes, this overlaps with (older) engine_type_e approach.
|
||||
*/
|
||||
boardTuneDefaults();
|
||||
|
||||
// set initial pin groups
|
||||
setDefaultBasePins();
|
||||
|
||||
|
|
Loading…
Reference in New Issue