Bluetooth support for ESP32 IDF 2.0 Release

[Ritesh]

Hi Espressif Systems Developer,

We have started to work on ESP32 chip since last one year and we have also developed different different application based on ESP32 Development Board and Our Custom Boards.

We are right now using ESP32 IDF 2.0 Official RTOS SDK for our development purpose and it works fine till now as per our requirement.

But, Now we have requirement to start Bluetooth as well for our project requirement and I have seen that Bluetooth Classic and BLE support is keep on changing regularly every day.

So, Would you please suggest that can I go for Bluetooth support with existing ESP32 IDF 2.0 RTOS SDK?

[Ritesh]

Hi Espressif Developer,

Would you please provide feedback or response regarding requirement which I have raised for Bluetooth Support?

Please let me know if need any information from my side.

[WiFive]

Suggest you use 3.0 when it comes out within 1-2 weeks

[Ritesh]

Suggest you use 3.0 when it comes out within 1-2 weeks

Hi,

Thanks for quick response.

But, We have already started application development on ESP32 2.0 IDF SDK and we just need Bluetooth support into our product.

So that it will be little bit harder to move from ESP32 2.0 SDK to 3.0 as we need to validate each and every feature again with 3.0 SDK as well if we will move with this.

Can it be possible to apply relevant patches for Bluetooth into existing 2.0 ESP32 IDF SDK? Or it's difficult to do that?

Please provide you suggestions for this.

[WiFive]

I think it is too hard since bt and wifi are not all open source. And there are so many changes and fixes since 2.0, over 1800 commits.

[Ritesh]

I think it is too hard since bt and wifi are not all open source. And there are so many changes and fixes since 2.0, over 1800 commits.

Hi,

Thanks for quick response.

So, It means we need to upgrade ESP32 IDF RTOS SDK from 2.0 to 3.0 if we want to use Bluetooth feature for my application development.

Also, Can you please confirm or make sure with ESP32 SDK Developer that will it be completely released full features of Bluetooth into ESP32 IDF 3.0 RTOS SDK? If yes then we will take decision to move ahead with ESP32 IDF 3.0 SDK.

Please confirm that stuff from your side if possible and provide me update regarding that.

[WiFive]

No there will be more features in 3.1 but much easier to go from 3.0 to 3.1.

[Ritesh]

No there will be more features in 3.1 but much easier to go from 3.0 to 3.1.

Hi,

Thanks for update.

So, It means all basic features regarding Bluetooth will be covered into ESP32 IDF 3.0 SDK Release. correct?

Would you please provide tentative schedule for ESP32 IDF 3.0 Official Stable RTOS SDK Release?

[ESP_Angus]

Hi Ritesh,

At minimum, we strongly recommend updating to the V2.1.1 release when it becomes available. This is a point release to V2.0 so it is mostly backwards compatible. There is a small list of incompatible changes here:
https://github.com/espressif/esp-idf/releases/tag/v2.1

You can get the updated 2.1 branch which will become V2.1.1 here:
https://github.com/espressif/esp-idf/tree/release/v2.1

(You can update to this branch now, and then update to the V2.1.1 release when it becomes available shortly - the additional changes will be minor.)

There are a number of important fixes in the release/v2.1 branch for V2.1.1, including Bluetooth security fixes (a "BlueBorne" vulnerability ​CVE-2017-0785) and WiFi security fixes ("KRACK" aka CERT VU#228519).

These point releases are the supported way to update V2.0 to get bug fixes, without requiring major changes to your firmware.

If you find that V2.1.1 does not contain enough Bluetooth functionality for your project requirements, you can look at updating all the way to V3.0 when it is available.

[jumjum123]

@ESP_ANGUS, just read about Release V2.1.1 and now I'm confused.
In my understanding next release would be V3.0 and first plan was to get it done first week of Oct.
This did not work, and there is additional delay because of Chinese national holiday.
In my understanding this means, we would have been close to V3.0 this or next month.

With a V2.1.1 release comin up, V3.0 release could be delayed for some more time.
Is there any release plan, including expected time range for release, that you can tell us ?
thanks in advance