I managed to decrease it to about 150ms but that's still a lot for what I should be doing. Did you try the option I mentioned above? Is GPIO low on power on (or esp_rom_disable_logging)? Bootloader logging as minimal as acceptable? I think a typical application with all optimisations should be able...

Hello @aleksboshnakov, I just found your message but later. Want to add something to this discussion. When the chip starts the boot loader take place but you can start your code that can check some conditions and then continue to sleep or wake up after timeout or pin state change and load software ...

I can't understand then what the deep-sleep mode is for if every time the device wakes up it has to bootloader.

After I tried light sleep I realized that it resumes the code from the point where the device goes to sleep.

Thx.

Hi, I am new to esp32. In the last two days I have tried to run different types of code and I have focused on how deep-sleep works that I can't understand. Is it normal that when the device wakes up it goes into the bootloader? Is it possible to avoid the bootloader and on wake up to resume the code...