Hello
I'm just asking if and how big the difference of the quiescent current between the ESP32 WROVER and ESP32 WROOM Module should be in deep sleep mode.
Thanks
Kilobyte
ESP32 WROVER pSRAM Quiescent current
Re: ESP32 WROVER pSRAM Quiescent current
Maximal standby current of ESP-PSRAM32 is 50 uA, but it is powered by VDD_SDIO and is powered down before entering deep sleep (same as Flash chip).
As a result, there is no difference in current consumption in deep sleep between ESP32 WROVER and ESP32 WROOM Module.
As a result, there is no difference in current consumption in deep sleep between ESP32 WROVER and ESP32 WROOM Module.
-
- Posts: 30
- Joined: Thu Jun 29, 2017 7:10 pm
Re: ESP32 WROVER pSRAM Quiescent current
Hi,
I measure when using the same code the esp-wroom-32 uses 7uA and the esp32 wrover uses 80uA. The underlying pcb is also the same.
I wonder what is extra needed for the esp32 wrover to get to the low current usage.
Thanks,
I measure when using the same code the esp-wroom-32 uses 7uA and the esp32 wrover uses 80uA. The underlying pcb is also the same.
I wonder what is extra needed for the esp32 wrover to get to the low current usage.
Thanks,
Re: ESP32 WROVER pSRAM Quiescent current
At the moment I only have esp32-wrover on ESP-WROVER-KIT board which is not suitable for deep sleep power consumption measurement.ginodecock wrote:Hi,
I measure when using the same code the esp-wroom-32 uses 7uA and the esp32 wrover uses 80uA. The underlying pcb is also the same.
I wonder what is extra needed for the esp32 wrover to get to the low current usage.
Thanks,
I've tested deep sleep power on ALB32-WROVER module (with 8MB Flash & 4MB psRAM) which probably has the same internal schematics as ESP32-WROVER and the results are:
- 5.5 uA when only RTC timer wake-up & wake-up from GPIO are enabled
- 32 uA when ULP wake-up is also enabled
- 300 uA when touch wake-up is enabled
Tested with deep sleep example from latest esp-idf.
To get this power consumption I had to configure some GPIOs at the begining of app_main():
Code: Select all
void app_main()
{
gpio_pad_select_gpio(12);
gpio_set_direction(12, GPIO_MODE_INPUT);
gpio_set_pull_mode(12, GPIO_FLOATING);
for (int i=32; i<34; i++) {
gpio_pad_select_gpio(i);
if (i < 34) {
gpio_set_direction(i, GPIO_MODE_INPUT);
gpio_set_pull_mode(i, GPIO_PULLUP_ONLY);
}
}
struct timeval now;
gettimeofday(&now, NULL);
...
...
Last edited by loboris on Sat Dec 23, 2017 11:41 am, edited 3 times in total.
Re: ESP32 WROVER pSRAM Quiescent current
Hmmloboris wrote:Code: Select all
for (int i=32; i<40; i++) { gpio_pad_select_gpio(i); gpio_set_direction(i, ***GPIO_PULLUP_ONLY***); if (i < 34) gpio_set_pull_mode(i, GPIO_PULLUP_ONLY); }
Re: ESP32 WROVER pSRAM Quiescent current
Just leftovers from testing, I'm aware it is "Hmm" code...WiFive wrote: Hmm
Last edited by loboris on Sat Dec 23, 2017 11:35 am, edited 1 time in total.
Re: ESP32 WROVER pSRAM Quiescent current
Now that you shared it at least fix the starred argumentloboris wrote: Just leftovers from testing, I'm aware it is "Hmm" code...
-
- Posts: 30
- Joined: Thu Jun 29, 2017 7:10 pm
Re: ESP32 WROVER pSRAM Quiescent current
This seems to do the trick.
These GPIO pins are not used in the schematic of the ESP32 Wrover.
Is the underlying cause the difference between hardware version REV0 en REV1 of the ESP32 chip?
These GPIO pins are not used in the schematic of the ESP32 Wrover.
Is the underlying cause the difference between hardware version REV0 en REV1 of the ESP32 chip?
Who is online
Users browsing this forum: ESP_mofeifei and 21 guests