Your setup sounds doable! The ATOM Lite ESP32 can control two SERVO2 modules (12 servos each) without major issues, but powering 24 servos may require careful battery and power management. Using separate battery modules with a single charging base is smartâjust ensure proper wiring and charging circuits. For streaming camera data over USB-C, the ATOM Lite might struggle; upgrading to an ESP32-C3 or Core might be better. LEGO framing is a great idea for prototyping! Start small, test servo control and power, then scale up step by step.
Posts made by hacxx
-
RE: Making a Robot: USB-C -> ATOM -> 2x SERVO2 ?
-
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.
-
timescamps of the photos taken by V-training
To fix incorrect timestamps in V-Training photos, update your device's firmware, check and set the RTC (sync via Wi-Fi or manually), and reconfigure the app. Also, format the SD card to FAT32. If issues persist, try a factory reset.
-
RE: M5Stick C - Cannot flash firmware
Yes, this is a common issue with M5Stick C flashing. Try holding the G0 button while connecting the USB cable to enter bootloader mode, then start the flash. Also, double-check your USB drivers and try a different USB port directly on your PC (avoid hubs). If problems persist, adding a 10”F capacitor between EN and GND can help stabilize the reset line. Make sure the serial port is correctly selected, and close other apps using it. This usually resolves the âFailed to connect to ESP32â errors.
-
RE: M5Dial port A as RX / TX interface for CAN module?
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.
-
RE: LittleFS problem with M5core2 and PIO
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!
-
RE: GPIO ports for the grove connector?
For the M5Stack Core2, Grove Port A uses I2C on GPIO 21 (SDA) and GPIO 22 (SCL). However, when using a Pb.HUB, you're communicating with the hub over I2C, and each connected unit (like relays or RGB) is addressed virtually via the hub.
Since openHASP doesn't natively support Pb.HUB devices, you canât directly control GPIOs through it. Instead, youâd need custom firmware or integrate via ESPHome or Arduino to bridge Pb.HUB control with openHASP.
TL;DR: GPIO 21/22 for I2C, but control of devices via Pb.HUB needs extra handling outside openHASP.
-
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: UiFlow 2.0 discuss(how-to, bug, feature request or sometings)
Thanks for sharing the UiFlow 2.0 resources! I appreciate having a dedicated space for bugs, how-tos, and feature requests. Does anyone have tips on avoiding common firmware burning errors, especially with account binding? Also curious if thereâs a timeline for the full API docs release. Looking forward to seeing how this evolves!
-
RE: M5Stack GPS module (M003) finds no satellites
Hey Dennis, sounds like youâve covered most of the basics. A few things to check: make sure the antenna switch (INT/EXT) is physically set correctly on the module. Also, the NEO-M8N can take a few minutes for a cold startâtry leaving it powered outside for 15â20 minutes. Lastly, ensure it has a clean 3.3V power source; voltage drops can affect satellite acquisition. If none of that helps, try updating the GPS firmware via u-center. Two dead modules is unlikely, but not impossible. Good luck!