@cricri There is FDISK utility built-in. You can list all the partitions and delete those are not used anymore. System partitions are read-only, so you will not delete anything extra. Also you can create new partition at any time. For example, the Game Station requires spare partition for cache. so just add it in FDISK with a few clicks. @dzepetko said in M5Apps - multiple apps installer: How can i install meshtastic and 4exampe winamp? - i have error not enough space.. ;/ By default the SDK (ESP-IDF) makes firmware bundle with default partitions, But the thing is: application could not use it at all or use one of them. So we can cook a binary with only partitions that really need by the app. This can save much space.

M5Paper quirks can definitely slow you down. Curious what steps you’ve tried so far and if any improvements helped.

Connectivity and login problems tend to pop up with firmware tools. Curious if anyone found a reliable workaround.

@RPI25 said in Is it possible to use the M5GO Bottom 3 with the Tab 5: M5GO Bottom 3 Hi RPI25 (and felmue) I am guessing (as you didn't say) that you want to use the Battery function of the M5GO to power the TAB5? Or is there another reason you wish to add the M5GO to the TAB5? With that said on the M5Stack Store it very specifically states that each "version" of the M5GOs are designed to work with a specific Core ONLY. I included a graphic as well: [image: 1769979322100-m5go.png] I did compare pinouts that were provided by Felix (thanks!) and again I am only guessing is that you are after the battery function? With that said I would simply purchase the battery (which I did do with my TAB5). I am curious about your project? Thanks-Brian

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.

Hello @KAYDE1 maybe checkout this example here? To make it work I had to adapt the GPIO used for the LEDs: // buscfg.pin_data = 26; buscfg.pin_data = 25; I also added a delay(1000); at the end of the loop(). Thanks Felix

Hello @infraready indeed on the pictures the back of both SE and Lite are marked SE - strange. Anyways, have you tied to burn and run the M5CoreS3 demo firmware? This should give you a good indication about whether the camera works or not. Please note: I do not have an M5CoreS3 Lite to test this myself. Thanks Felix

Like @felmue I also did a bit more testing of the low voltage flags, then enabled the charge circuit (and setting the charge voltage via bfvsel to unlimited). The clock has held time ever since. I'm curious about how long the capacitor can run the clock when fully charged and I have disabled charging again. But my device spends most of it's time on USB power so the duration is hard to measure; so lets try to estimate it :-) If the frequency out and I2C is disabled (inien = True) the device should typically draw 0.3 µA when on backup battery (table 5 in the datasheet). The capacitor is possibly a ML414H; 0.07 F. Table 3 in the datasheet says that the clock oscillator minimum voltage is 1.1v, and the start voltage is VStandby; 3.3v. So we just need to work out the discharge time. Start with working out the equivalent resistance at 3.3v; R=Voltage/Current = 3.3/0.0000003 = 11000000 = 11 MΩ Now use an online discharge calculator to do the 'heavy lifting'... https://3roam.com/capacitor-discharge-time-calculator/ (I like that site; it shows the maths used) This gives an estimated! time of 845932 seconds; which is ~235 hours, almost ten days. Which seems reasonable for a capacitor backup.

@cleatus007 using grove cable and connect to port on side of cardputer

I'm trying to upload a new firmware on the unit roller connecting a ST_Link v2 to the SPI connector with STM32CubeProgrammer. Roller SPI ---------------- ST_LinkV2 V --------------------- 3.3 G -------------------- GND C ------------------ SWCLOCK D ------------------ SWDIO O ------------------- NC when the firmware si uploaded the unit roller works (display right boot image and information, led is on, button and encoder works and menu works too), but if I disconnect the SPI cable and I power the unit from grove or dc in 6/16v, the unit doesn't work(black display, led off, etc). this is the .hex firmware used. and this is the cube log: 22:11:59 : MASS ERASE ... 22:11:59 : Mass erase successfully achieved 22:11:59 : UPLOADING ... 22:11:59 : Size : 1024 Bytes 22:11:59 : Address : 0x8000000 22:11:59 : Read progress: 22:11:59 : Data read successfully 22:11:59 : Time elapsed during the read operation is: 00:00:00.019 22:12:36 : Opening and parsing file: ROLLERCAN.hex 22:12:36 : Memory Programming ... 22:12:36 : File : ROLLERCAN.hex 22:12:36 : Size : 94.38 KB 22:12:36 : Address : 0x08002000 22:12:36 : Erasing memory corresponding to segment 0: 22:12:36 : Erasing internal memory sectors [4 51] 22:12:37 : Download in Progress: 22:12:39 : File download complete 22:12:39 : Time elapsed during download operation: 00:00:02.735 22:12:39 : Verifying... 22:12:39 : Read progress: 22:12:39 : Time elapsed during verifying operation: 00:00:00.645 22:12:39 : Download verified successfully 22:12:39 : Memory [0x08000000 : 0x08020000] - Checksum : 0x011ED0C0 22:12:39 : RUNNING Program ... 22:12:39 : Address: : 0x08002000 22:12:39 : Application is running, Please Hold on... 22:12:39 : Start operation achieved successfully this is the log of OB: { "deviceId" : 1128, "bitNameToValue" : { "RDP" : 170, "BOR_LEV" : 0, "nRST_STOP" : 1, "nRST_STDBY" : 1, "nRST_SHDW" : 1, "IWDG_SW" : 1, "IWDG_STOP" : 1, "IWDG_STDBY" : 1, "WWDG_SW" : 1, "nBOOT1" : 1, "SRAM_PE" : 1, "CCMSRAM_RST" : 1, "nSWBOOT0" : 1, "nBOOT0" : 1, "NRST_MODE" : 3, "IRHEN" : 1, "PCROP1_STRT" : 16383, "PCROP1_END" : 0, "PCROP_RDP" : 0, "WRP1A_STRT" : 63, "WRP1A_END" : 0, "WRP1B_STRT" : 63, "WRP1B_END" : 0, "SEC_SIZE1" : 0, "BOOT_LOCK" : 0 } } If I power the unit from grove or DC in, I have 3.3v on SPI (V,G). I tried to merge and burn a bootloader.hex too but no joy. after uploading the firmware if I connect the grove cable of an atom lite running a i2c scanner code, I can see 0x64 on serial monitor. I can also disconnect the SPI cable and the roller still works until a power cycle. ideas?? tnks a lot!!