@m5stack If I power down the M5StickC by pressing the power button for 6 seconds, the current consumption is 0mA, so the AXP192 can turn everything off, like IMU, display etc. How do I tell the AXP192 to only turn on the ESP32 and keep the IMU etc turned off?

That way I will only have the current consumption of the AXP192 and ESP32 (10uA).

Seems to me like the IMU MPU6886 is powered via VESP_3V3, which is driven by the AXP192's DC/DC-converter 1 DCDC1, which also supplies the ESP32.

According to the MPU6886 datasheet, the regular power consumption with all 6 axes on is around 2.8mA, which matches your observations of 2mA. You can use the low power modes down to 45µA (only Accelerometer), or Full-Chip Sleep mode at 10µA (see p. 11).

On power up the IMU defaults to Sleep Mode (see p. 32), so maybe it is sufficient to not initialize it. Otherwise you would have to turn it off by writing to register PWR_MGMT. For full power down, no standby must be set (see section 9.9, p. 52.)

Unfortunately the M5StickC-library does not offer an interface for any of those power management features.

@m5stack: It would be a big help to have power management support in the library, and an example that demonstrates different power consumption states (maybe with the coulomb counter to get a real integral power consumption). Also a great example to prove that M5StickC is usable as a wearable and standalone device for more than just a few minutes.

The RTC would be able to trigger an interrupt on a preset alarm time, or with a timer. But I'm not sure if this is sufficiently connected to the PMU AXP192 to wake it up from complete system power down. This would be something @m5stack could probably answer.

That way I will only have the current consumption of the AXP192 and ESP32 (10uA).

I've got my M5StickC in pieces trying to reduce power consumption for increased battery life, and I can see at least 20 resistors without even counting properly.

When will you be releasing the schematic?

I was looking for the schematic because I wanted to understand whether the IMU interrupt pins were routed to a GPIO.

Me too ! ! !

I was thinking that the one on Github was correct but is the old M5stick

I think it should be very beneficial to have he complete schematic and not just a block diagram (by the way not precise..ie RTC missing..)

At the end of the day M5stick C is a proto board (indeed very nice) done for makers and developers...people who want to exploit potential from your product and not having access to the schema seems a sort of contradiction

I hope you can release the schema and off course I respect anyway your philosophy

Davide

Thank you !

Block diagram level documentation showing the power management chip connections, would help those attempting to improve code to reduce sleep mode power consumption.

Hi,
M5StickC schematic is not permitted to be open source yet, maybe later. We have offered the block diagram on the back sticker of the device, include all components and pin layout. Do you think those info is enough ?

Not quite enough info. The question I have (and others too from another thread), is there any clamping or level shifting circuit (5V down to 3.3V) between the Grove port and I/O pins (G0, G26, G36) to the ESP32? If not, an external device (sensor) could pass 5V back into the M5stickC via Grove or I/O pins and damage the ESP32.

sure, it will available in next week

Did you release the schematic yet? Not sure how m5stack designed and built the m5stickC hardware without a finished schematic 🤷🏼‍♂️

As I am see, esp32 power connected to DC1 of AXP192.
LCD back light connected to LDO2 of AXP192.

Questions:

1. What connect to DC2, DC3, LDO1, LDO3?
2. Can I am reduce power consumption by power off LCD module (not backlight)?
3. Can I am reduce power consumption by power off MIC, RTC, GYRO?

May be schematics will be available soon? Please.

https://docs.m5stack.com/#/en/core/m5stickc