@hacxx I was able to work out the problem. I implemented changes to the m5stack board_m5cores3 component which makes it enable the correct AXP2101 power management for I2C for the Port A Grove port when using USB-C power.

My issue was when using the device with the DIN base and the battery on and a sensor (CO2L) plugged into the Grove Port A (I2C), the device would be working. But if I disconnect USB-C from my computer and switch off the DIN base power, then switch the DIN base back on and plug USB-C back in (simulating a complete power outage of mains and battery) the device would boot loop with the message about SDA being held low.

The only way for me to get out of the loop is to unplug the CO2L from Port A. Then the device would boot on its next attempt and the I2C port recovery would be successful. Finally, I could plugin the CO2L, reset using the button, and everything would work again.

The issue was I needed to call M5.Power.setExtOutput during setup() of the BoardM5CoreS3 class from the https://github.com/m5stack/M5CoreS3-Esphome repo's components.

void BoardM5CoreS3::setup() { M5.begin(); ESP_LOGI(TAG, "Enabling 5V power output on the external ports"); M5.Power.setExtOutput(true); ESP_LOGI(TAG, "Turning off display panel backlight"); M5.Display.setBrightness(0); }

I implemented this in a custom component which I then add as an external_component to my ESPHome config. I added additional functionality in a separate component, to expose the AXP2101 battery level, charging status, etc. I also added an automation action to allow printing out debug state info from the AXP2101, to help with debugging the IRQ and other power management concerns.

In my ESPHome config it looks like this now and the CO2L sensor works reliably now without the controller going into boot-loops from various power loss/power source change scenarios:

esphome: name: ${hostname} friendly_name: ${friendlyname} platformio_options: board_build.flash_mode: dio board_build.mcu: esp32s3 board_build.f_cpu: 240000000L libraries: - m5stack/M5Unified external_components: - source: type: git url: https://github.com/terpasaurus-midwest/esphome-fork ref: m5cores3 path: my_components refresh: 2min components: [m5cores3_power, board_m5cores3] board_m5cores3: id: m5_board m5cores3_power: id: m5_power battery_sensor: name: "Battery Level" id: battery_level battery_present_sensor: name: "Battery Present" id: battery_present battery_charging_sensor: name: "Battery Charging" id: battery_charging

@williamsmaith ah thanks - for seeing the breadth of what’s possible. Messages are key and with ESP32 sharing BLE and WIFI it really is a game changer. Let me know if you want to try the system out.
Thanks

@Nooblearns not a good start if M5Burner doesnt play game before you even connect your M5Stick

You're absolutely right — modifying the setup to control the POWERKEY via GPIO is a smart move. It gives you direct control, which is crucial in both scenarios: resetting the modem when it stops responding to AT commands and waking it up from PSM. This kind of manual control adds reliability, especially in unattended or remote deployments. Thanks for pointing that out!

Welcome aboard! Great starting point with Python and the M5Stick/Flipper - hands-on tools make learning fun. For cybersecurity, focus on networking basics (try CompTIA Network+), then dive into Linux, bash, and tools like Wireshark or Nmap. Use your old computer for practice: install Kali Linux and start with safe, local labs like TryHackMe or Hack The Box. Keep learning, stay curious, and always practice ethically. You’re on the right path - just take it one step at a time!

@jvli5
I think your initialization is not done correctly. You can try to refer to other cases in the Project Zone.

@kenneth123 Just tried and logged in with no issues.

Hello @smily77

according to the schematic GPIO15 is used as reset pin (SOC_EXTRF_RST).

Thanks
Felix

Port A on the M5Dial is hardwired for I2C and shares pins with the internal screen, so repurposing it for TWAI/serial isn’t feasible without major conflicts. For dual CAN, consider using an external UART-to-CAN adapter or a separate GPIO header (if available) to assign alternate TX/RX pins for the second CAN interface.

@felmue This community website seems to have a problem with AI bots offering useless information as if they did not even read or understand the users question..

This is the second one in a few weeks.

@pmolsen Agreed, having those sensors built-in without the magnet would make things a lot easier. It would remove the need for external modules and avoid interference issues. A Plus3 with that setup sounds like a good improvement.

I am interested, although I think this will probably go over my head.

Hi everyone,

I’m currently evaluating M5Stack components (specifically the M5StickC Plus 1.1) for potential use in school-level STEM education. My goal is to verify a few key points and ensure the platform is both functional and student-friendly for early teens.

📘 Project Overview: Angle-Based LED Flasher
For initial testing, I'm using:

M5StickC Plus 1.1

Angle Unit (IMU sensor)

External LED

The idea is simple:
👉 As the device is tilted, the LED’s flashing rate changes, and the current rate is displayed on-screen.

With the right firmware, a connected LED and angle sensor should make this fully achievable. The Grove port makes sensor/LED integration easy, and the built-in screen is perfect for real-time feedback.

💻 Clarifying UIFlow & Output Features
✅ Is UIFlow online only?
UIFlow v1 is available in both online and offline modes (via downloadable desktop IDE).

UIFlow v2, at this point, is primarily online via https://uiflow2.m5stack.com.

You’ll need to use M5Burner to flash the correct firmware for either version.

⚙️ Is PWM or Output Control Supported?
PWM control (for blinking LED with variable timing) is not clearly exposed in UIFlow 2’s block environment as of now.

You may need to toggle GPIO pins manually or use UIFlow v1 for better output control using blocks.

Alternatively, UIFlow does allow Python-level customization if needed — but this might be a stretch for middle school use.

📺 Display Issues in Landscape Mode?
Yes, displaying values in landscape requires a bit of manual screen rotation.

Some values flicker unless refreshed properly; for stable display, use logic blocks to update only when the value changes significantly.

🧠 MicroPython vs Block Coding?
I completely agree that MicroPython or Arduino can feel too complex for early teens. That's why block-based programming like UIFlow is a far better starting point — especially in a school setting where time and experience may be limited.

🔬 Educational Perspective – From MITSDE
As a learner at MIT School of Distance Education (MITSDE), I’ve developed an appreciation for platforms that blend practical hardware use with real-world applications. MITSDE’s curriculum in technology and systems emphasizes:

Hands-on project building

Embedded systems basics

Logical thinking and block coding for beginners

This mindset fits perfectly with M5Stack’s mission — allowing students to explore real computing and electronics concepts in an engaging, approachable way.

🌟 Future Potential: If This Works Out…
Build a thermometer with ENV sensors

Light meters, timers, tilt-controlled games, sound alarms, etc.

All built using block code and plug-and-play modules — ideal for STEM labs

[https://mitsde.com/](link url)