@robski while waiting i bought a new display in case that is the problem.

For future reference to people who search for M5 burner shows nothing... Go into your app data folder in C:/Users/appdata/roaming Delete the M5 stack folder Also delete m5 burner and its associated files from where you keep it/run it. Re-extract the files to the place you keep your m5 burner program and run it, log-in again.

Hi guys I looked at some of the comments - they are all dated from last year. I did not see anything recent. That makes me believe that the commenting feature has been turned off. Thanks Felix

To anyone trying something similar in the future MODULE_4IN8OUT module; MFRC522_I2C mfrc522(0x28, -1, &Wire); void setup() { M5.begin(true, true, true, true); Serial.begin(115200); delay(500); Serial.println("Starting setup..."); M5.Lcd.println("Init..."); // POWER MANAGEMENT dla Port A (RFID) M5.Axp.SetBusPowerMode(0); M5.Axp.SetLDOEnable(2, true); delay(200); // --- I2C BUSES --- Wire.begin(32, 33, 100000); Wire1.begin(21, 22, 100000); delay(100); M5.Lcd.println("Init 4IN8OUT..."); // Start module 4IN8OUT if (!module.begin(&Wire1, 21, 22, MODULE_4IN8OUT_ADDR)) { M5.Lcd.setTextColor(RED); M5.Lcd.println("4IN8OUT INIT FAIL"); Serial.println("4IN8OUT INIT FAIL"); while (1) delay(1000); } M5.Lcd.setTextColor(GREEN); M5.Lcd.println("4IN8OUT OK!"); Serial.println("4IN8OUT OK!"); M5.Lcd.setTextColor(WHITE); // Init RFID mfrc522.PCD_Init(); M5.Lcd.println("RFID OK!"); Serial.println("RFID OK!");

@TimmyProgamsStuff I'm glad about that. Have a lot of fun

Serial and server connection issues can be tricky — been there! Sometimes it’s just a port config or baud mismatch. Hope you find the root cause soon!

@seahope Interesting post! Leveraging HF models like Realistic Vision with the AX8850 module sounds like a solid step toward faster, more efficient on-device AI workflows.

@DocDatenschutz I did some reading and it seems that the Cardputer Adv handles the keyboard differently then on the Cardputer, meaning older firmware is unable to sense keyboard input. As far as I am aware, there is no current fix for this issue besides getting new firmware made for the Adv, though it seems like they are currently trying to fix the issue.

Hi! Have you been able to solve the problem? If so, please tell me how. I am using the ESP32_BLE_KEYBOARD library, and when I connect my PC/phone via Bluetooth (BLE) to my Cardputer on STAMPS3A, it causes the Cardputer to reboot

@richardd672 a mi me sale JTAG/serial debug unit no piuerto com dicen que es probelma de firmware

Bumping this topic, it's months since @AgreeDK asked it and, as far as I know, there's no way to use the Camera in Tab5 with Arduino code

I finally managed to get an application working with graphics and touch on the Tab5. My solution: Removed any reference to managed components in the idf_component.yml files. Clone the M5Unified and M5GFX repositories and put them in the components directory. Added references to CMakeLists.txt for the added components. Application now builds and I have tested the display with the BarGraph anf the TouchTest applications. Hope this helps anyone experiencing the same issue. Regards, Mark

@BobPossible same error, any solutions?

Ok, it worked finally. At least, I needed to use module_llm.melotts instead of module_llm.tts. The model specification in tts_config doesn't matter for my case. It picks melotts-en-default somehow automatically even though the default value is melotts_zh-cn. The module is very unstable when the controller is powered on. It requires several clicks of the reset button until it finally speaks. (The return value of melotts.inference is -97 when it's successful.)

same issue happened Windows 11 Home 24H2 No updates pending Ryzen 7 9700X 32 GB Ram

@simondid have you even tried to look it up yourself? Google's first hit is literally this thread from April, including a full ESPHome config. ESPHome also has a draft PR for including EPDiy as a generic display platform, and EPDiy itself has a PaperS3 pull request, which will allow the BMI270 component from the above thread to work (currently EPDiy tries to import some legacy code that breaks I2C, as patrick3399 used a custom fork of EPDiy that isn't exactly up to date).