adam/Meck
1
0 Fork 0
mirror of https://github.com/pelgraine/Meck.git synced 2026-10-30 19:52:01 +01:00
Code Issues 8 Packages Projects Releases Wiki Activity

trouble starting up with SD card installed #4

New Issue
Open
opened 2026-10-04 23:05:39 +02:00 by adam · 10 comments
adam commented 2026-10-04 23:05:39 +02:00
Owner
Copy link
Copy source

I might have a flaky sd card: it's a cheap Amazon Basics 64GB (which I was hoping to be able to use for an un-demanding application like this, because I don't completely trust it, although I was able to boot a Raspberry Pi with it a while back). Often after rebooting with the card installed, Meck hangs on the Loading... screen and never gets further. But if I pull out the sd card, boot once, then insert the SD card and reset, it can be ok sometimes. I think the UI should be designed to fail gracefully in this case: show a warning but then keep going without it, and retry later. But maybe the reason why it is unhappy with this card also needs troubleshooting. I'm not sure if it's the card's fault or not.

Why do you say 32GB or bigger? It's not storing that much data.

I might have a flaky sd card: it's a cheap Amazon Basics 64GB (which I was hoping to be able to use for an un-demanding application like this, because I don't completely trust it, although I was able to boot a Raspberry Pi with it a while back). Often after rebooting with the card installed, Meck hangs on the Loading... screen and never gets further. But if I pull out the sd card, boot once, then insert the SD card and reset, it can be ok sometimes. I think the UI should be designed to fail gracefully in this case: show a warning but then keep going without it, and retry later. But maybe the reason why it is unhappy with this card also needs troubleshooting. I'm not sure if it's the card's fault or not. Why do you say 32GB or bigger? It's not storing that much data. <!-- github-sync-id:4285258445 -->
adam commented 2026-10-04 23:05:40 +02:00
Author
Owner
Copy link
Copy source

OK I got a 128GB card working, but that's really ridiculous. Had to order another pile of various SD cards so I can see what smaller-sized one will work.

OK I got a 128GB card working, but that's really ridiculous. Had to order another pile of various SD cards so I can see what smaller-sized one will work. <!-- github-comment-id:4271539956 -->
adam commented 2026-10-04 23:05:41 +02:00
Author
Owner
Copy link
Copy source

Few things I need to know - (1) what device type are you using, (2)what firmware are you using, and did you start with the -merged verstion on first time flash, and (3) how long did you wait for the Loading... screen to resolve. The latter one is an intermitten spiffs failure error that takes betwen 1.5 to 1.75 mins to resolve itself. It's proven a real issue to tackle because it only happens intermittently, and only the first time you flash with a new SD card installed.

It should work with a 16GB SD card. 32GB is recommended for Meck because of the sheer number of features incorporated with the firmware. This is vibecoded entirely free firmware you're testing; what size and type of SD card you use is entirely a matter for you, but 32GB+ Sandisk is recommended as I've found that to be most reliable.

Few things I need to know - (1) what device type are you using, (2)what firmware are you using, and did you start with the -merged verstion on first time flash, and (3) how long did you wait for the Loading... screen to resolve. The latter one is an intermitten spiffs failure error that takes betwen 1.5 to 1.75 mins to resolve itself. It's proven a real issue to tackle because it only happens intermittently, and only the first time you flash with a new SD card installed. It should work with a 16GB SD card. 32GB is recommended for Meck because of the sheer number of features incorporated with the firmware. This is vibecoded entirely free firmware you're testing; what size and type of SD card you use is entirely a matter for you, but 32GB+ Sandisk is recommended as I've found that to be most reliable. <!-- github-comment-id:4275272874 -->
adam commented 2026-10-04 23:05:41 +02:00
Author
Owner
Copy link
Copy source

Just noting Meck v1.7 is now out, which includes an update to the Loading splash screen to let first-time flashers to know the formatting may take 1-2 minutes after first flash.

https://github.com/pelgraine/Meck/releases/tag/v1.7

Just noting Meck v1.7 is now out, which includes an update to the Loading splash screen to let first-time flashers to know the formatting may take 1-2 minutes after first flash. https://github.com/pelgraine/Meck/releases/tag/v1.7 <!-- github-comment-id:4275811033 -->
adam commented 2026-10-04 23:05:42 +02:00
Author
Owner
Copy link
Copy source

also stucked at loading on first boot. hardware is HD-v2-250915 with 4G and used firmware v1.7-Meck-4G-BLE-merged

updated: fixed by first flash with meshcore firmware and then flash this firmware.

Note sure whether the following log is expected or not?

BQ27220: Design Capacity = 1400 mAh (target 1400)
BQ27220: Design Capacity already correct, FCC=3000 mAh
BQ27220: FCC 3000 outside target band [1300..1500], checking Design Energy (target 5180 mWh)
BQ27220: DE correct (5180 mWh) — fixing Qmax + stored FCC
BQ27220:   [0x9106] 3000 -> 1400
BQ27220:   [0x929D] 3000 -> 1400
BQ27220: Qmax + stored FCC updated, exited CFG_UPDATE
BQ27220: Issuing RESET to force FCC recalculation...
BQ27220: FCC after RESET: 1400 mAh (target <= 1400)
_PowerOn : 44999
_Update_Full : 1015001
_Update_Part : 650001
_PowerOn : 45000
_Update_Part : 650001
[  6642][E][esp32-hal-cpu.c:110] addApbChangeCallback(): duplicate func=0x42074544 arg=0x3fc992a0
E (6373) SPIFFS: mount failed, -10025
[  6762][E][SPIFFS.cpp:89] begin(): Mounting SPIFFS failed! Error: -1
SPIFFS mount failed - formatting (this may take 1-2 minutes)...
_PowerOn : 44000
_Update_Part : 650001
E (7196) SPIFFS: mount failed, -10025
also stucked at loading on first boot. hardware is HD-v2-250915 with 4G and used firmware v1.7-Meck-4G-BLE-merged > updated: fixed by first flash with meshcore firmware and then flash this firmware. Note sure whether the following log is expected or not? ``` BQ27220: Design Capacity = 1400 mAh (target 1400) BQ27220: Design Capacity already correct, FCC=3000 mAh BQ27220: FCC 3000 outside target band [1300..1500], checking Design Energy (target 5180 mWh) BQ27220: DE correct (5180 mWh) — fixing Qmax + stored FCC BQ27220: [0x9106] 3000 -> 1400 BQ27220: [0x929D] 3000 -> 1400 BQ27220: Qmax + stored FCC updated, exited CFG_UPDATE BQ27220: Issuing RESET to force FCC recalculation... BQ27220: FCC after RESET: 1400 mAh (target <= 1400) _PowerOn : 44999 _Update_Full : 1015001 _Update_Part : 650001 _PowerOn : 45000 _Update_Part : 650001 [ 6642][E][esp32-hal-cpu.c:110] addApbChangeCallback(): duplicate func=0x42074544 arg=0x3fc992a0 E (6373) SPIFFS: mount failed, -10025 [ 6762][E][SPIFFS.cpp:89] begin(): Mounting SPIFFS failed! Error: -1 SPIFFS mount failed - formatting (this may take 1-2 minutes)... _PowerOn : 44000 _Update_Part : 650001 E (7196) SPIFFS: mount failed, -10025 ``` <!-- github-comment-id:4318398680 -->
adam commented 2026-10-04 23:05:43 +02:00
Author
Owner
Copy link
Copy source

also stucked at loading on first boot. hardware is HD-v2-250915 with 4G and used firmware v1.7-Meck-4G-BLE-merged

updated: fixed by first flash with meshcore firmware and then flash this firmware.

Note sure whether the following log is expected or not?

BQ27220: Design Capacity = 1400 mAh (target 1400)
BQ27220: Design Capacity already correct, FCC=3000 mAh
BQ27220: FCC 3000 outside target band [1300..1500], checking Design Energy (target 5180 mWh)
BQ27220: DE correct (5180 mWh) — fixing Qmax + stored FCC
BQ27220:   [0x9106] 3000 -> 1400
BQ27220:   [0x929D] 3000 -> 1400
BQ27220: Qmax + stored FCC updated, exited CFG_UPDATE
BQ27220: Issuing RESET to force FCC recalculation...
BQ27220: FCC after RESET: 1400 mAh (target <= 1400)
_PowerOn : 44999
_Update_Full : 1015001
_Update_Part : 650001
_PowerOn : 45000
_Update_Part : 650001
[  6642][E][esp32-hal-cpu.c:110] addApbChangeCallback(): duplicate func=0x42074544 arg=0x3fc992a0
E (6373) SPIFFS: mount failed, -10025
[  6762][E][SPIFFS.cpp:89] begin(): Mounting SPIFFS failed! Error: -1
SPIFFS mount failed - formatting (this may take 1-2 minutes)...
_PowerOn : 44000
_Update_Part : 650001
E (7196) SPIFFS: mount failed, -10025

Logs are always appreciated as they help with debugging, so thank you for including that! That can happen when you're loading Meck without an SD card in, or without one that's been pre-formatted to FAT32. Can I double check you've flashed it with a formatted SD card, and also whether or not you're using the firmware with the M5 Launcher?

> also stucked at loading on first boot. hardware is HD-v2-250915 with 4G and used firmware v1.7-Meck-4G-BLE-merged > > > updated: fixed by first flash with meshcore firmware and then flash this firmware. > > Note sure whether the following log is expected or not? > > ``` > BQ27220: Design Capacity = 1400 mAh (target 1400) > BQ27220: Design Capacity already correct, FCC=3000 mAh > BQ27220: FCC 3000 outside target band [1300..1500], checking Design Energy (target 5180 mWh) > BQ27220: DE correct (5180 mWh) — fixing Qmax + stored FCC > BQ27220: [0x9106] 3000 -> 1400 > BQ27220: [0x929D] 3000 -> 1400 > BQ27220: Qmax + stored FCC updated, exited CFG_UPDATE > BQ27220: Issuing RESET to force FCC recalculation... > BQ27220: FCC after RESET: 1400 mAh (target <= 1400) > _PowerOn : 44999 > _Update_Full : 1015001 > _Update_Part : 650001 > _PowerOn : 45000 > _Update_Part : 650001 > [ 6642][E][esp32-hal-cpu.c:110] addApbChangeCallback(): duplicate func=0x42074544 arg=0x3fc992a0 > E (6373) SPIFFS: mount failed, -10025 > [ 6762][E][SPIFFS.cpp:89] begin(): Mounting SPIFFS failed! Error: -1 > SPIFFS mount failed - formatting (this may take 1-2 minutes)... > _PowerOn : 44000 > _Update_Part : 650001 > E (7196) SPIFFS: mount failed, -10025 > ``` Logs are always appreciated as they help with debugging, so thank you for including that! That can happen when you're loading Meck without an SD card in, or without one that's been pre-formatted to FAT32. Can I double check you've flashed it with a formatted SD card, and also whether or not you're using the firmware with the M5 Launcher? <!-- github-comment-id:4318673300 -->
adam commented 2026-10-04 23:05:44 +02:00
Author
Owner
Copy link
Copy source

also stucked at loading on first boot. hardware is HD-v2-250915 with 4G and used firmware v1.7-Meck-4G-BLE-merged

updated: fixed by first flash with meshcore firmware and then flash this firmware.

Note sure whether the following log is expected or not?

BQ27220: Design Capacity = 1400 mAh (target 1400)
BQ27220: Design Capacity already correct, FCC=3000 mAh
BQ27220: FCC 3000 outside target band [1300..1500], checking Design Energy (target 5180 mWh)
BQ27220: DE correct (5180 mWh) — fixing Qmax + stored FCC
BQ27220:   [0x9106] 3000 -> 1400
BQ27220:   [0x929D] 3000 -> 1400
BQ27220: Qmax + stored FCC updated, exited CFG_UPDATE
BQ27220: Issuing RESET to force FCC recalculation...
BQ27220: FCC after RESET: 1400 mAh (target <= 1400)
_PowerOn : 44999
_Update_Full : 1015001
_Update_Part : 650001
_PowerOn : 45000
_Update_Part : 650001
[  6642][E][esp32-hal-cpu.c:110] addApbChangeCallback(): duplicate func=0x42074544 arg=0x3fc992a0
E (6373) SPIFFS: mount failed, -10025
[  6762][E][SPIFFS.cpp:89] begin(): Mounting SPIFFS failed! Error: -1
SPIFFS mount failed - formatting (this may take 1-2 minutes)...
_PowerOn : 44000
_Update_Part : 650001
E (7196) SPIFFS: mount failed, -10025

Logs are always appreciated as they help with debugging, so thank you for including that! That can happen when you're loading Meck without an SD card in, or without one that's been pre-formatted to FAT32. Can I double check you've flashed it with a formatted SD card, and also whether or not you're using the firmware with the M5 Launcher?

“you've flashed it with a formatted SD card”: yes, sd card is already fat32. sd card is installed when booting meck.
"whether or not you're using the firmware with the M5 Launcher": I didn't use m5 launcher.

Notes: Shift+Backspace, saving...
_PowerOn : 45000
_Update_Part : 651001
[716663][E][vfs_api.cpp:332] VFSFileImpl(): fopen(/sd/notes/note_20240515_1104.txt) failed
Notes: Failed to save note_20240515_1104.txt
Notes: Created /notes
[716677][E][vfs_api.cpp:105] open(): /sd/notes does not exist, no permits for creation
> > also stucked at loading on first boot. hardware is HD-v2-250915 with 4G and used firmware v1.7-Meck-4G-BLE-merged > > > updated: fixed by first flash with meshcore firmware and then flash this firmware. > > > > > > Note sure whether the following log is expected or not? > > ``` > > BQ27220: Design Capacity = 1400 mAh (target 1400) > > BQ27220: Design Capacity already correct, FCC=3000 mAh > > BQ27220: FCC 3000 outside target band [1300..1500], checking Design Energy (target 5180 mWh) > > BQ27220: DE correct (5180 mWh) — fixing Qmax + stored FCC > > BQ27220: [0x9106] 3000 -> 1400 > > BQ27220: [0x929D] 3000 -> 1400 > > BQ27220: Qmax + stored FCC updated, exited CFG_UPDATE > > BQ27220: Issuing RESET to force FCC recalculation... > > BQ27220: FCC after RESET: 1400 mAh (target <= 1400) > > _PowerOn : 44999 > > _Update_Full : 1015001 > > _Update_Part : 650001 > > _PowerOn : 45000 > > _Update_Part : 650001 > > [ 6642][E][esp32-hal-cpu.c:110] addApbChangeCallback(): duplicate func=0x42074544 arg=0x3fc992a0 > > E (6373) SPIFFS: mount failed, -10025 > > [ 6762][E][SPIFFS.cpp:89] begin(): Mounting SPIFFS failed! Error: -1 > > SPIFFS mount failed - formatting (this may take 1-2 minutes)... > > _PowerOn : 44000 > > _Update_Part : 650001 > > E (7196) SPIFFS: mount failed, -10025 > > ``` > > Logs are always appreciated as they help with debugging, so thank you for including that! That can happen when you're loading Meck without an SD card in, or without one that's been pre-formatted to FAT32. Can I double check you've flashed it with a formatted SD card, and also whether or not you're using the firmware with the M5 Launcher? “you've flashed it with a formatted SD card”: yes, sd card is already fat32. sd card is installed when booting meck. "whether or not you're using the firmware with the M5 Launcher": I didn't use m5 launcher. ``` Notes: Shift+Backspace, saving... _PowerOn : 45000 _Update_Part : 651001 [716663][E][vfs_api.cpp:332] VFSFileImpl(): fopen(/sd/notes/note_20240515_1104.txt) failed Notes: Failed to save note_20240515_1104.txt Notes: Created /notes [716677][E][vfs_api.cpp:105] open(): /sd/notes does not exist, no permits for creation ``` <!-- github-comment-id:4323421494 -->
adam commented 2026-10-04 23:05:44 +02:00
Author
Owner
Copy link
Copy source

Thanks for that. Looks like I need to dig further into these SPIFFs errors with some fresh SD cards of different brand types. Will add a more robust format fallback for mount and autoformat failures in V1.8.

Thanks for that. Looks like I need to dig further into these SPIFFs errors with some fresh SD cards of different brand types. Will add a more robust format fallback for mount and autoformat failures in V1.8. <!-- github-comment-id:4323524205 -->
adam commented 2026-10-04 23:05:45 +02:00
Author
Owner
Copy link
Copy source

Check out https://github.com/pelgraine/Meck/releases/tag/v1.8 and let me know if you have any further feedback.

Check out https://github.com/pelgraine/Meck/releases/tag/v1.8 and let me know if you have any further feedback. <!-- github-comment-id:4366063589 -->
adam commented 2026-10-04 23:05:46 +02:00
Author
Owner
Copy link
Copy source

didn't work, stuck at loading.

I tried meshcore non-sd firmware (https://meshcore.io/flasher), it works fine.

didn't work, stuck at loading. I tried meshcore non-sd firmware (https://meshcore.io/flasher), it works fine. <!-- github-comment-id:4367520464 -->
adam commented 2026-10-04 23:05:46 +02:00
Author
Owner
Copy link
Copy source

Glad to hear Ripple non-SD firmware is working for you! Honestly I'd hope everyone uses Ripple first before they try Meck; Scott is a developer who does this sort of thing for a living, I am most definitely not one.

I haven't been able to replicate the same issue on any of my three T-Deck Pro devices, apologies. I might have to look into a Meck lite version that is designed to work without a SD card for these situations.

Glad to hear Ripple non-SD firmware is working for you! Honestly I'd hope everyone uses Ripple first before they try Meck; Scott is a developer who does this sort of thing for a living, I am most definitely not one. I haven't been able to replicate the same issue on any of my three T-Deck Pro devices, apologies. I might have to look into a Meck lite version that is designed to work without a SD card for these situations. <!-- github-comment-id:4376011171 -->
Sign in to join this conversation.
No Branch/Tag Specified
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
adam (Adam Wojcieszonek)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/Meck#4