I plan to build ble mesh networks using esp32s3.
I ran successfully the samples based on bluedroid stack and they worked OK.
I was able to provision node using nRF Mesh mobile app.
Then I understood that the Nimble stacks uses much less resources so I started to example apps under Nimble
The blemesh sample tells in README that "To test this demo, any BLE mesh provisioner app can be used"
But I am not able to provision with any app! The nRF Mesh app worked perfectly with bluedroid examples but not at all with Nimble blemesh example. The Scan does not see unprovisioned node. It seems that the node is not really beaconing.
The log shows:
Code: Untitled.txt Select all
I (392) main_task: Calling app_main()
I (412) BLE_INIT: BT controller compile version [963cad4]
I (412) phy_init: phy_version 601,98f2a71,Jun 29 2023,09:58:12
I (452) BLE_INIT: Bluetooth MAC: dc:da:0c:57:a7:c2
I (452) NimBLE: GAP procedure initiated: stop advertising.
I (462) NimBLE_MESH: Bluetooth initialized
I (512) NimBLE_MESH: Mesh initialized
I (512) main_task: Returned from app_main()In the README example log, it should continue with something like:
Code: Untitled.txt Select all
I (895) NimBLE_MESH: Mesh initialized
GAP procedure initiated: advertise; disc_mode=0 adv_channel_map=0 own_addr_type=1 adv_filter_policy=0 adv_itvl_min=160 adv_itvl_max=160
GAP procedure initiated: stop advertising.
GAP procedure initiated: advertise; disc_mode=2 adv_channel_map=0 own_addr_type=1 adv_filter_policy=0 adv_itvl_min=160 adv_itvl_max=240
I cannot find any parameter in menuconfig that could impact on this.
Any suggestions?