Best posts made by hacxx

It sounds like the SCL line on GPIO1 is stuck low, causing the bus to hang. Since your internal I2C on GPIO11/12 works fine, this suggests a hardware issue on Port A or interference on those pins. Double-check for any accidental shorts, damaged cables, or faulty devices connected to Port A. Also, try disconnecting all devices from Port A and test again. If the problem persists, it might be a hardware fault on the Core S3 board’s GPIO1 pin. Consider testing with a different device or contacting M5Stack support for hardware diagnostics.

For Core2 AWS Deep Sleep Wake:
The M5Stack Core2 AWS exposes ESP32 RTC GPIOs GPIO36 (VP), GPIO39 (VN), GPIO34, GPIO35, GPIO25, GPIO26, GPIO27, and GPIO32 for external wakeup triggers. Configure via esp_sleep_enable_ext0_wakeup() or esp_sleep_enable_ext1_wakeup(). Check the Core2 pinout to avoid conflicts with built-in peripherals.

Note: Some pins may require pull-up/down resistors. Test with low-power triggers (e.g., buttons) to verify wakeup reliability.

UIFLOW 2.0 has updated many units, and the SK6812 RGB LED support is now under the “Neopixel” or “Addressable LED” unit instead of “RGB LED.” Check for these new units in the device list. The functionality is similar but reorganized for better flexibility with different LED types. If you don’t see it, try updating UIFLOW to the latest version or check the official docs/forums for recent changes.

It sounds like your I2C works during setup but fails in the loop, which may indicate timing or bus handling issues on the STM32. Make sure you’re properly handling I2C interrupts and not blocking the bus in your main loop. Also, check that your I2C clock speed matches what the PPS module supports. STM32’s HAL I2C functions sometimes behave differently from Arduino’s Wire library, so review how you manage repeated start conditions and error handling. Double-check pull-up resistors on the I2C lines and confirm the voltage levels are stable at 3.3V during runtime.

Hi! As of now, there isn’t an official Eagle library specifically for the M5StampS3. You can try using a generic ESP32-S3 footprint or create a custom library based on the unit’s datasheet. Hopefully, M5Stack or the community will release official libraries soon.

Hi! This error often happens due to unstable USB connections or driver issues. Try these steps: use a different USB cable (preferably a high-quality, data-capable one), connect directly to your Mac’s USB port (avoid hubs), and restart your Mac before uploading. Also, check that your ESP32-S3 drivers are properly installed and up to date. Lowering the upload baud rate (e.g., from 921600 to 115200) in the Arduino IDE can improve stability. If it persists, try uploading from another computer to rule out hardware issues. Hope this helps!

Great to see UIFlow 2.0 making Wi-Fi access easier on the Tab5. Regarding your issue - yes, UIFlow’s interface thread keeps running in the background even when you execute custom MicroPython via serial. That’s why UI elements like “POWER” or “SLEEP” still respond. It’s part of the UIFlow runtime. For full control, consider disabling the UIFlow runtime before running your code.

The error means I2S port 0 driver wasn’t installed before uninstall was called. Make sure you call i2s_driver_install() successfully before attempting i2s_driver_uninstall(). Also, check that your code isn’t trying to uninstall the driver twice or uninstall before install. Reviewing the initialization sequence and adding error checks after install calls should help fix this issue. If you’re using legacy I2S, consider updating to the latest driver APIs for better stability.

I’m planning to use an M5Stack Core2 with ENV III and Soil Moisture units to monitor temperature, humidity, and soil moisture in my balcony garden. Data will be sent via MQTT to a local server for analysis and alerts. Looking forward to sharing updates!