Modifying Matter Controller Example with BLE Provisioning Causes LoadProhibited Error

[iamiha]

Description:
I am modifying the Matter repository's controller example to use standard BLE provisioning. Once provisioning is complete, the controller should start automatically.

Changes Implemented:

• Implemented standard BLE provisioning.
• After successful provisioning, start_controller() is called to initialize and start the Matter controller.

Issue:

Provisioning works correctly, but when start_controller() is called, a LoadProhibited error occurs, leading to a Guru Meditation crash.

Relevant Code:

void start_controller() {
  esp_err_t err = ESP_OK;

  #if CONFIG_ENABLE_CHIP_SHELL
    esp_matter::console::diagnostics_register_commands();
    esp_matter::console::wifi_register_commands();
    esp_matter::console::init();
    #if CONFIG_ESP_MATTER_CONTROLLER_ENABLE
      esp_matter::console::controller_register_commands();
    #endif
  #endif

  err = esp_matter::start(app_event_cb);
  ABORT_APP_ON_FAILURE(err == ESP_OK, ESP_LOGE(TAG, "Failed to start Matter, err:%d", err));

  #if CONFIG_ESP_MATTER_COMMISSIONER_ENABLE
    esp_matter::lock::chip_stack_lock(portMAX_DELAY);
    esp_matter::controller::matter_controller_client::get_instance().init(112233, 1, 5580);
    esp_matter::controller::matter_controller_client::get_instance().setup_commissioner();
    esp_matter::lock::chip_stack_unlock();
  #endif
}

Error Output:

I (29626) app_main: binded , starting es-matter
I (29716) chip[DL]: NVS set: chip-counters/reboot-count = 1 (0x1)
I (29716) chip[DL]: NVS set: chip-counters/total-hours = 0 (0x0)
I (29726) chip[DL]: NVS set: chip-config/unique-id = "1997E661A0593838"
I (29726) chip[DL]: Real time clock set to 946684800 (0100/00/01 00:00:00 UTC)
btdm: bss start 0x3fcef180, len 36
btdm: data start 0x3fcef174, data start rom 0x40057350, len 12
--- 0x40057350: _data_start_btdm_rom in ROM

MAGIC fadebead VERSION 00010009
I (29726) BLE_INIT: BT controller compile version [c66a703]
Guru Meditation Error: Core  0 panic'ed (LoadProhibited). Exception was unhandled.

Core  0 register dump:
PC      : 0x420ad671  PS      : 0x00060630  A0      : 0x820bcc04  A1      : 0x3fcdb950  
--- 0x420ad671: semphr_delete_wrapper at /home/farhana/idf/idfv5.2.3/esp/v5.2.3/esp-idf/components/bt/controller/esp32c3/bt.c:568

A2      : 0x0101a8c0  A3      : 0x00000000  A4      : 0x00060620  A5      : 0x3fcdb9c0  
A6      : 0x3fcdb9a0  A7      : 0x0000000c  A8      : 0x00000000  A9      : 0x3fcdb900  
A10     : 0x00000047  A11     : 0x3fcdb9c0  A12     : 0x3fcdb9a0  A13     : 0x0000000c  
--- Warning: Writing to serial is timing out. Please make sure that your application supports an interactive console and that you have picked the correct console for serial communication.
--- Warning: Writing to serial is timing out. Please make sure that your application supports an interactive console and that you have picked the correct console for serial communication.
A14     : 0x00000011  A15     : 0x3fca0e60  SAR     : 0x0000000e  EXCCAUSE: 0x0000001c  
EXCVADDR: 0x0101a8c0  LBEG    : 0x40056f08  LEND    : 0x40056f12  LCOUNT  : 0x00000000  
--- 0x40056f08: __memcpy_aux in ROM
0x40056f12: __memcpy_aux in ROM



Backtrace: 0x420ad66e:0x3fcdb950 0x420bcc01:0x3fcdb970 0x420bdaf0:0x3fcdb990 0x420adec5:0x3fcdb9e0 0x420b62cf:0x3fcdba20 0x42073e75:0x3fcdba80 0x420745eb:0x3fcdbaa0 0x42074736:0x3fcdbb00 0x42073045:0x3fcdbb20 0x42073395:0x3fcdbb40 0x420733c9:0x3fcdbbb0 0x4038091e:0x3fcdbbd0
--- 0x420ad66e: semphr_delete_wrapper at /home/farhana/idf/idfv5.2.3/esp/v5.2.3/esp-idf/components/bt/controller/esp32c3/bt.c:561
0x420bcc01: ble_sm_sc_init at ??:?
0x420bdaf0: btdm_controller_init at ??:?
0x420adec5: esp_bt_controller_init at /home/farhana/idf/idfv5.2.3/esp/v5.2.3/esp-idf/components/bt/controller/esp32c3/bt.c:1436
0x420b62cf: nimble_port_init at /home/farhana/idf/idfv5.2.3/esp/v5.2.3/esp-idf/components/bt/host/nimble/nimble/porting/nimble/src/nimble_port.c:178
0x42073e75: chip::DeviceLayer::Internal::BLEManagerImpl::InitESPBleLayer() at /home/farhana/github/matter-gw/build/esp-idf/chip/../../../../../idf/idfv5.2.3/.espressif/esp-matter/connectedhomeip/connectedhomeip/config/esp32/third_party/connectedhomeip/src/platform/ESP32/nimble/BLEManagerImpl.cpp:926
0x420745eb: chip::DeviceLayer::Internal::BLEManagerImpl::DriveBLEState() at /home/farhana/github/matter-gw/build/esp-idf/chip/../../../../../idf/idfv5.2.3/.espressif/esp-matter/connectedhomeip/connectedhomeip/config/esp32/third_party/connectedhomeip/src/platform/ESP32/nimble/BLEManagerImpl.cpp:743
0x42074736: chip::DeviceLayer::Internal::BLEManagerImpl::DriveBLEState(int) at /home/farhana/github/matter-gw/build/esp-idf/chip/../../../../../idf/idfv5.2.3/.espressif/esp-matter/connectedhomeip/connectedhomeip/config/esp32/third_party/connectedhomeip/src/platform/ESP32/nimble/BLEManagerImpl.cpp:1743
0x42073045: chip::DeviceLayer::Internal::GenericPlatformManagerImpl<chip::DeviceLayer::PlatformManagerImpl>::_DispatchEvent(chip::DeviceLayer::ChipDeviceEvent const*) at /home/farhana/github/matter-gw/build/esp-idf/chip/../../../../../idf/idfv5.2.3/.espressif/esp-matter/connectedhomeip/connectedhomeip/config/esp32/third_party/connectedhomeip/src/include/platform/internal/GenericPlatformManagerImpl.ipp:304
0x42073395: chip::DeviceLayer::PlatformManager::DispatchEvent(chip::DeviceLayer::ChipDeviceEvent const*) at /home/farhana/github/matter-gw/build/esp-idf/chip/../../../../../idf/idfv5.2.3/.espressif/esp-matter/connectedhomeip/connectedhomeip/config/esp32/third_party/connectedhomeip/src/include/platform/PlatformManager.h:503
 (inlined by) chip::DeviceLayer::Internal::GenericPlatformManagerImpl_FreeRTOS<chip::DeviceLayer::PlatformManagerImpl>::_RunEventLoop() at /home/farhana/github/matter-gw/build/esp-idf/chip/../../../../../idf/idfv5.2.3/.espressif/esp-matter/connectedhomeip/connectedhomeip/config/esp32/third_party/connectedhomeip/src/include/platform/internal/GenericPlatformManagerImpl_FreeRTOS.ipp:257
0x420733c9: chip::DeviceLayer::PlatformManager::RunEventLoop() at /home/farhana/github/matter-gw/build/esp-idf/chip/../../../../../idf/idfv5.2.3/.espressif/esp-matter/connectedhomeip/connectedhomeip/config/esp32/third_party/connectedhomeip/src/include/platform/PlatformManager.h:403
 (inlined by) chip::DeviceLayer::Internal::GenericPlatformManagerImpl_FreeRTOS<chip::DeviceLayer::PlatformManagerImpl>::EventLoopTaskMain(void*) at /home/farhana/github/matter-gw/build/esp-idf/chip/../../../../../idf/idfv5.2.3/.espressif/esp-matter/connectedhomeip/connectedhomeip/config/esp32/third_party/connectedhomeip/src/include/platform/internal/GenericPlatformManagerImpl_FreeRTOS.ipp:280
0x4038091e: vPortTaskWrapper at /home/farhana/idf/idfv5.2.3/esp/v5.2.3/esp-idf/components/freertos/FreeRTOS-Kernel/portable/xtensa/port.c:134

Request for Help:

• Has anyone successfully integrated BLE provisioning with the Matter controller?
• Could there be conflicts between the BLE provisioning stack and Matter’s BLE usage?
• Are there any recommended steps to cleanly stop BLE provisioning before initializing the Matter controller?

Any insights or suggestions would be greatly appreciated!

sdkconfig.txt

[dhrishi]

@iamiha I see the following in your sdkconfig -

# CONFIG_WIFI_PROV_KEEP_BLE_ON_AFTER_PROV is not set

Can you please check if BLE is getting deinited after provisioning? Ideally, you would need it for Matter BLE-based commissioning. So, you should set the above option.

[iamiha]

After enabling CONFIG_WIFI_PROV_KEEP_BLE_ON_AFTER_PROV=y, I encountered the following error:

E (51756) BLE_INIT: controller init failed
assert failed: ble_svc_gap_init ble_svc_gap.c:333 (rc == 0)

Full log message :

I (50426) app_main: binded , starting es-matter
I (50506) chip[DL]: NVS set: chip-counters/reboot-count = 1 (0x1)
I (50506) chip[DL]: NVS set: chip-counters/total-hours = 0 (0x0)
I (50516) chip[DL]: NVS set: chip-config/unique-id = "15F41C2D78321EE4"
                                                                                                                  I (50516) chip[DL]: Real time clock set to 946684800 (0100/00/01 00:00:00 UTC)
I (50516) chip[CTL]: Setting attestation nonce to random value
I (50516) chip[CTL]: Setting CSR nonce to random value
I (50516) chip[CTL]: Setting attestation nonce to random value
I (50516) chip[CTL]: Setting CSR nonce to random value
I (50526) chip[TS]: Last Known Good Time: [unknown]
I (50526) chip[TS]: Setting Last Known Good Time to firmware build time 2023-10-14T01:16:48
> I (50536) chip[IN]: CASE Server enabling CASE session setups
I (50536) chip[CTL]: Couldn't get ExampleOpCredsCAKey from storage: Error CHIP:0x000000A0
I (50606) chip[CTL]: Couldn't get ExampleOpCredsICAKey from storage: Error CHIP:0x000000A0
I (50726) chip[CTL]: Generating RCAC
I (50796) chip[CTL]: Generating ICAC
I (50866) chip[CTL]: Generating NOC
I (50946) chip[FP]: Validating NOC chain
I (51396) chip[FP]: NOC chain validation successful
I (51396) chip[FP]: Added new fabric at index: 0x1
I (51396) chip[FP]: Assigned compressed fabric ID: 0xCDBB6B8D21A51A37, node ID: 0x000000000001B669
I (51396) chip[TS]: Last Known Good Time: 2023-10-14T01:16:48
I (51396) chip[TS]: New proposed Last Known Good Time: 2021-01-01T00:00:00
I (51396) chip[TS]: Retaining current Last Known Good Time
I (51406) chip[FP]: Metadata for Fabric 0x1 persisted to storage.
I (51416) chip[TS]: Committing Last Known Good Time to storage: 2023-10-14T01:16:48
I (51436) chip[CTL]: Joined the fabric at index 1. Fabric ID is 0x0000000000000001 (Compressed Fabric ID: CDBB6B8D21A51A37)
I (51436) chip[DIS]: Updating services using commissioning mode 0
I (51436) chip[DIS]: CHIP minimal mDNS started advertising.
I (51436) chip[DIS]: Advertise operational node CDBB6B8D21A51A37-000000000001B669
I (51436) chip[DIS]: CHIP minimal mDNS configured as 'Operational device'; instance name: CDBB6B8D21A51A37-000000000001B669.
I (51436) chip[DIS]: mDNS service published: _matter._tcp
I (51446) chip[DIS]: Advertise commission parameter vendorID=65521 productID=32768 discriminator=0000/00 cm=0 cp=0
I (51446) chip[DIS]: CHIP minimal mDNS configured as 'Commissioner device'; instance name: D1D3904DFF2C8600.
I (51446) chip[DIS]: mDNS service published: _matterd._udp
E (51756) BLE_INIT: controller init failed


assert failed: ble_svc_gap_init ble_svc_gap.c:333 (rc == 0)


Backtrace: 0x40375936:0x3fced1c0 0x4037ff21:0x3fced1e0 0x40386c2d:0x3fced200 0x420ae28f:0x3fced320 0x42073ec7:0x3fced340 0x420745eb:0x3fced360 0x42074736:0x3fced3c0 0x42073045:0x3fced3e0 0x42073395:0x3fced400 0x420733c9:0x3fced470 0x4038091e:0x3fced490
--- 0x40375936: panic_abort at /home/farhana/idf/idfv5.2.3/esp/v5.2.3/esp-idf/components/esp_system/panic.c:466
0x4037ff21: esp_system_abort at /home/farhana/idf/idfv5.2.3/esp/v5.2.3/esp-idf/components/esp_system/port/esp_system_chip.c:93
0x40386c2d: __assert_func at /home/farhana/idf/idfv5.2.3/esp/v5.2.3/esp-idf/components/newlib/assert.c:81
0x420ae28f: ble_svc_gap_init at /home/farhana/idf/idfv5.2.3/esp/v5.2.3/esp-idf/components/bt/host/nimble/nimble/nimble/host/services/gap/src/ble_svc_gap.c:333 (discriminator 1)
0x42073ec7: chip::DeviceLayer::Internal::BLEManagerImpl::InitESPBleLayer() at /home/farhana/github/matter-gw/build/esp-idf/chip/../../../../../idf/idfv5.2.3/.espressif/esp-matter/connectedhomeip/connectedhomeip/config/esp32/third_party/connectedhomeip/src/platform/ESP32/nimble/BLEManagerImpl.cpp:939
0x420745eb: chip::DeviceLayer::Internal::BLEManagerImpl::DriveBLEState() at /home/farhana/github/matter-gw/build/esp-idf/chip/../../../../../idf/idfv5.2.3/.espressif/esp-matter/connectedhomeip/connectedhomeip/config/esp32/third_party/connectedhomeip/src/platform/ESP32/nimble/BLEManagerImpl.cpp:743
0x42074736: chip::DeviceLayer::Internal::BLEManagerImpl::DriveBLEState(int) at /home/farhana/github/matter-gw/build/esp-idf/chip/../../../../../idf/idfv5.2.3/.espressif/esp-matter/connectedhomeip/connectedhomeip/config/esp32/third_party/connectedhomeip/src/platform/ESP32/nimble/BLEManagerImpl.cpp:1743
0x42073045: chip::DeviceLayer::Internal::GenericPlatformManagerImpl<chip::DeviceLayer::PlatformManagerImpl>::_DispatchEvent(chip::DeviceLayer::ChipDeviceEvent const*) at /home/farhana/github/matter-gw/build/esp-idf/chip/../../../../../idf/idfv5.2.3/.espressif/esp-matter/connectedhomeip/connectedhomeip/config/esp32/third_party/connectedhomeip/src/include/platform/internal/GenericPlatformManagerImpl.ipp:304
0x42073395: chip::DeviceLayer::PlatformManager::DispatchEvent(chip::DeviceLayer::ChipDeviceEvent const*) at /home/farhana/github/matter-gw/build/esp-idf/chip/../../../../../idf/idfv5.2.3/.espressif/esp-matter/connectedhomeip/connectedhomeip/config/esp32/third_party/connectedhomeip/src/include/platform/PlatformManager.h:503
 (inlined by) chip::DeviceLayer::Internal::GenericPlatformManagerImpl_FreeRTOS<chip::DeviceLayer::PlatformManagerImpl>::_RunEventLoop() at /home/farhana/github/matter-gw/build/esp-idf/chip/../../../../../idf/idfv5.2.3/.espressif/esp-matter/connectedhomeip/connectedhomeip/config/esp32/third_party/connectedhomeip/src/include/platform/internal/GenericPlatformManagerImpl_FreeRTOS.ipp:257
0x420733c9: chip::DeviceLayer::PlatformManager::RunEventLoop() at /home/farhana/github/matter-gw/build/esp-idf/chip/../../../../../idf/idfv5.2.3/.espressif/esp-matter/connectedhomeip/connectedhomeip/config/esp32/third_party/connectedhomeip/src/include/platform/PlatformManager.h:403
 (inlined by) chip::DeviceLayer::Internal::GenericPlatformManagerImpl_FreeRTOS<chip::DeviceLayer::PlatformManagerImpl>::EventLoopTaskMain(void*) at /home/farhana/github/matter-gw/build/esp-idf/chip/../../../../../idf/idfv5.2.3/.espressif/esp-matter/connectedhomeip/connectedhomeip/config/esp32/third_party/connectedhomeip/src/include/platform/internal/GenericPlatformManagerImpl_FreeRTOS.ipp:280
0x4038091e: vPortTaskWrapper at /home/farhana/idf/idfv5.2.3/esp/v5.2.3/esp-idf/components/freertos/FreeRTOS-Kernel/portable/xtensa/port.c:134

• Could this be due to an issue with NimBLE stack configuration when keeping BLE active after provisioning?
• Are there additional BLE-related configs that need to be adjusted when enabling CONFIG_WIFI_PROV_KEEP_BLE_ON_AFTER_PROV?
• Any recommendations on debugging or resolving this initialization failure?

[shripad621git]

@iamiha, along with CONFIG_WIFI_PROV_KEEP_BLE_ON_AFTER_PROV=y option enabled please call the ble_deinit api after successful provisioning log. You can refer to the ble_deinit apis called here.
The above crash occurs since the ble stack is already initialized and locked by the provisioning code. To use the matter initialization with ble provisioning, you need to deinit the nimble stack.
For e.g.:

case WIFI_PROV_CRED_SUCCESS:
{
    ESP_LOGI(TAG, "Provisioning successful");
    if (!ble_hs_is_enabled())
    {
         ESP_LOGI("DeviceLayer", "BLE already deinited");
    }
    esp_err_t err = nimble_port_stop();
    if (err != ESP_OK)
    {
         ESP_LOGE(TAG, "nimble port stop failed , err:%d \n", err);
    }

    err = nimble_port_deinit();
    if (err != ESP_OK)
    {
        ESP_LOGE(TAG, "nimble port deinit failed  , err:%d \n", err);
    }
 }

[shripad621git]

@iamiha , any updates?

[iamiha]

@shripad621git ,

Thankyou, the issue is resolved now