Detailed Description

Initialization code and main status reporting look.

Date: Dec 25, 2013

Author: Andrey Belomutskiy, (c) 2012-2021

Definition in file rusefi.cpp.

Functions
void	rebootNow ()

void	scheduleReboot ()

void	onAssertionFailure ()

void	initEfiWithConfig ()

__NO_RETURN void	runMainLoop ()

void	runRusEfi ()

void	chDbgStackOverflowPanic (thread_t *otp)

Variables
bool	main_loop_started = false

static char	panicMessage [200]

static virtual_timer_t	resetTimer

static jmp_buf	jmpEnv

Function Documentation

◆ chDbgStackOverflowPanic()

void chDbgStackOverflowPanic ( thread_t * otp )

this depends on chcore.h patch +void chDbgStackOverflowPanic(thread_t *otp);

chSysHalt("stack overflow"); \
chDbgStackOverflowPanic(otp); \

Definition at line 314 of file rusefi.cpp.

                                            {
    (void)otp;
    strcpy(panicMessage, "stack overflow: ");
#if defined(CH_USE_REGISTRY)
    int p_name_len = strlen(otp->p_name);
    if (p_name_len < sizeof(panicMessage) - 2)
        strcat(panicMessage, otp->p_name);
#endif
    chDbgPanic3(panicMessage, __FILE__, __LINE__);
}

Here is the call graph for this function:

◆ initEfiWithConfig()

void initEfiWithConfig ( )

Now let's initialize actual engine control logic todo: should we initialize some? most? controllers before hardware?

Definition at line 253 of file rusefi.cpp.

                         {
    // If some config operation caused an OS assertion failure, return immediately
    // This sets the "unwind point" that we can jump back to later with longjmp if we have
    // an assertion failure. If that happens, setjmp() will return non-zero, so we will
    // return immediately from this function instead of trying to init hardware again (which failed last time)
    if (setjmp(jmpEnv)) {
        return;
    }
 
    commonEarlyInit();
 
#if EFI_WIFI
    startWifiConsole();
#endif
 
    // Config could be completely bogus - don't start anything else!
    if (validateConfigOnStartUpOrBurn()) {
        /**
         * Now let's initialize actual engine control logic
         * todo: should we initialize some? most? controllers before hardware?
         */
        initRealHardwareEngineController();
 
 
        // This has to happen after RegisteredOutputPins are init'd: otherwise no change will be detected, and no init will happen
        rememberCurrentConfiguration();
 
    #if EFI_PERF_METRICS
        initTimePerfActions();
    #endif
 
    }
}

Referenced by runRusEfi().

Here is the call graph for this function:

Here is the caller graph for this function:

◆ onAssertionFailure()

void onAssertionFailure ( )

Definition at line 165 of file rusefi.cpp.

                          {
    // There's been an assertion failure: instead of hanging, jump back to where we check
    // if (setjmp(jmpEnv)) (see below for more complete explanation)
    longjmp(jmpEnv, 1);
}

Referenced by chDbgPanic3().

Here is the call graph for this function:

Here is the caller graph for this function:

◆ rebootNow()

void rebootNow ( )

Definition at line 150 of file rusefi.cpp.

                 {
    NVIC_SystemReset();
}

Referenced by executeTSCommand(), and scheduleReboot().

Here is the caller graph for this function:

◆ runMainLoop()

void runMainLoop ( )

This loop is the closes we have to 'main loop' - but here we only publish the status. The main logic of engine control is around main_trigger_callback

Definition at line 287 of file rusefi.cpp.

                   {
    efiPrintf("Running main loop");
    main_loop_started = true;
    /**
     * This loop is the closes we have to 'main loop' - but here we only publish the status. The main logic of engine
     * control is around main_trigger_callback
     */
    while (true) {
#if EFI_CLI_SUPPORT && !EFI_UART_ECHO_TEST_MODE
        // sensor state + all pending messages for our own rusEfi console
        // todo: is this mostly dead code?
        updateDevConsoleState();
#endif /* EFI_CLI_SUPPORT */
 
        chThdSleepMilliseconds(200);
    }
}

Referenced by runRusEfi().

Here is the call graph for this function:

Here is the caller graph for this function:

◆ runRusEfi()

void runRusEfi ( )

we need to initialize table objects before default configuration can set values

Next we should initialize serial port console, it's important to know what's going on

Definition at line 174 of file rusefi.cpp.

                 {
    engine->setConfig();
 
#if EFI_TEXT_LOGGING
    // Initialize logging system early - we can't log until this is called
    startLoggingProcessor();
#endif
 
#if HAL_USE_WDG
    setWatchdogResetPeriod(WATCHDOG_RESET_MS);
    startWatchdog();
#endif // HAL_USE_WDG
 
#if EFI_PROD_CODE
    errorHandlerInit();
    errorHandlerShowBootReasonAndErrors();
#endif
 
#if defined(STM32F4) || defined(STM32F7)
    addConsoleAction("stm32_standby", stm32_standby);
#endif
 
    addConsoleAction(CMD_REBOOT, scheduleReboot);
#if EFI_DFU_JUMP
    addConsoleAction(CMD_REBOOT_DFU, jump_to_bootloader);
#endif /* EFI_DFU_JUMP */
 
#if EFI_USE_OPENBLT
    addConsoleAction(CMD_REBOOT_OPENBLT, jump_to_openblt);
#endif
 
    /**
     * we need to initialize table objects before default configuration can set values
     */
    initDataStructures();
 
    // Perform hardware initialization that doesn't need configuration
    initHardwareNoConfig();
 
  // at the moment that's always hellen board ID
    detectBoardType();
 
#if EFI_ETHERNET
    startEthernetConsole();
#endif
 
#if EFI_USB_SERIAL
    startUsbConsole();
#endif
 
#if HAL_USE_USB_MSD
    initUsbMsd();
#endif
 
    /**
     * Next we should initialize serial port console, it's important to know what's going on
     */
    initializeConsole();
 
    // Read configuration from flash memory
    loadConfiguration();
 
#if EFI_TUNER_STUDIO
    startTunerStudioConnectivity();
#endif /* EFI_TUNER_STUDIO */
 
    // Start hardware serial ports (including bluetooth, if present)
#if EFI_TUNER_STUDIO
    startSerialChannels();
#endif // EFI_TUNER_STUDIO
 
    initEfiWithConfig();
 
    // periodic events need to be initialized after fuel&spark pins to avoid a warning
    initPeriodicEvents();
 
    runMainLoop();
}

Referenced by main().

Here is the call graph for this function:

Here is the caller graph for this function:

◆ scheduleReboot()

void scheduleReboot ( )

Some configuration changes require full firmware reset. Once day we will write graceful shutdown, but that would be one day.

Definition at line 158 of file rusefi.cpp.

                      {
    efiPrintf("Rebooting in 3 seconds...");
    chibios_rt::CriticalSectionLocker csl;
    chVTSetI(&resetTimer, TIME_MS2I(3000), (vtfunc_t) rebootNow, NULL);
}