[Bug]: T-Echo broke by itself -> reboot loop #5536
Replies: 5 comments
-
Try the factory erase uf2 process |
Beta Was this translation helpful? Give feedback.
-
Formatting the filesystem fixed my T-Echo 🎉 I installed meshtastic CLI in Windows Subsystem for Linux (WSL) , but that didn't work on the first try, so I used Arduino IDE instead. Could we adapt the documentation regarding that any serial terminal works, not just "meshtastic --proto"? |
Beta Was this translation helpful? Give feedback.
-
Hi folks. So I have tried two different meshtastic versions now, and with both, the T-Echo breaks after some time. This time there are logs. First I tried 2.5.15. `//\ E S H T /\ S T / C �[0m�[34mDEBUG �[0m| ??:??:?? 1 �[34mFilesystem files: Then I tried 2.5.11, which ran for 2 days now but ended breaking too: `//\ E S H T /\ S T / C �[0m�[34mDEBUG �[0m| ??:??:?? 2 �[34mFilesystem files: In both cases the configuration was default, except setting the region. Does anybody have an idea how to fix this? |
Beta Was this translation helpful? Give feedback.
-
This just happened to me. Do we have any fixes for this problem ? |
Beta Was this translation helpful? Give feedback.
-
I managed to fix this by forcing a call to format(). Since auto format only happens on mount failure and this error seems to be about a corrupted file system that does mount but causes the LFS assert: error. PR to add a call to FSCom.format() at the end of lfs_assert in incoming. #5670 |
Beta Was this translation helpful? Give feedback.
-
Category
Other
Hardware
T-Echo
Firmware Version
2.5.14.f2ee0df
Description
Hi folks.
I have a T-Echo and installed 2.5.14
I added a 6000mAh battery and was looking to see how long it would last, but in the morning I realized that the T-Echo already stopped working in the night. Bluetooth wouldn't connect and the LEDs would flash blue-red-red.
Plugging it in on my PC via USB would just give reconnects every ~2 seconds.
I found a help article here and started following it (Xinyuan-LilyGO/T-Echo#18 (comment))
Burning the bootloader worked and uploading different firmwares works, but the device is still stuck in the reboot loop.
I yet have to successfully delete the filesystem.
Serial Monitor ends an error, assert block lfs, so I suspect a corrupted filesystem might be the ultimate reason.
I worked on this kinda in between other things today, so I am sorry this report is not as detailed as it could be and that I didn't grab the original logs.
I hope this still might come in useful to somebody. If I manage to fix the device, I will document it here.
Relevant log output
No response
Beta Was this translation helpful? Give feedback.
All reactions