[Bug]: T-Beam v1.2 running in router mode crashes and enters endless reboot cycle #3066
Comments
|
Here are logs after RST that show a normal boot after clearing the issue for reference. ets Jul 29 2019 12:21:46
rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0030,len:1184
load:0x40078000,len:13192
load:0x40080400,len:3028
entry 0x400805e4
E (865) esp_core_dump_flash: No core dum����ѥѥ���found!
E (865) esp_core_dump_flash: No core dump partition found!
[ 12][D][esp32-hal-cpu.c:244] setCpuFrequencyMhz(): PLL: 480 / 2 = 240 Mhz, APB: 80000000 Hz
[ 464][I][esp32-hal-psram.c:96] psramInit(): PSRAM enabled
��@INFO | ??:??:?? 0
//\ E S H T /\ S T / C
INFO | ??:??:?? 0 Booted, wake cause 0 (boot count 1), reset_reason=reset
DEBUG | ??:??:?? 0 Filesystem files (499712/1048576 Bytes):
DEBUG | ??:??:?? 0 /prefs/channels.proto (53 Bytes)
DEBUG | ??:??:?? 0 /prefs/config.proto (88 Bytes)
DEBUG | ??:??:?? 0 /prefs/db.proto (1493 Bytes)
DEBUG | ??:??:?? 0 /static/.gitkeep (0 Bytes)
DEBUG | ??:??:?? 0 /static/Logo_Black.svg.gz (602 Bytes)
DEBUG | ??:??:?? 0 /static/Logo_White.svg.gz (610 Bytes)
DEBUG | ??:??:?? 0 /static/apple-touch-icon.png.gz (3164 Bytes)
DEBUG | ??:??:?? 0 /static/favicon.ico.gz (2270 Bytes)
DEBUG | ??:??:?? 0 /static/icon.svg.gz (852 Bytes)
DEBUG | ??:??:?? 0 /static/index-H3yz6dTg.js.gz (348 Bytes)
DEBUG | ??:??:?? 0 /static/index-cnVnppgi.css.gz (17208 Bytes)
DEBUG | ??:??:?? 0 /static/index-t3MYXjf0.js.gz (206869 Bytes)
DEBUG | ??:??:?? 0 /static/index.html.gz (545 Bytes)
DEBUG | ??:??:?? 1 /static/maplibre-gl-pS6olApQ.js.gz (208178 Bytes)
DEBUG | ??:??:?? 1 /static/robots.txt.gz (42 Bytes)
DEBUG | ??:??:?? 1 /static/site.webmanifest.gz (197 Bytes)
[ 1062][I][esp32-hal-i2c.c:75] i2cInit(): Initialising I2C Master: sda=21 scl=22 freq=100000
[ 1064][I][XPowersCommon.tpp:248] begin(): SDA:21 SCL:22
[ 1068][W][Wire.cpp:301] begin(): Bus already started in Master Mode.
INFO | ??:??:?? 1 AXP2101 PMU init succeeded, using AXP2101 PMU
[ 1100][D][XPowersAXP2101.tpp:2791] setInterruptImpl(): DISABLE - HEX:0xffffffff BIN:
DEBUG | ??:??:?? 1 =======================================================================
DEBUG | ??:??:?? 1 DC1 : + Voltage:3300 mV
DEBUG | ??:??:?? 1 DC2 : - Voltage:900 mV
DEBUG | ??:??:?? 1 DC3 : - Voltage:900 mV
DEBUG | ??:??:?? 1 DC4 : - Voltage:1100 mV
DEBUG | ??:??:?? 1 ALDO1: - Voltage:1800 mV
DEBUG | ??:??:?? 1 ALDO2: + Voltage:3300 mV
DEBUG | ??:??:?? 1 ALDO3: + Voltage:3300 mV
DEBUG | ??:??:?? 1 ALDO4: - Voltage:2900 mV
DEBUG | ??:??:?? 1 BLDO1: - Voltage:1800 mV
DEBUG | ??:??:?? 1 BLDO2: - Voltage:2800 mV
DEBUG | ??:??:?? 1 =======================================================================
DEBUG | ??:??:?? 1 Battery: usbPower=1, isCharging=0, batMv=4163, batPct=100
INFO | ??:??:?? 1 Scanning for i2c devices...
[ 1170][W][Wire.cpp:301] begin(): Bus already started in Master Mode.
DEBUG | ??:??:?? 1 Scanning for i2c devices on port 1
DEBUG | ??:??:?? 1 I2C device found at address 0x34
INFO | ??:??:?? 1 axp192/axp2101 PMU found
DEBUG | ??:??:?? 1 I2C device found at address 0x3c
INFO | ??:??:?? 1 ssd1306 display found
INFO | ??:??:?? 1 ssd1306 display found
DEBUG | ??:??:?? 1 0x4 subtype probed in 2 tries
INFO | ??:??:?? 1 2 I2C devices found
DEBUG | ??:??:?? 1 acc_info = 0
INFO | ??:??:?? 1 Meshtastic hwvendor=4, swver=2.2.16.1c6acfd
DEBUG | ??:??:?? 1 Setting random seed 77522584
DEBUG | ??:??:?? 1 Total heap: 185496
DEBUG | ??:??:?? 1 Free heap: 151108
DEBUG | ??:??:?? 1 Total PSRAM: 4192107
DEBUG | ??:??:?? 1 Free PSRAM: 4191847
DEBUG | ??:??:?? 1 NVS: UsedEntries 90, FreeEntries 540, AllEntries 630, NameSpaces 3
DEBUG | ??:??:?? 1 Setup Preferences in Flash Storage
DEBUG | ??:??:?? 1 Number of Device Reboots: 22880
DEBUG | ??:??:?? 1 OTA firmware version 0.2.1.2fbe7fc
INFO | ??:??:?? 1 Initializing NodeDB
INFO | ??:??:?? 1 Loading /prefs/db.proto
INFO | ??:??:?? 1 Loaded saved devicestate version 22
INFO | ??:??:?? 1 Loading /prefs/config.proto
INFO | ??:??:?? 1 Loaded saved config version 22
[ 1338][E][vfs_api.cpp:105] open(): /littlefs/prefs/module.proto does not exist, no permits for creation
INFO | ??:??:?? 1 No /prefs/module.proto preferences found
INFO | ??:??:?? 1 Installing default ModuleConfig
INFO | ??:??:?? 1 Loading /prefs/channels.proto
INFO | ??:??:?? 1 Loaded saved channelFile version 22
[ 1380][E][vfs_api.cpp:105] open(): /littlefs/oem/oem.proto does not exist, no permits for creation
INFO | ??:??:?? 1 No /oem/oem.proto preferences found
DEBUG | ??:??:?? 1 cleanupMeshDB purged 0 entries
WARN | ??:??:?? 1 Using nodenum 0x7a6c69c4
DEBUG | ??:??:?? 1 Number of Device Reboots: 22880
DEBUG | ??:??:?? 1 Expanding short PSK #1
INFO | ??:??:?? 1 Wanted region 1, using US
DEBUG | ??:??:?? 1 region=1, NODENUM=0x7a6c69c4, dbsize=16
INFO | ??:??:?? 1 Saving /prefs/db.proto
WARN | ??:??:?? 1 SPI.begin(SCK=5, MISO=19, MOSI=27, NSS=18)
DEBUG | ??:??:?? 1 Read RTC time as 1
INFO | ??:??:?? 1 Setting GPS power=1
DEBUG | ??:??:?? 1 WANT GPS=1
INFO | ??:??:?? 1 Setting GPS power=1
DEBUG | ??:??:?? 1 Using GPIO34 for GPS RX
DEBUG | ??:??:?? 1 Using GPIO12 for GPS TX
DEBUG | ??:??:?? 1 NeighborInfoModule is disabled
INFO | ??:??:?? 1 External Notification Module Disabled
INFO | ??:??:?? 1 Turning on screen
DEBUG | ??:??:?? 1 Module wants a UI Frame
DEBUG | ??:??:?? 1 Module wants a UI Frame
WARN | ??:??:?? 1 RF95Interface(cs=18, irq=26, rst=23, busy=33)
INFO | ??:??:?? 1 Starting meshradio init...
DEBUG | ??:??:?? 1 (bw=250, sf=11, cr=4/5) packet symLen=8 ms, payloadSize=0, time 231 ms
DEBUG | ??:??:?? 1 (bw=250, sf=11, cr=4/5) packet symLen=8 ms, payloadSize=253, time 2115 ms
INFO | ??:??:?? 1 Radio freq=906.875, config.lora.frequency_offset=0.000
INFO | ??:??:?? 1 Set radio: region=US, name=LongFast, config=0, ch=19, power=30
INFO | ??:??:?? 1 Radio myRegion->freqStart -> myRegion->freqEnd: 902.000000 -> 928.000000 (26.000000 mhz)
INFO | ??:??:?? 1 Radio myRegion->numChannels: 104 x 250.000kHz
INFO | ??:??:?? 1 Radio channel_num: 20
INFO | ??:??:?? 1 Radio frequency: 906.875000
INFO | ??:??:?? 1 Slot time: 42 msec
INFO | ??:??:?? 1 Set radio: final power level=20
DEBUG | ??:??:?? 1 Current limit set to 100.000000
DEBUG | ??:??:?? 1 Current limit set result 0
INFO | ??:??:?? 1 RF95 init result 0
INFO | ??:??:?? 1 Frequency set to 906.875000
INFO | ??:??:?? 1 Bandwidth set to 250.000000
INFO | ??:??:?? 1 Power output set to 20
INFO | ??:??:?? 1 RF95 Radio init succeeded, using RF95 radio
INFO | ??:??:?? 1 Not using WIFI
DEBUG | ??:??:?? 1 (bw=250, sf=11, cr=4/5) packet symLen=8 ms, payloadSize=237, time 2000 ms
DEBUG | ??:??:?? 1 LoRA bitrate = 118.500000 bytes / sec
INFO | ??:??:?? 1 PowerFSM init, USB power=0
DEBU���??:??:?? 1 Enter state: BOOT
[ 1857][D][esp32-hal-cpu.c:244] setCpuFrequencyMhz(): PLL: 320 / 4 = 80 Mhz, APB: 80000000 Hz
DEBUG | ??:??:?? 1 [Power] Battery: usbPower=1, isCharging=0, batMv=4163, batPct=100
DEBUG | ??:??:?? 1 [Screen] Screen: Started...
DEBUG | ??:??:?? 1 [GPS] WANT GPS=0
INFO | ??:??:?? 1 [GPS] Setting GPS power=0
INFO | ??:??:?? 1 [RangeTestModule] Range Test Module - Disabled
DEBUG | ??:??:?? 4 [PowerFSM] Enter state: ON
INFO | ??:??:?? 4 [PowerFSM] Initialise the NimBLE bluetooth module
INFO | ??:??:?? 6 [PowerFSM] Turning off screen
INFO | ??:??:?? 8 [PowerFSM] lsEnter begin, ls_secs=86400
INFO | ??:??:?? 9 [PowerFSM] Disable bluetooth
INFO | ??:??:?? 22 [PowerFSM] Exit light sleep gpio: btn=0
INFO | ??:??:?? 22 [PowerFSM] wakeCause2 7
INFO | ??:??:?? 22 [PowerFSM] Exit state: LS
DEBUG | ??:??:?? 22 [PowerFSM] Enter state: NB
INFO | ??:??:?? 22 [PowerFSM] Disable bluetooth |
|
Interrupt wdt timeout on CPU1 means that a long-running action may be executed inside an interrupt handler (e.g. serial print) which is bad and can lead to arbitrary errors, in this case a timeout exception is triggered and then panic with reboot. |
|
This issue has been mentioned on Meshtastic. There might be relevant details there: https://meshtastic.discourse.group/t/lilygo-t-bean-supreme-s3-boot-loop/9517/2 |
|
I created the forum post mentioned above. In my case, with the T-Beam Supreme, the device enters the boot loop as soon as it restarts after being set to the Router role. I will get the log output and add it here soon. |
|
It turns out that I can't post logs because I can't get the device out of the boot loop. The only way to recover is to flash the device. |
|
I have the same issue in Routermode with Tbeam v1.1 and 2.2.23. //\ E S H T /\ S T / C INFO | ??:??:?? 0 Booted, wake cause 0 (boot count 1), reset_reason=reset DEBUG | ??:??:?? 1 ======================================================================= Core 1 register dump: Backtrace: 0x40081c8a:0x3ffbfd2c |<-CORRUPTED Core 0 register dump: Backtrace: 0x4022c0fb:0x3ffbce30 0x4014d3d5:0x3ffbce50 0x40099384:0x3ffbce70 ELF file SHA256: 6dc29cd95c3c96f2 E (2385) esp_core_dump_flash: Core dump flash config is corrupted! CRC=0x7bd5c66f instead of 0x0 rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) //\ E S H T /\ S T / C |
|
There is hope... I could reproduce this issue! |
|
I have the same issue. The device works fine in client mode, but as soon as I set it into
I created a additional issue in the LilyGo repo: Xinyuan-LilyGO/LilyGo-LoRa-Series#161 Note: I am using |
Category
Other
Hardware
T-Beam
Firmware Version
2.2.160-beta
Description
Meshtastic will run without issue for several hours, but then crashes at some point and enters a loop of endless crash/reboot where the oled only shows the splash screen.
While I can't say for sure because I haven't been running 2.2.16 for very long, this issue seems to have emerged after I changed the configuration of this device from router+client to just router mode. I will be reverting to router+client to see if that improves things.
I also wasn't able to obtain logs from the first crash starts the crash/reboot loop yet, but the below logs are repeated on each crash/reboot cycle that follows.
Resetting the device via the RST button clears the issue and the device operates normally again until the next time the issue appears.
Will update this issue as more details are obtained.
Relevant log output
The text was updated successfully, but these errors were encountered: