@sjg

We appreciate feedback, even tough one, to be able make things better. The feedback we have already received since the launch has push us to make corrective actions like my colleague mentioned above, unfortunately it has taken some time to implement as we are trying to improve the examples, documentations and the flow for the better. Now we are getting closer to make publish those development experience improvements. Once those changes are available, you, and other developers, will see it is huge leap to the right direction. 

Your idea of doing usage testing is a good one, and we have done that after the launch, but I think we need to continue on that path more systematically.

And as many stated above, if you have still questions open, we are here and in the support portal to help you further.

Sincerely yours, 

.sami.

Hi,

I wanted to check if you are using the latest firmware (SDK v1.1.2-184)?

The affect of scanning for other device causing a buffer overflow, should not definitely happen, but could you eliminate that possibility by performing the tests in a more quiet environment?

Thanks,

Sami

Hi AC,

Unfortunately our BT121 only supports the SPP profile in classic mode, and we don't have A2DP support. But besides that the classic (SPP) and BLE can be ran simultaneously, up to 1 BR/EDR+7 BLE connections.

Hopefully this clarifies. 

Sami

This post was answered privately. 

Hi,

Custom profiles are not part of the qualification/declaration process. If your device implements one of the adopted profiles, like HID profile or Health Thermometer profile, and you want to market the product as compatible with those adopted profiles then you have to go through the Profile Subsystem testing/declaring, but custom profiles do not need to be tested or declared. 

That said, you still need to declare the physical end-product by referring to our tested components (RF-Phy, LL, Host Stack) and that will come with a fee of $4000/$8000 depending on your SIG membership status. 

Regards,

Sami

Hi Arnold,

Sorry for the lengthy wait for the reply, we have guys looking in to the question and should be with you shortly. 

Regards,

Sami

On March 14th 2017, Silicon Labs released new SoCs to widen its Wireless Gecko portfolio with the new EFR32xG12 devices supporting Bluetooth 5 features, with larger memory options, enhanced cryptography acceleration support for multiprotocol to name a few of the new features. The EFR32xG12 devices are available for order. Please check the device specs from the press release and the product pages.

http://news.silabs.com/press-release/corporate-news/new-wireless-gecko-socs-help-developers-tackle-multiprotocol-iot-design

http://www.silabs.com/products/wireless/wireless-gecko-iot-connectivity-portfolio

Together with new devices we released new version of the Bluetooth SDK v2.3.0.0, as part of the Gecko Suite SDK v1.0.0.0. The SDK added support to newly released products, but also added features like:

* Switched multiprotocol between Bluetooth and zigbee
* Bluetooth 5.0: 2M PHY support for EFR32BG12/MG12
* Bluetooth 5.0: Advertisement sets support
* Bluetooth 4.2: 250B ATT MTU and 128B link layer packet support
* EFR32BG12MG12 hardware support
* Gecko Bootloader support
* GCC compiler support (Beta)

Get your hands on the new SDK by downloading or upgrading to the latest Simplicity Studio v4 and using the package manager to download the Bluetooth Smart SDKv2.3.0.0.

http://www.silabs.com/products/development-tools/software/bluetooth-smart-software

We created a FAQ about the software release, please check if your question has been already answered or post a question as a comment:

http://community.silabs.com/t5/Bluetooth-Wi-Fi/Bluetooth-SDK-2-3-0-FAQ/m-p/192360

Hi Erik,

Thanks for your feedback, we will use the Silicon Labs template for all the Wireless modules materials for all new releases, also including the just released BGM111. However, we do not have plans currently to change the already existing Bluegiga documentation to Silicon Labs templates.

.sami.

Hi Melanie,

I think you'll find the Knowledgebase article below just what you need to get started.

http://community.silabs.com/t5/Bluetooth-Wi-Fi-Knowledge-Base/Programming-the-BT121/ta-p/173579

Let us know if you have questions.

Regards,

Sami

Hi, 

The piconet topology implementation is on the ACL level  and is the same on both, RFCOMM and HID.  

If there are multiple logical links on top of an ACL, then all logical links need to have the same role. Does it work if you do the role switch on the RFCOMM?

Regards,

Sami