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

[Bug]: T-Echo won't boot with 2.3.0 #3390

Closed
pista01 opened this issue Mar 12, 2024 · 12 comments · Fixed by #3375
Closed

[Bug]: T-Echo won't boot with 2.3.0 #3390

pista01 opened this issue Mar 12, 2024 · 12 comments · Fixed by #3375
Labels
bug Something isn't working

Comments

@pista01
Copy link

pista01 commented Mar 12, 2024

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

//\ E S H T /\ S T / C

DEBUG | ??:??:?? 0 Filesystem files:
DEBUG | ??:??:?? 0  module.proto (98 Bytes)
DEBUG | ??:??:?? 0  channels.proto (140 Bytes)
DEBUG | ??:??:?? 0  config.proto (89 Bytes)
DEBUG | ??:??:?? 0  db.proto (979 Bytes)
DEBUG | ??:??:?? 0 Using analog input 4 for battery level
INFO  | ??:??:?? 0 Scanning for i2c devices...
DEBUG | ??:??:?? 0 Scanning fo
@pista01 pista01 added the bug Something isn't working label Mar 12, 2024
@pista01 pista01 changed the title [Bug]: T-Echo wo't boot with 2.3.0 [Bug]: T-Echo won't boot with 2.3.0 Mar 12, 2024
@Mictronics
Copy link
Contributor

Mictronics commented Mar 12, 2024

Can't confirm. Tried 2.3.0.5f47ca1 Alpha and also the latest master ee685b4. Both work on one of my T-Echos with board marked v1.0 2021-06-28. The board is equipped with BME280.

Seems PR #3375 related.

@pista01
Copy link
Author

pista01 commented Mar 12, 2024

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.

@rcarteraz
Copy link
Member

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/

@pista01
Copy link
Author

pista01 commented Mar 12, 2024

I checked that already when I opened issue #3249. The test build of 2.2.25 from that issue worked. Nothing since.

@thebentern
Copy link
Contributor

@pista01 can you try this one?
#3406

@jeremybox
Copy link

The linked firmware has the same issue.

@pista01
Copy link
Author

pista01 commented Mar 14, 2024

Is there a uf2 file somewhere? I don't have a dev env setup.

@andrekir
Copy link
Member

@pista01
Copy link
Author

pista01 commented Mar 14, 2024

I tried them both. Both are working.

@andrekir andrekir linked a pull request Mar 14, 2024 that will close this issue
@jeremybox
Copy link

jeremybox commented Mar 14, 2024

Both versions linked above still seem to freeze my device.

�@�INFO | ??:??:?? 1

//\ E S H T /\ S T / C

DEBUG | ??:??:?? 1 Filesystem files:
DEBUG | ??:??:?? 1 Using analog input 4 for battery level
INFO | ??:??:?? 1 Scanning for i2c devices...
DEBUG | ??:??:?? 1 Scanning for i2c devices on port 1

-frezes here-

@andrekir
Copy link
Member

@jeremybox did you remove the file names under your first line? it should look like:

DEBUG | ??:??:?? 2 Filesystem files:
DEBUG | ??:??:?? 2  db.proto (331 Bytes)
DEBUG | ??:??:?? 2  config.proto (89 Bytes)
DEBUG | ??:??:?? 2  module.proto (113 Bytes)
DEBUG | ??:??:?? 2  channels.proto (97 Bytes)
(...)

could be a different issue. do you have any known working firmware version? or try flashing SoftRF, it runs a POST check on startup.

@jeremybox
Copy link

jeremybox commented Mar 15, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants