Posts made by hacxx

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.

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.

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.

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.

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.

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.

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!

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.

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.

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.

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.

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.

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.

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!

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.

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!

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!

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!

The rom/miniz.h error occurs because newer board definitions (3.2.x) removed legacy ESP32 support. Downgrading to 2.1.x works, but to fix it permanently:

Manual fix: Replace #include <rom/miniz.h> with #include <miniz.h> in pngle.c (as noted in the linked guide).

Disable auto-updates: In Arduino IDE, go to File > Preferences and uncheck "Check for updates on startup."

M5Stack isn’t abandoning older Cores, but newer SDKs drop deprecated APIs. If issues persist, stick with 2.1.x or modify the library.

It sounds like the 5V output on the M5Capsule may not be designed to supply higher current devices directly—30mA is very low. Unlike the M5GO, the Capsule likely has current-limited or protected output. You might try powering the camera from an external 5V source and just connect data lines to the Capsule. Also worth checking if there's a FET or regulator in the schematic limiting output.