T-Echo Meshtastic Corruption (lemmy.sdf.org)

submitted 3 weeks ago by wesker@lemmy.sdf.org to c/meshtastic@mander.xyz

2 comments fedilink hide all child comments

I recently bought 2 T-Echo Meshtastic devices directly from Lilygo.

Both devices on default settings seem to repeatedly corrupt their flashed firmware. Reflashing them will undo the brick for a couple days, and then it happens all over again.

I have yet to discover what exactly is causing this issue, but suspect it's beyond my expertise. For it to be happening on default settings, and simply by sitting on a desktop, seems pretty outrageous.

you are viewing a single comment's thread
view the rest of the comments

[-] mp3@lemmy.ca 2 points 3 weeks ago* (last edited 3 weeks ago)

It's possible that the lack of a MMU in the nRF52840 can cause memory corruption if the code writes somewhere it shouldn't because of a programming mistake. I remember that my previous "smartwatch" (the BangleJS 2) which use the exact same chip had some memory corruption issues when it first came out that were likely caused by some bugs in the code.

this post was submitted on 31 Aug 2024

11 points (92.3% liked)

Meshtastic

272 readers

1 users here now

A community to discuss Meshtastic (https://meshtastic.org/docs/introduction)

founded 9 months ago

MODERATORS

Sal@mander.xyz