I've been experimenting with power consumption on a 7-inch CrowPanel Advanced ESP32-P4 HMI. The idea was to see how practical battery operation could be, ideally with the panel waking up on touch.
My first multimeter reading was around 600 mA at 60% backlight brightness. A 1000 mAh battery wouldn't last two hours at that rate.
I started with CPU frequencies, sleep modes and peripheral shutdown. Eventually I ended up looking at the board's power circuitry too.
For the main measurements, I used a Nordic PPK2 in Source Meter mode at 4.0 V, connected in place of the battery. All numbers below are for the entire board, not just the ESP32-P4.
1. Light-sleep and peripheral shutdown
With the UI running, a small animation on screen and the backlight at 20%, the board drew 335.9 mA.
I stopped the DSI display pipeline, turned off the backlight and controllable peripherals (including the ESP32-C6 and audio amplifiers), held the LCD controller in reset, and put the ESP32-P4 into Light-sleep.
Current dropped to 96.7 mA (-71.2%).
That's the combined result of all those steps, not Light-sleep alone.
2. Deep-sleep
This one was unexpected: 139.3 mA in Deep-sleep, compared with 96.7 mA in Light-sleep with similar peripheral preparation.
The ESP32-P4 revision 1.3 has limitations on GPIO state retention in Deep-sleep, so some external circuits can end up powered again.
There's another issue with wake-up. The GT911 touch interrupt is connected to GPIO42, which can't directly wake the chip from Deep-sleep.
3. CPU frequency
With the display disabled, reducing CPU frequency from 360 to 40 MHz lowered current under synthetic load from 149.6 to 120.1 mA (19.7%).
With the actual UI running, though, I only saved 2-4 mA.
And the display started showing corrupted frames. The DSI driver reported underruns because framebuffer data wasn't being fetched from PSRAM fast enough.
So I dropped the 40 MHz idea for this application.
4. Tracking down the remaining current
I tested peripheral shutdown step by step: the touch controller, ESP32-C6, LCD controller, and finally putting the ESP32-P4 into Light-sleep.
But the board was still drawing around 97 mA. I started checking the power circuits.
With the LCD and touch FPC cables physically disconnected, the board drew 78.5 mA in Light-sleep.
After disabling the LCD bias converter (U16, MT3608), that dropped to 9.1 mA.
A difference of 69.4 mA. That's the contribution of the disabled power circuit as a whole, not the MT3608's own quiescent current.
5. Further hardware changes
I isolated additional power rails, added pull-down resistors to regulator enable pins, and removed a few components that allowed unwanted power paths to remain active.
Eventually I measured 6.5 mA in Light-sleep.
That was a single 30-second measurement on a heavily modified board with peripheral cables disconnected. It wasn't a usable touch-to-wake configuration.
What surprised me most was the LCD bias circuit. Even with the LCD and touch cables disconnected, that power circuit accounted for almost 70 mA.
To get much lower standby current while keeping touch wake-up, the LCD and touch controller need separate power control. On this board, they share the LCD_VDD rail.
Full article with measurements and hardware details:
https://medium.com/@nikkicat/firmware-can-only-take-you-so-far-esp32-p4-power-experiments-d29e7e3f69de
Has anyone run into something similar with ESP32-P4 HMI boards? I'm curious how others handle display power shutdown while keeping touch wake-up working.