Closed ZweiEuro closed 3 years ago
Arduino libraries are not intended to work inside RTOS.
In general? Oh, i didn't know that. Is there an alternative lib i can use for bluetooth? The esp32 raw gatts implementation is incredibly hard to use.
@maximkulkin the same thing happens when using the normal gatts demo from esp-idf :)
E (22678) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
E (22678) task_wdt: - IDLE0 (CPU 0)
E (22678) task_wdt: Tasks currently running:
E (22678) task_wdt: CPU 0: btController
E (22678) task_wdt: CPU 1: IDLE1
E (22678) task_wdt: Print CPU 0 (current core) backtrace
Backtrace:0x40138363:0x3FFBE8D0 0x40082E71:0x3FFBE8F0 0x401859E0:0x3FFB5E90 0x40185F95:0x3FFB5EB0 0x4008FED5:0x3FFB5EE0
#0 0x40138363:0x3 in task_wdt_isr at /home/zweieuro/.platformio/packages/framework-espidf/components/esp_common/src/task_wdt.c:187
E (22678) task_wdt: Print CPU 1 backtrace
Backtrace:0x40081DC3:0x3FFBEED0 0x40082E71:0x3FFBEEF0 0x4000BFED:0x3FFBC870 0x40090135:0x3FFBC880 0x40138607:0x3FFBC8A0 0x40138613:0x3FFBC8D0 0x401386C9:0x3FFBC8F0 0x40090B0D:0x3FFBC910 0x4008FED5:0x3FFBC930
E (27678) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
E (27678) task_wdt: - IDLE0 (CPU 0)
E (27678) task_wdt: Tasks currently running:
E (27678) task_wdt: CPU 0: btController
E (27678) task_wdt: CPU 1: IDLE1
E (27678) task_wdt: Print CPU 0 (current core) backtrace
Backtrace:0x40138363:0x3FFBE8D0 0x40082E71:0x3FFBE8F0 0x401859E0:0x3FFB5E90 0x40185F95:0x3FFB5EB0 0x4008FED5:0x3FFB5EE0
#0 0x40138363:0x3 in task_wdt_isr at /home/zweieuro/.platformio/packages/framework-espidf/components/esp_common/src/task_wdt.c:187
E (27678) task_wdt: Print CPU 1 backtrace
Backtrace:0x40081DC3:0x3FFBEED0 0x40082E71:0x3FFBEEF0 0x4000BFED:0x3FFBC870 0x40090135:0x3FFBC880 0x40138607:0x3FFBC8A0 0x40138613:0x3FFBC8D0 0x401386C9:0x3FFBC8F0 0x40090B0D:0x3FFBC910 0x4008FED5:0x3FFBC930
E (32678) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
E (32678) task_wdt: - IDLE0 (CPU 0)
E (32678) task_wdt: Tasks currently running:
E (32678) task_wdt: CPU 0: btController
E (32678) task_wdt: CPU 1: IDLE1
E (32678) task_wdt: Print CPU 0 (current core) backtrace
Backtrace:0x40138363:0x3FFBE8D0 0x40082E71:0x3FFBE8F0 0x401859E0:0x3FFB5E90 0x40185F95:0x3FFB5EB0 0x4008FED5:0x3FFB5EE0
#0 0x40138363:0x3 in task_wdt_isr at /home/zweieuro/.platformio/packages/framework-espidf/components/esp_common/src/task_wdt.c:187
E (32678) task_wdt: Print CPU 1 backtrace
Backtrace:0x40081DC3:0x3FFBEED0 0x40082E71:0x3FFBEEF0 0x4000BFED:0x3FFBC870 0x40090135:0x3FFBC880 0x40138607:0x3FFBC8A0 0x40138613:0x3FFBC8D0 0x401386C9:0x3FFBC8F0 0x40090B0D:0x3FFBC910 0x4008FED5:0x3FFBC930
Looks like you're doing something long running inside callbacks not meant for that and it triggers task watchdog (it checks that tasks are not stuck).
You mean in the bluetooth controller ? Its the basic example they have for bte, I am not doing any computation in it
OK, I'm not a fortune teller, but if vanilla ESP-IDF example does not work, you should be asking Espressif.
That's the issue, it seems to only not work when I try to use it while using your library as well
I completely understand that this is just an issue of my project and it's not your job to help me, but I wanted to ask for your general guess where I could start looking for the cause
I take it back, it's actually the example, thanks for your help !
When i use both bluetooth from here: https://github.com/nkolban/ESP32_BLE_Arduino and your homekit server i get these types of errors: