Hello @eleonorafontana16

I don't know whether it will affect one or the other or both long term. The fact that both use the same I2C address is like talking to two people with the same name. Some answers might get lost due to both people responding at the same time with different answers.

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

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

Hi all,

I have been looking for the answer to my problem and my best guest might be the fact that they both are using PortA, thus the competition.

Is there a way to switch from one sensor to another to get a reading from both?

Thank you in advance :)

@paulasousa it may be a cause of code changes in the libraries. You need to check the documents for the update records.
Probably better to rebuild from scratch

@perlix
Hi, are you sure to remove the line 'Serial.begin(115200);' in setup() and not change it to 'Serial.begin(9600);' or something else? I remove this line and compile it , a lot of error occured. Any advise. Thank you.

What about M5CoreS3? Doesn't seem to have BL pin defined. Can it be used with TFT_eSPI?

I had this. Take it apart, disconnect battery, wait a minute or two, plug it back in. Something in the pmic is buggy and this resets it then it works.

@IndianaTux
this works on my CoreS3, directly turns off LDO2

#include <M5CoreS3.h> #include <Wire.h> void setup() { // put your setup code here, to run once: Wire1.beginTransmission(0x34); Wire1.write(0x12); Wire1.write(0b01001011); // LDO2, aka OLED_VDD, off Wire1.endTransmission(); }