Nimble BLufi Host Stack with some problem after 5.2.3 as stack size start to overflow telling BTC_STACK (IDFGH-13796)

[filzek]

Answers checklist.

• I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
• I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
• I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report

Nimble BLufi Host Stack with some problem after 5.2.3 as stack size start to overflow

ERROR A stack overflow in task BTC_TASK has been detected.

So, something is weirdo, as this doenst happen before

[rahult-github]

Hi @filzek ,

Request you to always share complete log and sdkconfig whenever you raise any issue.

As for this issue, please try increasing the STACK_SIZE in menuconfig to see if it helps.

[filzek]

@rahult-github

ERROR A stack overflow in task BTC_TASK has been detected.

Backtrace: 0x40081931:0x3ffed8e0 0x40095c61:0x3ffed900 0x4009615d:0x3ffed920 0x400968c9:0x3ffed9a0 0x40095d5c:0x3ffed9c0 0x40095d0e:0x40091fc3 |<-CORRUPTED
--- 0x40081931: panic_abort at C:/Espressif/frameworks/esp-idf-v5.2/components/esp_system/panic.c:466
0x40095c61: esp_system_abort at C:/Espressif/frameworks/esp-idf-v5.2/components/esp_system/port/esp_system_chip.c:93
0x4009615d: vApplicationStackOverflowHook at C:/Espressif/frameworks/esp-idf-v5.2/components/freertos/FreeRTOS-Kernel/portable/xtensa/port.c:558
0x400968c9: vTaskSwitchContext at C:/Espressif/frameworks/esp-idf-v5.2/components/freertos/FreeRTOS-Kernel/tasks.c:3664 (discriminator 7)
0x40095d5c: _frxt_dispatch at C:/Espressif/frameworks/esp-idf-v5.2/components/freertos/FreeRTOS-Kernel/portable/xtensa/portasm.S:451
0x40095d0e: _frxt_int_exit at C:/Espressif/frameworks/esp-idf-v5.2/components/freertos/FreeRTOS-Kernel/portable/xtensa/portasm.S:246
0x40091fc3: strcmp at /builds/idf/crosstool-NG/.build/HOST-x86_64-w64-mingw32/xtensa-esp-elf/src/newlib/newlib/libc/machine/xtensa/strcmp.S:47

We are using NIMBLE and attached are the SDKCONFIG, it was supose that the BTC_TASK does nothing as the NIMBLE TASK should be in charge of all running code in the NIMBLE/BLUFI callback, and somehow it is trigerring the problem.

The SDK 5.2 to 5.2.2 did not bring this problem and this only happen in the 5.2.3, so, something related to the internal affairs of BTC_TASK to NIMBLE task has creating this issue

[rahult-github]

Hi @filzek ,

There is no sdkconfig attached in previous comment, please share it. Also, initial comment didn't mention regarding any crash / backtrace information. Can you please share the elf file also in this case ?

[filzek]

Hi @filzek ,

There is no sdkconfig attached in previous comment, please share it. Also, initial comment didn't mention regarding any crash / backtrace information. Can you please share the elf file also in this case ?

please send me a private email address to send it private to you as well, i will send the elf file.
sdkconfig.txt

[rahult-github]

Hi @filzek ,

Your sdkconfig has below settings. So bluedroid is used and not nimble. I will re-direct issue to correct team in this case, since the heading mentioned NimBLE stack .

Bluetooth

CONFIG_BT_ENABLED=y
CONFIG_BT_BLUEDROID_ENABLED=y
CONFIG_BT_NIMBLE_ENABLED is not set
CONFIG_BT_CONTROLLER_ONLY is not set
CONFIG_BT_CONTROLLER_ENABLED=y
CONFIG_BT_CONTROLLER_DISABLED is not set

[filzek]

@rahult-github

Hi, something is wrong, as the SDKCONFIG attached show the below info:

Hi @filzek ,

Your sdkconfig has below settings. So bluedroid is used and not nimble. I will re-direct issue to correct team in this case, since the heading mentioned NimBLE stack .

Bluetooth
CONFIG_BT_ENABLED=y
CONFIG_BT_BLUEDROID_ENABLED=y
CONFIG_BT_NIMBLE_ENABLED is not set
CONFIG_BT_CONTROLLER_ONLY is not set
CONFIG_BT_CONTROLLER_ENABLED=y
CONFIG_BT_CONTROLLER_DISABLED is not set

Bluetooth

CONFIG_BT_ENABLED=y

CONFIG_BT_BLUEDROID_ENABLED is not set

CONFIG_BT_NIMBLE_ENABLED=y

CONFIG_BT_CONTROLLER_ONLY is not set

CONFIG_BT_CONTROLLER_ENABLED=y

CONFIG_BT_CONTROLLER_DISABLED is not set

we are using NMBLE, as per show in the SDKCONFIG file, maybe you have open a wrong SDKCONFIG.TXT file.