ESP32 Forum

Hi,
I'm using current git master tree.
I hit bellow assertion, but I don't find lld_pdu.c in esp-idf.
Any idea bout this panic issue?

ASSERT_PARAM(10 9), in lld_pdu.c at line 519
Guru Meditation Error: Core 0 panic'ed (Interrupt wdt timeout on CPU0)
Core 0 register dump:
PC : 0x400845fd PS : 0x00060b34 A0 : 0x80087556 A1 : 0x3ffbe640
0x400845fd: r_assert_param at ??:?

A2 : 0x00000001 A3 : 0x00000000 A4 : 0x00000000 A5 : 0x60008054
A6 : 0x3ffbdcd4 A7 : 0x60008050 A8 : 0x800845fd A9 : 0x3ffbe620
A10 : 0x00000004 A11 : 0x00000000 A12 : 0x6000804c A13 : 0xffffffff
A14 : 0x00000000 A15 : 0xfffffffc SAR : 0x00000004 EXCCAUSE: 0x00000005
EXCVADDR: 0x00000000 LBEG : 0x40084535 LEND : 0x4008453c LCOUNT : 0x00000000
0x40084535: r_assert_param at ??:?

0x4008453c: r_assert_param at ??:?

Core 0 was running in ISR context:
EPC1 : 0x40009203 EPC2 : 0x00000000 EPC3 : 0x00000000 EPC4 : 0x400845fd
0x400845fd: r_assert_param at ??:?


Backtrace: 0x400845fd:0x3ffbe640 0x40087553:0x3ffbe660 0x400485a5:0x3ffbe690 0x4004868d:0x3ffbe6b0 0x4008793e:0x3ffbe6d0 0x400887a7:0x3ffbe6f0 0x40082541:0x3ffbe710 0x40090f4a:0x00000000
0x400845fd: r_assert_param at ??:?

0x40087553: r_lld_pdu_rx_handler at ??:?

0x4008793e: r_rwble_isr at ??:?

0x400887a7: r_rwbtdm_isr_wrapper at intc.c:?

0x40082541: _xt_lowint1 at /home/test/esp/esp-idf/components/freertos/xtensa_vectors.S:1105

0x40090f4a: vTaskEnterCritical at /home/test/esp/esp-idf/components/freertos/tasks.c:3564


Core 1 register dump:
PC : 0x401852aa PS : 0x00060634 A0 : 0x800d34b9 A1 : 0x3ffbc350
0x401852aa: esp_pm_impl_waiti at /home/test/esp/esp-idf/components/esp32/pm_esp32.c:474

A2 : 0x00000000 A3 : 0x80000001 A4 : 0x00000000 A5 : 0x00000001
A6 : 0x00060021 A7 : 0x00000000 A8 : 0x800d31a2 A9 : 0x3ffbc320
A10 : 0x00000000 A11 : 0x00000001 A12 : 0x800908a6 A13 : 0x3ffd0fa0
A14 : 0x00000003 A15 : 0x00060023 SAR : 0x00000000 EXCCAUSE: 0x00000005
EXCVADDR: 0x00000000 LBEG : 0x00000000 LEND : 0x00000000 LCOUNT : 0x00000000

Backtrace: 0x401852aa:0x3ffbc350 0x400d34b6:0x3ffbc370 0x40091649:0x3ffbc390
0x401852aa: esp_pm_impl_waiti at /home/test/esp/esp-idf/components/esp32/pm_esp32.c:474

0x400d34b6: esp_vApplicationIdleHook at /home/test/esp/esp-idf/components/esp32/freertos_hooks.c:86

0x40091649: prvIdleTask at /home/test/esp/esp-idf/components/freertos/tasks.c:3564

Seems like the app crashed in the BLE handler; the BLE driver is not open-source, hence you not being able to find the file. Anything specific you do? I'd personally suspect memory corruption for this, but it's hard to tell from just the crash dump.

My application has both bt & wifi enabled.
After calling esp_ble_gap_start_scanning() in ESP_GAP_BLE_SCAN_PARAM_SET_COMPLETE_EVT,
the BLE handler only copy the scan result to a buffer (in memory).

BTW, today I cannot reproduce the previous "ASSERT_PARAM(10 9), in lld_pdu.c at line 519"
but I hit another assertion several times:

ASSERT_PARAM(512 0), in rwble.c at line 222
Guru Meditation Error: Core 0 panic'ed (Interrupt wdt timeout on CPU0)
Core 0 register dump:
PC : 0x4008462c PS : 0x00060034 A0 : 0x80087c0a A1 : 0x3ffbe6b0
0x4008462c: r_assert_param at ??:?

A2 : 0x00000001 A3 : 0x00000000 A4 : 0x00000000 A5 : 0x60008054
A6 : 0x3ffbdcd4 A7 : 0x60008050 A8 : 0x80084629 A9 : 0x3ffbe690
A10 : 0x00000004 A11 : 0x00000000 A12 : 0x6000804c A13 : 0xffffffff
A14 : 0x00000000 A15 : 0xfffffffc SAR : 0x00000004 EXCCAUSE: 0x00000005
EXCVADDR: 0x00000000 LBEG : 0x40084561 LEND : 0x40084568 LCOUNT : 0x00000000
0x40084561: r_assert_param at ??:?

0x40084568: r_assert_param at ??:?

Core 0 was running in ISR context:
EPC1 : 0x40185912 EPC2 : 0x00000000 EPC3 : 0x00000000 EPC4 : 0x4008462c
0x40185912: esp_pm_impl_waiti at /home/test/esp/esp-idf/components/esp32/pm_esp32.c:474

0x4008462c: r_assert_param at ??:?


Backtrace: 0x4008462c:0x3ffbe6b0 0x40087c07:0x3ffbe6d0 0x400887d3:0x3ffbe6f0 0x4008256d:0x3ffbe710 0x4018590f:0x00000000
0x4008462c: r_assert_param at ??:?

0x40087c07: r_rwble_isr at ??:?

0x400887d3: r_rwbtdm_isr_wrapper at intc.c:?

0x4008256d: _xt_lowint1 at /home/test/esp/esp-idf/components/freertos/xtensa_vectors.S:1105

0x4018590f: esp_pm_impl_waiti at /home/test/esp/esp-idf/components/esp32/pm_esp32.c:474


Core 1 register dump:
PC : 0x40185912 PS : 0x00060634 A0 : 0x800d34dd A1 : 0x3ffbc390
0x40185912: esp_pm_impl_waiti at /home/test/esp/esp-idf/components/esp32/pm_esp32.c:474

A2 : 0x00000000 A3 : 0x80000001 A4 : 0x00000000 A5 : 0x00000001
A6 : 0x00000000 A7 : 0x00000000 A8 : 0x800d31c2 A9 : 0x3ffbc360
A10 : 0x00000000 A11 : 0x00000001 A12 : 0x80090902 A13 : 0x3ffbc2a0
A14 : 0x00000003 A15 : 0x00060023 SAR : 0x00000000 EXCCAUSE: 0x00000005
EXCVADDR: 0x00000000 LBEG : 0x00000000 LEND : 0x00000000 LCOUNT : 0x00000000

Backtrace: 0x40185912:0x3ffbc390 0x400d34da:0x3ffbc3b0 0x400914f1:0x3ffbc3d0 0x400906f9:0x3ffbc3f0
0x40185912: esp_pm_impl_waiti at /home/test/esp/esp-idf/components/esp32/pm_esp32.c:474

0x400d34da: esp_vApplicationIdleHook at /home/test/esp/esp-idf/components/esp32/freertos_hooks.c:86

0x400914f1: prvIdleTask at /home/test/esp/esp-idf/components/freertos/tasks.c:3564

0x400906f9: vPortTaskWrapper at /home/test/esp/esp-idf/components/freertos/port.c:403

I cannot find rwble.c (I think it's in a closed source library), so I have no idea what is going on.

Itd hard to determine what it's the issue but devs are working on it.

This precise crash occurs on our product too - it is the only reason it crashes, even when the system is left for days at a time. Since we require at least 12 hours of continuous operation it is a problem we would like to see fixed.

I should also point out that it has been happening for a considerable period across many releases of the code.

I can confirm, in our case, that it happens when we stop scanning, we scan for beacons for a period and then stop and collate results.

I suspect we could just keep scanning in that case but we will need to stop to connect to devices etc.

Since it is a commercial product, there is a lot at stake so a timely solution is paramount for us.

Is there any chance you can whittle your code down to a minimal example that you can share with us and that exhibits the issue?

Sorry, but I don't think it is possible.

We have at least 30 tasks in a complex system running on proprietary HW - and the failure only happens rarely.

I can tell you that we do not use WiFi or BT Classic in normal running mode, just BLE. We use the BLE to scan for beacons and the error occurs even when we have no BLE devices attached.

I can help out using our system if you have any patches to apply for debug purposes. I can leave a system running and send you the resulting logs for instance.

I can also try any fixes of course.

We can only wait for some time yet:
https://github.com/espressif/esp-idf/is ... -434271002

I have also experienced both of these crashes.
In my example I am connecting and disconnecting to two BLE sensors and then sending the data over wifi to a server. I basically only have two tasks running, so nothing too complex...