Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Heltec T114 V2 corrupted filesystem after several weeks. #130

Open
edegraaff opened this issue Jan 5, 2025 · 6 comments
Open

Heltec T114 V2 corrupted filesystem after several weeks. #130

edegraaff opened this issue Jan 5, 2025 · 6 comments

Comments

@edegraaff
Copy link

Hi, i have a Heltec t144 running as test router and the system had over the last months twice a corrupted filesystem. After reflashing it works again, sometimes i need to whipe the whole device before it accepts the new meshtastic image. I have no clue it is the mesthastic code causing this issue or the device itselves. The Tbeam, same version firmware of mesthastic, is stable like a rock.

Logging attached, i will reflash with the latest beta and see what happens.

Regards
eelco
meshtastic-log-2025-01-05T12-52-18.040Z.log

@b8b8
Copy link

b8b8 commented Jan 5, 2025

This may be more appropriate for the "firmware" section. It also seems to be more prevalent on all NRF devices. I have seen similar issues on the T1000E. What firmware version are you running?

@edegraaff
Copy link
Author

firmware-heltec-mesh-node-t114-2.5.14. was the one that was broken. I now was able to uploaded the official 2.4.2.7d00e1ce from the heltec site. Fall back to older releases that where on the download site of Heltec, i hope this is more stable. I could move the discussion to the firmware location...

@b8b8
Copy link

b8b8 commented Jan 5, 2025

Id suggest moving to a 2.5+ version. I have been running 2.5.18 on my T114 and has been working ok so far.

Anything previous to 2.5, is missing quite a few new features and is overall more detrimental to the mesh, as traffic was handled differently on those versions and was not optimized.

@edegraaff
Copy link
Author

Id suggest moving to a 2.5+ version. I have been running 2.5.18 on my T114 and has been working ok so far.

Anything previous to 2.5, is missing quite a few new features and is overall more detrimental to the mesh, as traffic was handled differently on those versions and was not optimized.

Ok, i will try to reflash, earlyer today the code was revoked and i was not able to download the latest version. Do you also run 24x7 for several weeks? The issue occurs after 4 to 8 weeks 24x7

@b8b8
Copy link

b8b8 commented Jan 6, 2025

For the one with this issue yes it was running for months, but it was a rak, not the T114. My T114s are handhelds that are not on all the time. I really think it is a general NRF issue though, not specific to the T114. 2.5.18 has been running well so far.

I see the code is still in the flasher, not sure what you mean by revoked.
Dont get your firmware from the heltec site. Get it from the official flasher, either latest stable or alpha release.
https://flasher.meshtastic.org/
https://github.com/meshtastic/firmware/releases
image

@edegraaff
Copy link
Author

When i entered the Meshtastic site yesterday and i wanted to download, the site showed a notice the firmware for the T114 was not availible. A few hours earlyer the firmware was there. Maybe there was a small mallfunction (firmware buildstreet active?) . It works now fine. I will upload the latest beta in the device. I also contacted Heltec, and they seem to have direct line with the dev team. Thanks for helping, and sharing thougths.
Regards Eelco

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants