[Bug]: T-Echo won't boot with 2.3.0 about firmware HOT 12 CLOSED

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.

from firmware.

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.

from firmware.

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/

from firmware.

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

from firmware.

@pista01 can you try this one?
#3406

from firmware.

The linked firmware has the same issue.

from firmware.

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

from firmware.

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

from firmware.

I tried them both. Both are working.

from firmware.

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-

from firmware.

@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.

from firmware.

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.

from firmware.