There are ~100 Knowledge Base Articles (KBAs) in the Bluetooth section of the forum on a diverse range of sub-topics. We know they are sometimes challenging to find, especially when you don't know what exists (and therefore you don't search for it).
To simplify this task we have created a Bluetooth Knowledge Base Article List which has all the KBAs divided into sub-topics. This list only contains KBAs which are meaningful today, so you won't find anything related with SDK 1.x, BGScript or anything else which has been deprecated. Most of those KBAs are still here but their title has been marked with a "[Deprecated]" prefix and a Note pointing for a more updated KBA where applicable. This is to avoid confusing our customers into reading material which is no longer applicable.
It would be great to hear if you find this list useful and any thoughts you might have on how to improve it.
Additionally please check out our Bluetooth training page -> https://www.silabs.com/support/training/bluetooth
Some mobile devices may have connection problems after updating BGX13 to 1.2.2045.0.
SIlicon Labs recently updated the firmware for BGX13 to version 1.2.2045.0.
This version has some feature improvements, but these improvements required that we make some changes to the GATT attributes. Because of this, some phones may experience connection problems after the BGX13 firmware is updated.
Some mobile devices remember the GATT attributes of devices that have been paired or bonded in the past. When the GATT attributes are changed after the 1.2 update, the mobile device cached GATT information is misaligned between the two devices. This causes invalid handles to bluetooth services and characteristics. As a result attempts to connect to the device may no longer work, or some feature may not work such as sending or receiving data between a phone and the specific BGX for which this invalid bonding exists.
Invalid/misaligned bonding data must be cleared and then the bond should be re-established using the correct GATT attributes.
The problem may manifest in the following ways.
On iOS, you may see a message on the device details screen reading "SOME_OTHER_MODE".
On either Android or iOS, you may also see a password dialog appear at an inappropriate time or when no password has been set. You might also see that data is not being sent from the phone to the BGX or from the BGX to the phone.
To solve this problem, perform the following operations:
1. Clarify to yourself what the specific issue is.
2. Apply basic troubleshooting:
3. Consult the datasheets and reference manuals. Sources include:
4. Search to see if someone has asked the same question already.
5. Include the relevant parts of your development setup in the problem description. Examples include:
6. Include steps to reproduce the problem or specific conditions the problem occurs in.
7. Be patient and avoid making duplicates of your question.
For general community usage please refer to the Silicon Labs Community Guidelines.
In the soc-empty example there is the code below.
Is there a recommended way to determine if the connection is being made from an apple or android device so that the connection interval can be changed to the faster times if it is an android connection? Or does it have to be hard coded so that either could run?
/* request connection parameter update.
* conn.interval min 20ms, max 40ms, slave latency 4 intervals,
* supervision timeout 2 seconds
* (These should be compliant with Apple Bluetooth Accessory Design Guidelines) */
// gecko_cmd_le_connection_set_parameters(_conn_handle, 16, 32, 4, 200);
I am trying to compile and upload the SOC-Thunderboard example onto Thunderboard BG22 board. The example compiles but does not work. I mean there is even no PRINTF output to the external terminal console. I cannot even debug it - all debug controls in Simplicity Studio are grayed out. I did not change anything in the example code. I use SDK 7.2.13 with all currently available upgrades.
It seems that the problem is in the debug adapter. I can download the pre-compiled SOC-Thunderboard app and it works fine - I can see PRINTF outputs ad connect to the device. However, that is what I see in the Launcher mode. "No adapter firmware directory specified" message does not appear with my other boards. Is it OK?
Also, when I attempt to download my compiled code I see the following:
After clicking on the link firmware download becomes available, but the app does not work. Please advise how to fix that.
The energy profiler seems to work with the binary file from the EMPTY SoC project but not with my code.
My code is actually working as I am able to pair and get indications and notifications.
What may I be doing wrong?
I`m using WSTK connected to Simplicity Studio, I`m trying to download Software examples from Flex 22.214.171.124 RAIL : Light and RAIL : Switch without success ,the error I got is,please advise.
I would like to use the BGM210P product to a new project in our company. This module contains a base firmware when we get it from the distributor?
I would use these modules in VSP(virtual serial port) mode as You call NCP mode, and I wouldn't program them with debugger just from my host processor(STM32) via UART.
So if I would follow this way could You tell me, that the module contains any FW or not?
Do I have to program the BGAPI and stack to the modules, or not? Does it contains the satck and BGAPI, and a default GATT?
I make a project of ble in the simplicity, like the picture below, and why i can't enter the 'gecko_evt_gatt_server_user_read_request_id ' and 'gecko_evt_gatt_server_user_write_request_id' when i read or write the charactistic from the 'EFR Connect' app?
I using BGM13p22 module , i need to send data from client to server . How to form client and server communication and i need to get RSSI values of client in sever side.
I am trying to send/receive any data using VendorModel with Android Phone application as a provisioner.
As I understand - there is no way to bind AppKey through Phone application. So I cannot send/receive any data through VendorModel, right?
we are designing a medical device and plan to use the Silab BRD4181A in it.
This design "decision" raises several questions:
Hi, I've seen that BG22 also has the RFSense wake-on radio feature.
Is the actual BLE stack for BG22 supporting this feature, so a device could use it for comissioning?