🤖Have you ever tried Chat.M5Stack.com before asking??😎

Categories

  • Firmware updates, Hardware Revisions, New Product info can be found here.

    75 Topics
    826 Posts
    KhanFromNorthK
    You can continue developing on the M5Stack Core2 reliably. The key is to bypass UIFlow entirely and use MicroPython directly through Thonny or VS Code.
  • M5Stack Events

    8 Topics
    31 Posts
    kurikoK
    @Apex574R Does the Userdemo firmware running normally?
  • Wish for a feature that doesn't exist yet? this is the place to ask for it. we will collect all the requirements and enquiry's and who knows ... sometime wish might come true!

    222 Topics
    676 Posts
    R
    I took a closer look and compared M5StampS3A vs M5StampS3 BAT and I must say that it is not possible to do any piggyback for pin mapping at the M5StampS3A level since ESP32-S3FN8 vs ESP32-S3-PICO-1-N8R8 have differences in the number of GPIOs (6 pins error), see the difference table below: [image: 1774204115000-f8a8e80c-1dca-472a-ab48-dac7e6656c42-image.png] So it only remains for M5Stack team to upgrade M5StampS3A for 2/8 PSRAM, i.e. have M5StampS3B version.
  • Forum rules - Announcements - General chit chat (ESP-32, ESP-8266, IoT, Raspberry Pi etc...)

    971 Topics
    3k Posts
    D
    @2-4-6-h8 I am experiencing the same issue. I've registered on this site (obviously) and confirmed my email address. The Android app just spins when I try to register on it. I attempted update the StackChan's firmware but when I connected to my Wifi, it restarted on its own. Now when I click on the "Change Wi-Fi" section under setup, it shows me the QR screen to download the app, then just shows me the StackChan ID. I It seems no one is monitoring these forum posts, as a lot of threads are going unanswered. I hope this can be resolved because this is been a frustrating and disappointing experince thus far.
  • Core and Modules info.

    3k Topics
    14k Posts
    D
    Your RFID 2 module is likely not broken. The "Failed authenticating" error is the key clue here. Mifare 1KB cards use sector-based authentication with crypto keys. Bruce (and most generic RFID readers) will attempt the default keys (e.g. FF FF FF FF FF FF or A0 A1 A2 A3 A4 A5) to authenticate, but if FlipperZero or NFC Tools wrote data using custom or non-default keys, authentication will fail even though the UID and card type are read correctly. Things to try: Test with a blank/factory card. If it reads fine, your module is working. Check what keys were used when writing via FlipperZero or NFC Tools and make sure Bruce is configured to use those same keys. If the card was written with default keys, try a different card; it may have been locked or write-protected. The fact that UID, ATQA, and SAK are being detected correctly strongly suggests the module is functional.
  • Projects Sharing.

    487 Topics
    2k Posts
    ZeloksaZ
    [image: 1778484757935-fb78d00d-9a67-4b0e-992f-caad9d17786a-image.jpeg] Hello everyone! I've just released my new firmware for the Cardputer: IMU Acoustic Analyzer. This project transforms your device into a professional-grade acoustic scleroscope, allowing you to measure the structural hardness and elasticity of real-world surfaces. ⚠️ Important: How it works (and how to drop it) This is a precision physical instrument. It does not come with a pre-filled encyclopedia of materials-you train it yourself. By standing the Cardputer on its edge (SD card slot facing UP) and letting it naturally tip over and fall flat onto a table or floor, the internal IMU records the micro-impact. It calculates the material's properties and saves the acoustic profile. Later, it can instantly identify which surface you dropped it on. The Drop Technique: Let it fall naturally. Do not apply downward force. Even a 1-degree tilt upon impact or hidden supports under a table will alter the acoustic stiffness! Durability: Do not be afraid to use it. During development, I dropped my Cardputer over 1000 times using this exact edge-drop method (including onto hard tiles). Because it simply tips over from a standing position, the device easily survives without any damage. ✨ Technical Features 4-Dimensional DSP Engine: Polling the BMI270 at 1600Hz, the custom DSP doesn't just look at peak impact. It calculates MaxG (hardness), Ratio (elastic rebound), flight time, and AUC (Area Under Curve) to measure the true physical impulse and viscosity of the impact. "Zero-Shot" Physical Insight: Even if a surface is not saved in your database, the analyzer evaluates the raw physics and gives you an instant diagnostic (e.g., Ultra-Hard | Elastic or Firm | Dampening). 🕹️ Controls [ 1 ]: Start 3-Drop Measurement. [ 2 ]: Add New Material (5-Drop Calibration). [ 3 ]: Open Database List. [ < / , ] & [ > / / ]: Navigate Database Pages (Left / Right). [ 1 - 4 ]: Delete a specific material from the current Database page. [ ESC / ` ]: Global Cancel / Return to Main Menu. [ - / _ ] & [ = / + ]: Decrease / Increase system volume (emits an acoustic test click). 📥 Download You can flash it right now via M5Burner - just search for IMU Acoustic Analyzer or Zeloksa. You can also find the .bin release on GitHub: 🔗 https://github.com/Zeloksa/IMU-Acoustic-Analyzer I would love to hear your feedback. Let me know what materials you scan and how your calibration profiles look!
  • This is the place to discuss driver issues, M5 burner troubleshooting, and development of software compatible with M5Stack

    3k Topics
    10k Posts
    RunaqueR
    Additional finding: Secondary firmware bug — boot sequence crash on cold boot (MEPC: 0x00000006) While investigating the sta.scan() crash, I discovered a second distinct firmware bug affecting the Tab5 in UIFlow2 v2.4.4. Description: On every cold boot, the device crashes during UIFlow2's initialization sequence before any user code runs. The device automatically reboots and boots successfully on the second attempt. Crash signature: Guru Meditation Error: Core 1 panic'ed (Instruction access fault). Exception was unhandled. MEPC : 0x00000006 MCAUSE : 0x00000001 MTVAL : 0x00000006 Key observation: The stack contains 0x7474696c (ASCII: "litt") pointing to a crash inside UIFlow2's LittlevGL/LVGL initialization sequence — not in user code. Reproducibility: 100% reproducible on cold boot Device always self-recovers on automatic reboot Completely independent of user code — happens before any user application starts This is a separate bug from issue #94 (sta.scan() at MEPC: 0x4ff13582). Both bugs share the same root environment (UIFlow2 v2.4.4 on Tab5) but occur at different stages and involve different subsystems.
  • 261 Topics
    568 Posts
    关于是否支持中文语音和中文界面啊?