- Silicon Labs Community
- Welcome and Announcements
- Silicon Labs Knowledge Base
- 8-bit MCU
- 32-bit MCU
- Bluetooth / Wi-Fi
- Other Products Category
- Optical/RH/Temp Sensor
- Other Products
- Hardware and Software Tools
- Simplicity Studio and Software
- General Discussions and Suggestions
- Chinese Forum
- Software Libraries
- Development Kits
- Reference Designs
- Third Party Tools
- White Papers
- Official Blog of Silicon Labs
- Chinese Blog
03-15-2017 02:59 AM - edited 04-12-2017 12:42 AM
This thread is dedicated to questions about the Bluetooth SDK 2.3.0 (released March 2017). The first post (the one that you are reading right now) is continuously updated so that it contains the latest status.
If your question is not specific to this BLE SDK version (2.3.0) then consider starting a new topic instead of replying to this topic.
NOTE: patch version 2.3.1 has been released, it replaces the 2.3.0.
Bluetooth SDK 2.3.0 FAQ
What's new in SDK 2.3.0?
New features include:
* Support for EFR32BG12 and EFR32MG12 product families
* Implementation for Bluetooth 5 2M PHY feature added. (EFR32BG12 and EFR32MG12 parts)
* Switched multiprotocol support
* GCC compiler support (Beta level)
* Bluetooth 5 Advertisement Sets
This is not a complete list. For more details, see the release notes.
For more information on the switched multiprotocol, see
Where is the 2.3.0 SDK located, I can't find it?
The directory structure has changed starting from v2.3.0. Bluetooth SDK is now found under:
BGScript and NCP examples are found in:
The libraries are in:
In previous versions, the SDK was in:
GCC related questions
Note that GCC support is Beta level in SDK v2.3.0.
Is OTA supported in the 2.3.0 release with GCC?
Yes, OTA is supported. See following thread:
* BGScript support will be discontinued in the next major release
* BGscript is not supported with EFR32MG12,EFR32BG12 products (even in 2.3.0)
* most of the HW related commands / events have been marked as deprecated
For more details, see the release notes.
Bad DC/DC configuration can cause unexpected resets when using maximum TX power (which is the default setting in most examples). => FIXED in SDK 2.3.1.
- Temporary workaround: lower the TX power with command gecko_cmd_system_set_tx_power.
Update history, starting from the latest change:
* Apri 12 - Added note about 2.3.1 patch release that is now available
* April 3 - Added known issues - unexpected resets due to bad DC/DC config
* March 16 - Added note about deprecated features
03-20-2017 07:13 AM
Please clarify question about Bluetooth 5 support and SDK 2.3.0:
Bluetooth 5 support is available just for new devices like EFR32BG12 and EFR32MG12?
Old devices like EFR32MG1P1 or EFR32BG1 ( Thunderboard sense and react) can support Bluetooth 5 Advertisement Sets feature ?
Any Bluetooth 5 application development guide ?
03-20-2017 07:47 AM
the BT5 2M PHY is supported only on the new EFR32xG12 devices.
The older EFR32MG/BG based products can support Advertisement sets and scan event reporting. Same applies to modules based on EFR32BG: BGM111, BGM113, BGM121.
There is no BT5 application development guide at the moment. A knowledgebase article about how to use the BT5 advertising sets should be avaiable soon.
03-22-2017 05:26 PM
How and where do I find it? Is there a download? I have tried updating Simplicity Studio but I am still stuck with 2.1.1. I was going to download the Simplicity Studio installation again but it is the same version as I already have.
03-23-2017 12:15 AM
How and where do I find it? Is there a download?
There is no separate download, the new SDK is installed using Studio package manager. Try locating it under the SDKs, see screenshot below:
The version numbering can be a bit confusing: you need to install Gecko SDK Suite 1.0.0 which includes the latest BLE SDK v2.3.0. The wireless SDKs are organized like this because they share some common components like the emlib/emdrv libraries and Gecko bootloader.
03-27-2017 01:08 PM
That's your own choice, you can go with BGScript but that will lock you to the existing SDK release. If you want to use features which will be added in the next releases you'd have to migrate your app to C.