@michapr Can you please try latest actual Arduino core and if the behaviour is still there Arduino core 3.2.0-rc2?

Yes, it is the same for me with 3.3.0

You may need to addesp_sleep_pd_config(ESP_PD_DOMAIN_VDDSDIO, ESP_PD_OPTION_OFF). That may require a longer sleep time. If you can't guarantee that you will be in sleep for seconds (so that you can turn off the flashmem), then you won't be able to get to the lowest consumption levels.

Hi@michapr

is this issue still valid considering the comments above?

Yes, it's still the same. I cannot useesp_sleep_pd_config(ESP_PD_DOMAIN_VDDSDIO, ESP_PD_OPTION_OFF) because need shorter sleep times.

The code can't change how the power domains work. Can you please explain what would be the solution you are looking for from this issue?

I understand that there may be no other solution for this chip, but I was somewhat surprised because the data sheet specified much better values for light sleep mode (without restrictions).
In my application—battery-powered sensors—the processor should go into light sleep mode both after the measurement and during the measurement. Deep sleep mode is out of the question because it requires a restart (and reinitializes the sensors).
The same applies to use in conjunction with LoRa modules (for example), where the “waiting time” for the gateway's response can be bridged by a light sleep mode.

So I think there maybe no solution - should look for another chip...

How do you measure the current?
It is very hard to measure it right, unless you have some proper tools to measure it like the Power Profiler Kit II from Nordic, or a similar device.

Still it is easy to overlook some unintended leak currents like from voltage regulator, pins pulled up or down, USB to serial adapters, etc.

How do you measure the current?

I'm using for all my work the Nordic Power Profiler Kit II.

Still it is easy to overlook some unintended leak currents like from voltage regulator, pins pulled up or down, USB to serial adapters, etc.

I don't think so, because the deep sleep current is <10uA, as expected.

OK, so we have established you have the proper tools ;) (Also love my PPK-II :) )
Other difference can still be that there are still parts active and/or pins maybe pulled high or low causing some current draw through those resistors.
250 uA over 3V3 is still in the order of 13 k, so it can still be some pull-up/down resistor.

Other unexpected power consumers can be for example if some internal device is still active which keeps the ABP frequency active.
You may need to look at the Technical Reference manual for this as it is quite elaborate in what may be kept active and what not.
Since the high resolution clock runs internally at 480 MHz (I think also for the C6) via some PLL circuits, I would not be surprised if this draws upto this amount of current (or even more)

Does theIDF example give you the expected results?

Other difference can still be that there are still parts active and/or pins maybe pulled high or low causing some current draw through those resistors.
250 uA over 3V3 is still in the order of 13 k, so it can still be some pull-up/down resistor.

But in this case the deep sleep current would be >10uA ... (same sketch, only other mode), right?
I also think about any other internal device, that's why was asking about any idea... I thought somebody else also had same issue before.

Does theIDF example give you the expected results?

Yes, if I remember right tried this "official" Light Sleep Example too - but made then all final tests with Arduino IDE (see sketch above)

Somebody know an ESP32 board with a real low light sleeping (and deep sleeping) current?
I had heard that the ESP32H4 was developed for this purpose, but it does not seem to be readily available yet (in the case of light sleep in Zigbee devicesespressif/esp-zigbee-sdk#501 (comment)).

As this issue became more of a discussion type. I have transferred it to the discussion.

You can still comment on the new discussion type and have a follow-up.

Kind regards.