We are mostly focused in standby, not in stop

This commit is contained in:
rusefi 2022-10-03 19:37:01 -04:00
parent 87101854e6
commit 75bf7382a2
3 changed files with 6 additions and 1 deletions

View File

@ -35,6 +35,7 @@ STOP mode for F7 is needed for wakeup from multiple EXTI pins. For example PD0,
However, for F40X & F42X this may be useless. STOP in itself eats more current than standby.
With F4 only having PA0 available for wakeup, this negates its need.
*/
/*
void stm32_stop() {
// Don't get bothered by interrupts
__disable_irq();
@ -63,6 +64,7 @@ void stm32_stop() {
// Lastly, reboot
NVIC_SystemReset();
}
*/
/*
* Standby for both F4 & F7 works perfectly, with very little current consumption.
* Downside is that there is a limited amount of pins that can wakeup F7, and only PA0 for F4XX.

View File

@ -179,6 +179,7 @@ STOP mode for F7 is needed for wakeup from multiple EXTI pins. For example PD0,
However, for F40X & F42X this may be useless. STOP in itself eats more current than standby.
With F4 only having PA0 available for wakeup, this negates its need.
*/
/*
void stm32_stop() {
SysTick->CTRL = 0;
SCB->SCR |= SCB_SCR_SLEEPDEEP_Msk;
@ -206,6 +207,8 @@ void stm32_stop() {
// Lastly, reboot
NVIC_SystemReset();
}
*/
/*
Standby for both F4 & F7 works perfectly, with very little curent consumption. Downside is that theres a limited amount of pins that can wakeup F7, and only PA0 for F4XX.
Cannot be used for CAN wakeup without hardware modificatinos.

View File

@ -190,7 +190,7 @@ void runRusEfi() {
#endif
#if defined(STM32F4) || defined(STM32F7)
addConsoleAction("stm32_stop", stm32_stop);
// addConsoleAction("stm32_stop", stm32_stop);
addConsoleAction("stm32_standby", stm32_standby);
#endif