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.
Best posts made by hacxx
-
RE: Core S3 I2C Issue: SCL is held low on the bus
-
RE: ECHO not working
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.
-
RE: [UIFlow 2.0] Thank for UIFlow2.0 for Tab5, but...
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.
-
RE: Controlling a PPS module with an STM32 Nucleo board instead of an M5 Core controller
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.
-
RE: 2024 Community Challenge Growing green.
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!
-
RE: No RGB LED unit for UIFLOW 2.0?
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.
-
RE: RTC Pins Exposed for Deep Sleep Wake?
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.
-
RE: Help: A fatal error occurred: No serial data received.
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!
-
RE: eagle lib...
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.
-
RE: Set hostname using W5500
The W5500 Ethernet library for Arduino does not natively support setting a DHCP hostname in its standard implementation. If you're using Ethernet.h, it lacks this functionality. For advanced DHCP options like hostname, consider using the EthernetENC or UIPEthernet library, which offer extended DHCP support. Alternatively, youâd need to modify the DHCP client in the library to include the hostname in the DHCP request packet manually.
Latest posts made by hacxx
-
RE: RTC Pins Exposed for Deep Sleep Wake?
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.
-
RE: Controlling a PPS module with an STM32 Nucleo board instead of an M5 Core controller
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.
-
RE: No RGB LED unit for UIFLOW 2.0?
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.
-
RE: ECHO not working
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.
-
RE: Core S3 I2C Issue: SCL is held low on the bus
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.
-
RE: eagle lib...
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.
-
RE: Where do I start???!!!
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!
-
RE: [UIFlow 2.0] Thank for UIFlow2.0 for Tab5, but...
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.
-
RE: Error: Detected a whitespace character in project paths.
This error usually happens when your project path includes spaces (e.g., /Users/Your Name/Documents/...). Try moving your project to a folder without spaces in the path, like /Users/YourName/Projects/M5StackAWS. Then re-open the project in VS Code. That should fix the issue without needing to modify the ini file.
-
RE: A fatal error occurred: MD5 of file does not match data in flash!
This error usually means the uploaded firmware didn't flash correctly. Try these steps:
Use a different USB cable and port. Press the reset button on your M5Stack before uploading. Make sure you have the latest Arduino M5Stack libraries and board definitions. Try erasing the flash completely using esptool (esptool.py erase_flash). Reboot your PC and M5Stack.
If it persists, it could be a hardware fault, but most often itâs a flashing or connection issue.