Open vk2diy opened 1 month ago
On further investigation it seems it's every time I try to reconfigure the device using the app that it crashes.
On further investigation, no it's still crashing. Maybe I'll see if it's the app. If I turn off bluetooth on the phone the app can't place a request so it might go stable. Hang on ...
Nope just seems to be crashing. I think the device is just stuck in an infinite reboot loop. It's confusing because the screen goes off and on but there's never any data displayed just the logo or black, and a momentary screen update looks partially corrupted before reboot. Flashing behind the screen continues as normal.
After awhile there is a long red flash followed by a period of no LED, followed by a reboot.
If I press the left button the screen doesn't wake and the flashing continues. If I press the middle button the screen wakes for awhile then goes back to sleep. If I press the right button it resets.
I can't use the android interface to do anything because it's not up long enough.
I've already tried resetting with the web flasher.
Please help me unbrick, otherwise I will have to send the hardware back.
No help after 1 week, I am returning the hardware. Your bug remains.
You can probably still reflash it with the CLI: https://meshtastic.org/docs/getting-started/flashing-firmware/esp32/cli-script/ You'll likely need to try to connect to it multiple times, because it only has a small amount of time to react before it reboots.
Not sure why it's crashing, this is the decoded stack trace:
0: 0x400d36b6: _ZN11MeshService11sendToPhoneEP22_meshtastic_MeshPacket$constprop$918 at ??:? 0: 0x40119fef: RoutingModule::handleReceivedProtobuf(_meshtastic_MeshPacket const&, _meshtastic_Routing) at :? 0: 0x4011778d: ProtobufModule<_meshtastic_Routing>::handleReceived(_meshtastic_MeshPacket const&) at :? 0: 0x4012ae65: Router::handleReceived(_meshtastic_MeshPacket, RxSource) at :? 0: 0x4012b0fd: Router::runOnce() at ??:? 0: 0x4013b4f6: concurrency::OSThread::run() at ??:? 0: 0x401324f9: loop() at ??:? 0: 0x400e2df5: loopTask(void*) at :?
Thanks but sorry I already returned the hardware.
To be clear the web flasher worked, I was able to reflash, but it didn't resolve the issue. So I doubt the CLI would work unless its results somehow differ.
Whatever was causing the issue (perhaps a stored message for repeating or something) needs to be removed from the memory I think. This is apparently a different process to flashing.
Category
Other
Hardware
T-Beam
Firmware Version
2.4.0.46d7b82
Description
Relevant log output