Hello @YO3HJV yes, I measured the current from the battery with this mA-meter and also used the AXP192 registers. Thanks Felix

@easytarget The internal battery have it's own protection module; if you really want to put another one in parallel with the internal one, choose one with a similar protection module. This would be the "next best practice" if you don't want to simpl replace the internal one with a bigger external one. Cheers, Adrian

Hi. Have you tried reading bytes from the GPS and displaying them on a serial monitor as they arrive as below, just to show you are getting data (if the serial setup is incorrect you should still receive data but it will be gibberish): // Serial is the serial monitor // Serial1 is the GPS data int intChar; char charChar; intChar = Serial1.read(); if(inChar != -1){ charChar = (char)intChar; Serial.print(charChar); } I have been using the M5Stack GPS v1.1 and it was set to 115200@7N1, not the advertised 115200@8N1 so might be an issue there (I got gibberish at first) Finally my M5Stack GPSv1.1 works fine with an Adafruit Itsy Bitsy 3v controller and an ESP32S3 based controller but not with the Seeed Wio Terminal. With the Seeed Wio Terminal I get nothing at all - no gibberish, absolutely nothing. It's as if the signal is not there (but it is !!).

Hello @drvval when I run M5Core2 v1.1 from battery, power consumption gets down to about 5.2 mA @ 4.2 V in ESP32 deep sleep. BTW: Interestingly when running from battery I can turn off the boost circuit. In my test I now only turn LCD backlight to zero and turn off boost circuit. When I turn LCD and/or TP off things start to go wrong. My guess is that ESP32 SPI / I2C bus gets confused if devices are suddenly disappearing. Thanks Felix

I should note that I am also using the SD card interface and whenever the SD is not detected on power up the display doesn't work either. I believe they are on the same bus.

Hello @eleonorafontana16 just to clarify - your current setup (controlling 2 servos using GPIO25 and GPIO26) doesn't include the GoPlus2 module anymore, correct? Thanks Felix

@robski not that I know of. As I mentioned, the USB-C works fine. It's the USB-A that is hit or miss on working. I think this is a mac issue as I search the net. Eg: here and here and mac ports Just was wondering if anyone has had this issue as well. I'm not stuck but my co-worker (not a developer) couldn't get the USB-A on a mac dongle to work. I just wanted her to use the Serial Monitor - as I implemented commands the user can type is to do an OTA update or other things. So they just needed a Serial Monitor (and this issue crept in). Thanks.

@GeorgeR Have a search for 'quadcopter battery' on Amazon (or your marketplace of choice) and you should find one of the right size and correct connector. I've bought a couple of batteries and charged them with the 'Timer Power Unit' for various projects. WARNING!! BEWARE! I've found about 50% of the batteries I've bought had the wires the opposite way round to that required by the M5Stack controllers. They will instantly kill your controller! Triple check the polarity before ever plugging them into your controller.

It looks like PlatformIO is still uploading your filesystem as SPIFFS despite setting board_build.filesystem = littlefs. This happens because the default partition table might not reserve space for LittleFS. Try creating a custom partition table that supports LittleFS and specify it in platformio.ini with board_build.partitions. Also, ensure your LittleFS_esp32 library is compatible with M5Core2. Without proper partitioning, mounting fails with corrupted directory errors like yours. Let me know if you want help generating a suitable partition CSV file!

Hello @hacxx please refrain from posting in year old threads which are already resolved. Thank you. Thanks Felix

@Boomvalt Xcode is OSX's dev environment and is needed for some low level functions needed for hardware programming even if you are not directly using it.

@kuriko Thank you for your hint. However, I don't know how it could help to solve my requirements. In M5StickC-Plus example, IMU will remain powered on and will send interrupt on gpio 35 on motion. In my requirement, axp2101 could send interrupt on power-on (usb), but its interrupt pin is not connected to esp32. AXP2101 usually wakes up esp32 by simply powering on esp32, it is not a real wake up by interrupt. Therefore, wake up by power-on (usb) works only if esp32 was powered off by axp2101 previously. I cannot power-off esp32 because it should also wake up on gpio interrupt from PIR.

for Hive MQTT below works for me Uiflow 2.2.5 [image: 1744880435095-mqtt-hive-m5stack.png]

Hello @Krmiller GetVBusVoltage() exists in M5Core2 library as well. See here. Thanks Felix

@pleister found the solution in rebuilding the extension https://github.com/curdeveryday/vscode-m5stack-mpy/issues/45