zhp0406
commented
3 weeks ago @damiencampanella 1- The controller library location for Esp32-S3 is at esp-idf/components/bt/controller/lib_esp32c3_family/esp32s3/libbtdm_app.a.
2- Based on your description, your issue may have been fixed in the latest IDF. Please test using the latest IDF. Alternatively, please cherry-pick the following commit 0f29b3cef97d406c5887d79da8592308540cdda0
diff --git a/components/bt/controller/esp32c3/bt.c b/components/bt/controller/esp32c3/bt.c
index dadb5c49ac..b9ea92014d 100644
--- a/components/bt/controller/esp32c3/bt.c
+++ b/components/bt/controller/esp32c3/bt.c
@@ -651,7 +651,7 @@ static bool IRAM_ATTR is_in_isr_wrapper(void)
static void *malloc_internal_wrapper(size_t size)
{
- void *p = heap_caps_malloc(size, MALLOC_CAP_DEFAULT|MALLOC_CAP_INTERNAL|MALLOC_CAP_DMA);
+ void *p = heap_caps_malloc(size, MALLOC_CAP_INTERNAL|MALLOC_CAP_DMA);
if(p == NULL) {
ESP_LOGE(BT_LOG_TAG, "Malloc failed");
}
damiencampanella
Answers checklist.
IDF version.
v5.2-307-g99daa62628
Espressif SoC revision.
ESP32S3
Operating System used.
Windows
How did you build your project?
Command line with idf.py
If you are using Windows, please specify command line type.
CMD
Development Kit.
ESP32-S3-WROOM-1
Power Supply used.
External 5V
What is the expected behavior?
BT was running fine with IDF 4.4.2.
What is the actual behavior?
I migrated to IDF release 5.2 and I am getting a crash during the bluetooth controller initialization. The only change I made (for the BT related code) was to replace _esp_bluedroidinit(); with _esp_bluedroid_config_t bluedroid_cfg = BT_BLUEDROID_INIT_CONFIG_DEFAULT(); esp_bluedroid_init_with_cfg(&bluedroidcfg);
It seems that there is a malloc fail with idf 5.2.
I tried printing memory usage just prior to calling the function esp_bt_controller_init: I added the following lines:
But it seems that there is plenty of heap memory left: it prints
_heap_caps_get_total_size: 8685604 heap_caps_get_free_size: 8490004 heap_caps_get_minimum_free_size: 8489972 heap_caps_get_largest_free_block: 8257536
I noticed that there was a folder components\bt\controller\esp32s3 for IDF 4.4.2 that is missing for IDF 5.2. I can see in the logs that the esp32c3 controller is called, even if I installed the idf tools using the command install.bat esp32s3.
Steps to reproduce.
I guess that using the code: _esp_bt_controller_mem_release(ESP_BT_MODE_BLE); esp_bt_controller_config_t bt_cfg = BT_CONTROLLER_INIT_CONFIG_DEFAULT(); esp_bt_controller_init(&btcfg); on the same HW should reproduce the issue.
Debug Logs.
More Information.
No response