#Voice PE bootloops due to a watchdog timeout problem (v 24.12.8)

1 messages · Page 1 of 1 (latest)

thorny otter
#

I received two voice pe today. After the first setup the bootloop problems started. When I reflash the boards everything works until I remove the power, then they just bootloop.
Does anyone have the same problem, or has an idea?

[18:01:54][I][wifi:617]: WiFi Connected!
[18:01:54][C][wifi:428]:   Local MAC: 20:F8:3B:09:30:F4
[18:01:54][C][wifi:433]:   SSID: 'MyWifi'[redacted]
[18:01:54][C][wifi:436]:   IP Address: 192.168.2.78
[18:01:54][C][wifi:439]:   BSSID: 5C:E9:31:B1:71:F2[redacted]
[18:01:54][C][wifi:441]:   Hostname: 'home-assistant-voice-0930f4'
[18:01:54][C][wifi:443]:   Signal strength: -44 dB ▂▄▆█
[18:01:54][C][wifi:447]:   Channel: 6
[18:01:54][C][wifi:448]:   Subnet: 255.255.255.0
[18:01:54][C][wifi:449]:   Gateway: 192.168.2.1
[18:01:54][C][wifi:450]:   DNS1: 192.168.2.160
[18:01:54][C][wifi:451]:   DNS2: 1.1.1.1
[18:01:54][C][api:026]: Setting up Home Assistant API server...
[18:01:54][C][micro_wake_word:083]: Setting up microWakeWord...
[18:01:54][C][micro_wake_word:109]: Micro Wake Word initialized
[18:01:54][I][app:062]: setup() finished successfully!
[18:01:58][D][esp-idf:000][wifi]: I (20245) wifi:
[18:01:58][D][esp-idf:000][wifi]: <ba-add>idx:1 (ifx:0, 5c:e9:31:b1:71:f2), tid:0, ssn:0, winSize:64
[18:01:58][D][esp-idf:000][wifi]: 
[18:01:58]
[18:01:59]E (21342) task_wdt: Task watchdog got triggered. The following tasks/users did not reset the watchdog in time:
[18:01:59]E (21342) task_wdt:  - loopTask (CPU 0)
[18:01:59]E (21342) task_wdt: Tasks currently running:
[18:01:59]E (21342) task_wdt: CPU 0: IDLE0
[18:01:59]E (21342) task_wdt: CPU 1: IDLE1
[18:01:59]E (21342) task_wdt: Aborting.
[18:01:59]E (21342) task_wdt: Print CPU 0 (current core) backtrace
[18:01:59]
[18:01:59]
[18:01:59]
[18:01:59]
[18:01:59]Backtrace: 0x40383577:0x3fcaffc0 0x420b2d31:0x3fcaffe0 0x4038717b:0x3fcb0000
[18:01:59]
[18:01:59]
[18:01:59]
[18:01:59]
[18:01:59]ELF file SHA256: c77aced757c7321d
[18:01:59]
[18:01:59]Rebooting...