ESP32 Deep Sleep Current Draw with MCUboot

[tuna-f1sh]

Hello!

Got a challenging one. I'm developing for a ESP32S3 WROOM1 N16R16 - custom board with a workspace 'boards/' definition.

I successfully configured deep sleep when flashing the app directly. Current draw is ~140 uA (LDO and other bits on board create higher than ESP32S3 datasheet 8 uA, this is ok). If I build with --sysbuild, no hardware changes, only partitioning the deep sleep current increases by a factor > 10 to ~1.8 mA.

I've configured to use the SPIRAM with CONFIG_SPIRAM_MODE_OCT but this is the same for both the non-sysbuild and sysbuild. I'm using a RTC GPIO as the wake source, configured with:

esp_sleep_disable_wakeup_source(ESP_SLEEP_WAKEUP_ALL);
esp_sleep_disable_ext1_wakeup_io(0);
...
esp_sleep_enable_ext1_wakeup_io(BIT(vdd_det.pin), ESP_EXT1_WAKEUP_ANY_HIGH);

Deep sleep is entered with sys_poweroff().

I wonder if anyone with experience developing the ESP32 support has any ideas on what could being configured differently with MCUboot? I feel like it must be something at the MCUboot init stage and jump to the app.

What I've tried but doesn't seem to have made a difference:

• Adding esp_sleep_config_gpio_isolate(); ref
• Adding CONFIG_ESP_SLEEP_FLASH_LEAKAGE_WORKAROUND=y, CONFIG_ESP_SLEEP_PSRAM_LEAKAGE_WORKAROUND=y, CONFIG_ESP_SLEEP_MSPI_NEED_ALL_IO_PU=y - I know these should only relate to light sleep but...
  ref

Thanks!

[tuna-f1sh]

I think I got to the problem after checking peripheral register stages and finding no difference, manually setting esp_sleep_pd_config(..) for peripherals etc. with no fix.

I was calling sys_poweroff() to go into deep sleep. If call esp_deep_sleep_start() directly, the current draw is the same and as expected (140 uA) for the MCUboot build too. I still am not sure why there would be a difference between solo app and --sysbuild since they both call

zephyr/soc/espressif/esp32s3/poweroff.c

Line 10 in 3568e1b

void z_sys_poweroff(void)

.

I believe the issue is

zephyr/soc/espressif/esp32s3/poweroff.c

Line 13 in 3568e1b

esp_sleep_pd_config(ESP_PD_DOMAIN_RTC_PERIPH, ESP_PD_OPTION_ON);

forcing esp_sleep_pd_config(ESP_PD_DOMAIN_RTC_PERIPH, ESP_PD_OPTION_ON);.

I'm not sure why this is forced since it's handled in the HAL depending on if EXT0 is used: https://github.com/zephyrproject-rtos/hal_espressif/blob/c95b9e4781390ca2eafe10342b69fb11673e514e/components/esp_system/sleep_modes.c#L1280

[sylvioalves]

@raffarost would you take a look?