[Bug]: t-deck ends up in boot loop after being powered on for a day or so

sycophantic commented 1 month ago

Hardware

T-Deck

Firmware Version

2.3.9.f06c56a

Description

After the t-desk is powered on for a day or so the device ends up stuck in a boot loop and can't be reset unless you power cycle it. This also happens on the latest beta.

Relevant log output

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

INFO  | ??:??:?? 1 Booted, wake cause 0 (boot count 1), reset_reason=reset      
DEBUG | ??:??:?? 1 Filesystem files (495616/1048576 Bytes):                     
DEBUG | ??:??:?? 1  /prefs/channels.proto (145 Bytes)                           
DEBUG | ??:??:?? 1  /prefs/config.proto (138 Bytes)                             
DEBUG | ??:??:?? 1  /prefs/db.proto (3122 Bytes)                                
DEBUG | ??:??:?? 1  /prefs/module.proto (111 Bytes)                             
DEBUG | ??:??:?? 1  /static/.gitkeep (0 Bytes)                                  
DEBUG | ??:??:?? 1  /static/Logo_Black.svg.gz (602 Bytes)                       
DEBUG | ??:??:?? 1  /static/Logo_White.svg.gz (610 Bytes)                       
DEBUG | ??:??:?? 1  /static/apple-touch-icon.png.gz (3164 Bytes)                
DEBUG | ??:??:?? 1  /static/favicon.ico.gz (2270 Bytes)                         
DEBUG | ??:??:?? 1  /static/icon.svg.gz (852 Bytes)                             
DEBUG | ??:??:?? 1  /static/index-BMhLjTmL.css.gz (16270 Bytes)                 
DEBUG | ??:??:?? 1  /static/index-Bt2MYVVB.js.gz (203021 Bytes)                 
DEBUG | ??:??:?? 1  /static/index-CGqDWSD_.js.gz (348 Bytes)                    
DEBUG | ??:??:?? 1  /static/index.html.gz (548 Bytes)                           
DEBUG | ??:??:?? 1  /static/maplibre-gl-BXZZhNda.js.gz (210451 Bytes)           
DEBUG | ??:??:?? 1  /static/robots.txt.gz (42 Bytes)                            
DEBUG | ??:??:?? 1  /static/site.webmanifest.gz (197 Bytes)                     
DEBUG | ??:??:?? 2 Using analog input 4 for battery level                       
INFO  | ??:??:?? 2 ADCmod: ADC Characterization based on Two Point values and fe
INFO  | ??:??:?? 2 Scanning for i2c devices...                                  
DEBUG | ??:??:?? 2 Scanning for i2c devices on port 1                           
DEBUG | ??:??:?? 2 I2C device found at address 0x40                             
DEBUG | ??:??:?? 2 Wire.available() = 2                                         
DEBUG | ??:??:?? 2 Register MFG_UID: 0xffff                                     
INFO  | ??:??:?? 2 INA219 sensor found at address 0x40                          
DEBUG | ??:??:?? 3 I2C device found at address 0x55                             
INFO  | ??:??:?? 3 T-Deck keyboard found                                        
DEBUG | ??:??:?? 4 I2C device found at address 0x5d                             
INFO  | ??:??:?? 4 LPS22HB sensor found                                         
INFO  | ??:??:?? 5 3 I2C devices found                                          
DEBUG | ??:??:?? 5 acc_info = 0                                                 
DEBUG | ??:??:?? 5 found i2c sensor meshtastic_TelemetrySensorType_INA219       
DEBUG | ??:??:?? 5 found i2c sensor meshtastic_TelemetrySensorType_LPS22        
DEBUG | ??:??:?? 6 No SD_MMC card detected                                      
INFO  | ??:??:?? 6 Meshtastic hwvendor=50, swver=2.3.9.f06c56a                  
DEBUG | ??:??:?? 6 Setting random seed 803171772                                
DEBUG | ??:??:?? 6 Total heap: 276696                                           
DEBUG | ??:??:?? 6 Free heap: 234072                                            
DEBUG | ??:??:?? 6 Total PSRAM: 8386295                                         
DEBUG | ??:??:?? 6 Free PSRAM: 8386295                                          
DEBUG | ??:??:?? 6 NVS: UsedEntries 211, FreeEntries 419, AllEntries 630, NameS7
DEBUG | ??:??:?? 6 Setup Preferences in Flash Storage                           
DEBUG | ??:??:?? 6 Number of Device Reboots: 4997                               
DEBUG | ??:??:?? 6 OTA firmware version 0.2.1.ceca52c                           
INFO  | ??:??:?? 6 Initializing NodeDB                                          
INFO  | ??:??:?? 6 Loading /prefs/db.proto                                      
INFO  | ??:??:?? 6 Loaded /prefs/db.proto successfully                          
INFO  | ??:??:?? 6 Loaded saved devicestate version 22, with nodecount: 33      
INFO  | ??:??:?? 6 Loading /prefs/config.proto                                  
INFO  | ??:??:?? 6 Loaded /prefs/config.proto successfully                      
INFO  | ??:??:?? 6 Loaded saved config version 22                               
INFO  | ??:??:?? 6 Loading /prefs/module.proto                                  
INFO  | ??:??:?? 6 Loaded /prefs/module.proto successfully                      
INFO  | ??:??:?? 6 Loaded saved moduleConfig version 22                         
INFO  | ??:??:?? 6 Loading /prefs/channels.proto                                
INFO  | ??:??:?? 6 Loaded /prefs/channels.proto successfully                    
INFO  | ??:??:?? 6 Loaded saved channelFile version 22                          
INFO  | ??:??:?? 6 File /oem/oem.proto not found                                
DEBUG | ??:??:?? 6 cleanupMeshDB purged 0 entries                               
DEBUG | ??:??:?? 6 Using nodenum 0x27cc6404                                     
DEBUG | ??:??:?? 6 Number of Device Reboots: 4997                               
DEBUG | ??:??:?? 6 Expanding short PSK #1                                       
INFO  | ??:??:?? 6 Wanted region 1, using US                                    
INFO  | ??:??:?? 6 Saving /prefs/db.proto                                       
DEBUG | ??:??:?? 7 Using GPIO00 for button                                      
��@INFO  | ??:??:?? 1

KyleMaas commented 1 month ago

Pretty sure I've seen this, too, although usually on a shorter timescale than a full day.

sycophantic commented 1 month ago

@KyleMaas you are right, it is more often than a full day. I'm on the latest Alpha and it crashed after a few hours. I'm going to try leave it plugged into PC and see if I can grab a log before it crashes. I wonder if a certain message is causing it?

joneyes commented 1 month ago

I have seen the same today on 2.3.10 - though when it reboots, it does so clean. Reboot occured after about 10 mins connected. Log attached meshtastic-log-2024-05-25T11-06-13.134Z.log

djripcord commented 2 weeks ago

Seen this issue on a T-beam supreme as well as a Wisblock Rak 4631. In the 4631 instance I had to DFU flash. It was also important to run the factory erase .uf2 in order to get it in a state where it would accept firmware.

thebentern commented 2 weeks ago

These are different issues. The T-Deck one appears to be some issue with GPIO interrupts on light sleep, based on that last log. `INFO | 12:03:59 678 [PowerFSM] lsEnter begin, ls_secs=300

INFO | 12:03:59 678 [PowerFSM] setup LORA_DIO1 (GPIO45) with wakeup b`

meshtastic / firmware