Closed sheldon123z closed 4 years ago
Hi @sheldon123z
Sorry for the inconvenience caused.
Currently please enable the "Bluetooth modem sleep" in the bluetooth controller menuconfig, this will fix this issue. And we have fixed this issue internally, the changes will be synchronized to Github very soon.
Another option is to cherry-pick this commit from master, it will also fix this issue.
Thanks and Regards
Hi @Campou ,
Thank you very much, that works!
I also have a quick question, since I am new to BLE mesh, I am still learning the stack. I found the examples seem not able to be provisioned by other provisioners except for the phone and the example provisioner, like an embedded Linux provisioner Raspberry Pi3 B+ using BlueZ, and the Tmall genie, which also uses Bluetooth mesh as the communication protocol. Both of them are not working with the examples. What adjustment should I do to handle this?
Thanks!
Environment
Development Kit: [ESP32-DevKitC]
Kit version (for WroverKit/PicoKit/DevKitC): [v4]
Module or chip used: [ESP32-WROOM-32D]
IDF version (run
git describe --tags
to find it): v4.0Build System: [idf.py]
Compiler version (run
xtensa-esp32-elf-gcc --version
to find it): // 1.22.0-80-g6c4433aOperating System: [Windows]
(Windows only) environment type: [ESP Command Promp].
Using an IDE?: [No]
Power Supply: [USB]
Problem Description
Hi, I am using ESP32 DevKitC to test the ble_mesh_server/client examples, everything looks like going well after I flashed the example into the board. However, I couldn't use my phone to detect the board in either the nRF Mesh application or the ESP-BLE-Prov application. When I use the cmd to monitor the board status, I found the board is rebooting all the time, and the log information is like below:
Debug Logs
Any thought about my problem?