T-Beams seemingly in a bootloop on USB

Support
1

I’m sorry that I don’t know how to give you better information, but I’ve noticed two separate units, on two separate occasions, seemingly in a boot loop, I’ve captured it twice on video.

The first time was on 1.1.32 but I’ve noticed it again today on version 1.1.42…

It seems to happen when it’s plugged into the computer via USB…

Let me know how I can be of more help with this.

[EDIT: I removed the Videos]

1 Like
2

Ooh if it happens and you can run a serial terminal at 921600 it will probably have the info we need to capture.

3

I tried yesterday to reproduce the situation, But it would not bootloop anymore. Then today, a T-Beam was dead so I plugged it into my computer as the closest USB charger and it started looping, but by the time I got a terminal logger going, it had stopped.

So I’m now assuming that it was a low battery situation causing the reboot?

1 Like
4

I’ve seen that in a 3D printed case, where the case was a bit tight, and the reset button was getting triggered repeatedly. I also think I have seen that in the past with low battery.

1 Like
5

hmm - low battery shouldn’t cause a reboot. If you happen to encounter it when you have access to a serial log hopefully it is printing a debug message with a hint on the cause.

6

New guy here… Haven’t done forums in a long time, so be gentle.
I am currently experiencing a boot loop when using USB.
I ordered my boards from the recommended link at meshtastic.org (https://www.aliexpress.com/item/4001178678568.html). After doing the soldering and turning it on, I noticed that the display control is constantly increasing. It is like the button is being held down. My board is NOT in a case, so there is no physical object pressing it.
Anyways, after researching, I discovered that I need to flash the latest firmware on the board to fix the brightness issue. I am currently running 1.0.0… In order to achieve this, I downloaded the ESP Home Flasher for Windows 64.
After plugging my board via USB to my windows PC, it is constantly rebooting… If I unplug, it is fine.
I capture the logs. Please provide any clues on where I can go next.

Using 'COM6' as serial port.
Showing logs:
[23:18:18]ets Jun  8 2016 00:22:57
[23:18:18]
[23:18:18]rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
[23:18:18]configsip: 0, SPIWP:0xee
[23:18:18]clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
[23:18:18]mode:DIO, clock div:2
[23:18:18]load:0x3fff0018,len:4
[23:18:18]load:0x3fff001c,len:1044
[23:18:18]load:0x40078000,len:8896
[23:18:18]load:0x40080400,len:5828
[23:18:18]entry 0x400806ac
[23:18:19][D][esp32-hal-psram.c:47] psramInit(): PSRAM enabled
[23:18:22]!_#j%{ji${_h4$bjB2LB19FjONB{s;^Bv(%s(	̔sgÝci%}!G7ERަˇkCBets Jun  8 2016 00:22:57
[23:18:22]
[23:18:22]rst:0x5 (DEEPSLEEP_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
[23:18:22]configsip: 0, SPIWP:0xee
[23:18:22]clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
[23:18:22]mode:DIO, clock div:2
[23:18:22]load:0x3fff0018,len:4
[23:18:22]load:0x3fff001c,len:1044
[23:18:22]load:0x40078000,len:8896
[23:18:22]load:0x40080400,len:5828
[23:18:22]entry 0x400806ac
[23:18:23][D][esp32-hal-psram.c:47] psramInit(): PSRAM enabled
[23:18:26]ͩ_`]%{li${^i4%bɌC2FalFjwEÃ8##E_#gj)浍!gCuMcsCh}GJC[23:18:26]
[23:18:26]rst:0x5 (DEEPSLEEP_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
[23:18:26]configsip: 0, SPIWP:0xee
[23:18:26]clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
[23:18:26]mode:DIO, clock div:2
[23:18:26]load:0x3fff0018,len:4
[23:18:26]load:0x3fff001c,len:1044
[23:18:26]load:0x40078000,len:8896
[23:18:26]load:0x40080400,len:5828
[23:18:26]entry 0x400806ac
[23:18:27][D][esp32-hal-psram.c:47] psramInit(): PSRAM enabled
[23:18:30]kc#_#k	{]l${^h4$B2MB1硌(NNB{;(#wfk?k)|1g[23:18:30]
[23:18:30]rst:0x5 (DEEPSLEEP_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
[23:18:30]configsip: 0, SPIWP:0xee
[23:18:30]clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
[23:18:30]mode:DIO, clock div:2
[23:18:30]load:0x3fff0018,len:4
[23:18:30]load:0x3fff001c,len:1044
[23:18:30]load:0x40078000,len:8896
[23:18:30]load:0x40080400,len:5828
[23:18:30]entry 0x400806ac
[23:18:31][D][esp32-hal-psram.c:47] psramInit(): PSRAM enabled
[23:18:34]_#j^{^i${^h4$cq!BbNdCO;KO$NC{s;#/c!!Ɛ!og%c"%h}!FJJ˯Vg=ƽ(%%ets Jun  8 2016 00:22:57
[23:18:34]
[23:18:34]rst:0x5 (DEEPSLEEP_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
[23:18:34]configsip: 0, SPIWP:0xee
[23:18:34]clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
[23:18:34]mode:DIO, clock div:2
[23:18:34]load:0x3fff0018,len:4
[23:18:34]load:0x3fff001c,len:1044
[23:18:34]load:0x40078000,len:8896
[23:18:34]load:0x40080400,len:5828
[23:18:34]entry 0x400806ac
[23:18:35]
Serial port closed!

Thank yall for the help and I look forward to figuring this out.

7

Well… Thanks for the Rubber duck experience… Turns out I am a dummy.

I realized that I needed to open the meshtastic app and update my board via the bluetooth option. This allowed me to get on version 1.1.48… Still had the constant display increasing issue… But now i could use USB and update my firmware.
Everything is fixed now and I will leave my posts here for another poor fool who has my experience.

Thank you all again!

2 Likes