-
Notifications
You must be signed in to change notification settings - Fork 963
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
[Bug]: T-Echo won't boot with 2.3.0 #3390
Comments
Maybe it's older than that. These are one of the first ones they shipped. I don't recall that there was an option for a BME280 back then. |
One thing I would check is what version of the bootoader you have. https://meshtastic.org/docs/getting-started/flashing-firmware/nrf52/update-techo-bootloader/ |
I checked that already when I opened issue #3249. The test build of 2.2.25 from that issue worked. Nothing since. |
The linked firmware has the same issue. |
Is there a uf2 file somewhere? I don't have a dev env setup. |
PR#3406 .uf2 for the T-echo here: https://github.com/meshtastic/firmware/actions/runs/8274137437/artifacts/1324540663 but please try this one first: https://github.com/meshtastic/firmware/actions/runs/8279238369/artifacts/1325679915 |
I tried them both. Both are working. |
Both versions linked above still seem to freeze my device. �@�INFO | ??:??:?? 1 //\ E S H T /\ S T / C DEBUG | ??:??:?? 1 Filesystem files: -frezes here- |
@jeremybox did you remove the file names under your first line? it should look like:
could be a different issue. do you have any known working firmware version? or try flashing SoftRF, it runs a POST check on startup. |
I did not edit the output. Additionally, I just tested and had no output at all under the SoftRF firmware. I then reflashed the meshtastic firmware and continue to have the blank filesystem files ouput. If you think I"m experiencing a different issue, I can file a separate ticket. |
Category
Other
Hardware
T-Echo
Firmware Version
2.2.24.e6a2c06 Beta
Description
I have 2 T-Echo devices (v1 boards) that refuse to boot after installing 2.3.0. Multiple boot attempts all freeze at the same place.
Relevant log output
The text was updated successfully, but these errors were encountered: