tony-fav / tasmota-blerry

GNU General Public License v3.0
96 stars 29 forks source link

Crash during setup on Tasmota 12.5.0 #74

Closed rspier closed 2 months ago

rspier commented 1 year ago
Rebooting...
ets Jul 29 2019 12:21:46

rst:0xc (SW_CPU_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:184
load:0x40078000,len:12680
load:0x40080400,len:2908
entry 0x400805c4

00:00:00.002 HDW: ESP32-D0WD-V3 
00:00:00.055 UFS: FlashFS mounted with 296 kB free
00:00:00.086 CFG: Loaded from File, Count 14
00:00:00.096 QPC: Count 1
00:00:00.253 BRY: Berry initialized, RAM used=4041 bytes
00:00:00.271 TFS: File '.drvset003' not found
00:00:00.271 CFG: Energy use defaults as file system not ready or file not found
00:00:00.276 Project tasmota - Tasmota Version 12.5.0(bluetooth)-2_0_7(2023-04-17T08:07:04)
00:00:00.288 iBeacon register for advert callbacks
00:00:00.288 MI32Option0: 1
00:00:00.288 MI32Option1: 0
00:00:00.289 MI32Option2: 0
00:00:00.299 MI32Option4: 1
00:00:00.300 MI32Option5: 0
00:00:00.300 MI32Option6: 0
00:00:00.300 M32: init: request callbacks
00:00:00.955 WIF: Connecting to AP1 REMOVED Channel 6 BSSId 58:CB:52:AB:40:76 in mode 11n as tasmota-6393B0-5040...
00:00:01.097 WIF: Connected
00:00:01.357 HTP: Web server active on tasmota-6393B0-5040 with IP address 10.0.0.138
03:36:05.003 BLE: MasterEnable->1
03:36:05.011 BLE: BLETask:Starting NimBLE
03:36:05.766 RSL: INFO1 = {"Info1":{"Module":"ESP32-DevKit","Version":"12.5.0(bluetooth)","FallbackTopic":"cmnd/DVES_6393B0_fb/","GroupTopic":"cmnd/tasmotas/"}}
03:36:05.781 RSL: INFO2 = {"Info2":{"WebServerMode":"Admin","Hostname":"tasmota-6393B0-5040","IPAddress":"10.0.0.138","IP6Global":"REMOVED","IP6Local":"REMOVED"}}
03:36:05.802 RSL: INFO3 = {"Info3":{"RestartReason":{"Exception":29,"Reason":"StoreProhibited","EPC":"40084c54","EXCVADDR":"00000000","CallChain":["40084c51","40098a55","4009e33d","401ed352","401ec5af","401ec516","401ec5c1","4011175a","401117ce","40109131","4012c968","400f0479","400f05a3","400f1709","400f28da","400f7f66","4012f970","4011824d","401107ae","40110ee5","40112151","4014cd89","4011b209","401577d6","40161481","400e698b"]},"BootCount":7}}
03:36:08.911 QPC: Reset
03:36:08.918 RSL: STATE = {"Time":"2023-06-12T03:36:08","Uptime":"0T00:00:06","UptimeSec":6,"Heap":89,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":0,"Berry":{"HeapUsed":3,"Objects":45},"Wifi":{"AP":1,"SSId":"REMOVED","BSSId":"REMOVED","Channel":6,"Mode":"11n","RSSI":100,"Signal":-39,"LinkCount":1,"Downtime":"0T00:00:02"}}
03:36:08.949 RSL: BLE = {"Time":"2023-06-12T03:36:08","BLEDevices":REMOVED}
03:36:08.962 RSL: BLE = {"Time":"2023-06-12T03:36:08","BLE":{"scans":0,"adverts":30,"devices":1,"resets":0}}
03:37:14.145 CMD: br load('blerry_setup.be')

abort() was called at PC 0x401ed352 on core 1

Backtrace: 0x40084c51:0x3ffd33c0 0x40098a55:0x3ffd33e0 0x4009e33d:0x3ffd3400 0x401ed352:0x3ffd3480 0x401ec5af:0x3ffd34a0 0x401ec516:0x3ffd34c0 0x401ec5c1:0x3ffd34e0 0x4011175a:0x3ffd3500 0x401117ce:0x3ffd3540 0x40109131:0x3ffd3560 0x4012c968:0x3ffd3620 0x400f0479:0x3ffd3640 0x400f05a3:0x3ffd3700 0x400f1709:0x3ffd3720 0x400f28da:0x3ffd3740 0x400f7f66:0x3ffd37c0 0x4012b9bd:0x3ffd3800 0x4015cb6e:0x3ffd3880 0x4012ed74:0x3ffd38c0 0x4011b209:0x3ffd38e0 0x40161331:0x3ffd3900 0x40161455:0x3ffd39f0 0x401626dd:0x3ffd3a60 0x400e698b:0x3ffd3ad0

ELF file SHA256: 0000000000000000

Rebooting...
tony-fav commented 1 year ago

Is this only happening on 12.5.0? Does it work fine on a version older on the same device?

rspier commented 1 year ago

It works fine on 12.0.2.

rspier commented 1 year ago

The device is https://www.amazon.com/dp/B08246MCL5, a generic WROOM-32 dev board.

I've been looking for a way to interpret the Backtrace, but not finding it.

bam80 commented 9 months ago

Is this still happening with 13.x?

tony-fav commented 2 months ago

I have reports that blerry is working fine even on 14.1 with a modified startup rule (that adds a delay before starting blerry). So, I am closing this issue.