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.
As you may have noticed, a new Bluetooth SDK (2.11.0) was recently released as part of the Gecko SDK Suite v2.5.0. This post highlights some of the developer experience (DX) improvements in this release.
One of the changes introduced in this SDK is refactoring of the soc-empty example. The example code itself has not changed much, but the project has been slightly restructured. The target here is to:
decouple the application code (app.c) from the main.c
improve portability across SDK versions (reduce migration effort)
enable using same application code in multiple radio boards or even custom boards (same app.c works for many targets)
If you are currently using an older SDK version (between 2.6.x and 2.10.x), no need to worry - the new soc-empty is still quite similar, there are no drastic changes.
Some additional improvements that will help you get started:
printf() debugging is supported out-of-the-box, all the necessary files are pulled into the project automatically
printf() is disabled by default, can be turned on simply by changing one #define in app.h
More details are found in the KB article linked above.
If you have any questions or comments about the new soc-empty example, feel free to post comments in this thread!
I'm currently working on implementing Bluetooth mesh features for BGM13P chips. We want to provision and access the mesh nodes from linux embedded side. Unfortunatly a Bluetooth mesh library (which was described in the Mesh webinar) is not available. My starting point is your "mesh light node" sample which works fine with your demo app. Porting this knowledge to linux (based on Bluez 5.50 as an alternative) I currently face some issue in the provisioning phase. In your documentation refering the light sample you explain that only an android client sdk is currently available. Could you also give some advice/requirement that is needed to run provisioning successful? Do you also offer or has some plans to support linux as well too? If so I will now follow up with some more detailled error description. It would be great to access your devices from linux as well. I think many people are really interested in that! I'm also more interested in having a SiliconLabs mesh library which is able to run on ARM and x86.
Under linux I build Bluez 5.50 with mesh support to have access to the commandline tool (meshctl). Running meshctl I follow the provisioning process. After connecting to the the development board and exchanging some piece of data, the provisioning failed.
Running meshctl from Bluez 5.50 (build with option --enable-mesh)
$ meshctl
[meshctl]# discover-unprovisioned on
SetDiscoveryFilter success
Discovery started
Adapter property changed
[CHG] Controller 6D:10:51:73:84:E3 Discovering: yes
Mesh Provisioning Service (00001827-0000-1000-8000-00805f9b34fb)
Device UUID: 53696c6162734465762dc6838c570b00
OOB: 0000
[NEW] Device 00:0B:57:8C:83:C6 light node 83:c6
[meshctl]# provision 53696c6162734465762dc6838c570b00
Trying to connect Device 00:0B:57:8C:83:C6 light node 83:c6
Adapter property changed
[CHG] Controller 6D:10:51:73:84:E3 Discovering: no
Connection successful
Services resolved yes
Found matching char: path /org/bluez/hci0/dev_00_0B_57_8C_83_C6/service0009/char000a, uuid 00002adb-0000-1000-8000-00805f9b34fb
Found matching char: path /org/bluez/hci0/dev_00_0B_57_8C_83_C6/service0009/char000c, uuid 00002adc-0000-1000-8000-00805f9b34fb
Start notification on /org/bluez/hci0/dev_00_0B_57_8C_83_C6/service0009/char000c
Characteristic property changed /org/bluez/hci0/dev_00_0B_57_8C_83_C6/service0009/char000c
AcquireNotify success: fd 7 MTU 69
Notify for Mesh Provisioning Out Data started
Open-Node: 0x2f0bce0
Open-Prov: 0x2f21310
Open-Prov: proxy 0x2f1c390
Initiated provisioning
Characteristic property changed /org/bluez/hci0/dev_00_0B_57_8C_83_C6/service0009/char000a
AcquireWrite success: fd 8 MTU 69
GATT-TX: 03 00 10
GATT-RX: 03 01 01 00 01 00 00 00 00 00 00 00 00
Got provisioning data (12 bytes)
01 01 00 01 00 00 00 00 00 00 00 00
Provisioning failed
Attempting to disconnect from 00:0B:57:8C:83:C6
Characteristic property changed /org/bluez/hci0/dev_00_0B_57_8C_83_C6/service0009/char000c
Write closed
Services resolved no
Characteristic property changed /org/bluez/hci0/dev_00_0B_57_8C_83_C6/service0009/char000a
The development board with BGM13P shows following state changes on its display
1) unprovisioned
2) provisioning - connected
3) prov failed
4) unprovisioned
I have a project where two BLE modules exchange data. The slave should constantly send data and the master (Central) should read the data automatically after starting. I miss in the command set of the BGX the option to connect e.g. the last slave automatically again.
At the moment I connect via "scan" and later via "con 1" which is not very satisfying. Alternatively I wanted to try the assignment of a hardware pin: GPIO0: ufu 0 scan and GPIO1: ufu 0 con 1 each with "Function Trigger" Rising Edge. But that didn't work.
I tried a lot of things - but didn't find the right solution.
I would be very grateful for a suggestion on how the connection can be re-established automatically after a first contact. (or a certain address, e.g. BGX-3425)
(I have two BGX13P Dev Boards and several BGX13P to try out.)
I really like the ease of use of the Bluetooth Xpress BGX13P preprogrammed device for ease of use but don't have the background with the phone app development and wondered if the MIT App Inventor program can be used to ease that barrier to entry. Can the MIT app inventor development environment write android apps to communicate with the BGX13P now or in the future? It is currently in use to support the Bluetooth classic serial port profile (SPP) that is not in BLE now. I'd like to use the BGX13P like the HC06 non-FCC certified module shown in this video. This would make things really easy on the master/phone side. Thanks for your time.
I've been trying to update an STM32 firmware. I am able to send a file using the SPP example. I have a BLED112 connected with my pc (cygwin terminal).
The other MCU have a Bootloader that use Ymodem to transfer files. I have connected the UART of my board with the UART of the STM32 MCU). I can send the file, and it's properly sent but my firmware is not updated. I assume that it comes from the Ymodem protocol that does not recognise the data that I transmit.
1) At this point I want to send Ymodem Packets over BLE (with CRC) but the size of the data exchanged by this protocol is about 1k, and with Bluetooth I can't obviously send 1k by 1k packets. So how can i do that ?
2) Is there a better way of doing this firmware update over BLE, knowing I can modify the Bootloader firmware ? An other protocol that better match with BLE ?
we are currently working on a DMP project using 2.4 GHz IEEE 180.15.4 and BLE on a EFR32MG13P732.
After upgrading to SDK 2.6.0.0, RAIL 2.7.0 Build 24 [BLE Gecko v2.12-0 Build 69], we have issues to establish BLE connections. The fast majority of connection attempts fail, ofthen this causes the advertisements to stop. Many of these connection attempts do not lead to any additional Link layer aktivity.
This problem does NOT occur on MG12 (BRD4162A).
The problem also does not occur on RAIL v2.6-2 Build 2. It is suffiicient to downgrade the file librail_multiprotocol_efr32xg13_iar_release.a to version 2.6.2 to solve the issue, not changing any of the other RAIL files. We can also reproduce this behavoiour with Demo software on Silabs Eval Boards, not using our own hardware or firmware. Also on Silabs Eval hardware, downgrading librail_multiprotocol_efr32xg13_iar_release.a solves the issue.
Steps to reproduce:
Open Simplicity Studio 4.2
Hardware: BRD4168A Rev A01 (EFR32MG13P732HG)
Create a new App Builder project using SDK 2.6.0.0
Choose Bluetooth SDK 2.12.0.0
Create SOC - Empty - RAIL - DMP
Select an MG13 part such as BRD4168A
Compile and flash the device
Download a BLE Scanner app for Android
Try to connect
see many failed attempts
Downgrade RAIL lib
Connection attemtps will succeed
Please let us now whether you can re-create this and how we can fix this without downgrading.
I had a problem on the section 3.6, reading and writing the Local Database, when I follow the example to the letter, it said that cmuClock_ADC0 is not declared in app.c
I'm currently using Bluetooth SDK 2.12, and program using the template soc-empty.
Hello! I am trying to connect my mobile phone to the module WT32-E. I used the command "inquiry" and the module found the phone, but when I try to connect using the command " call {MAC address} {target} {RFCOMM} " , it returns error: NO CARRIER 0 ERROR 1b04 SDC_NO_RESPONSE_DATA . How can I solve this? I think I write the wrong target number but not sure. Please help me !
I use the BLED112 with firmware version ble-1.6.0-140 and the dongle does not transmit to the COM port every advertisement packets my devices send.
I start scanning using GAP Discover Mode gap_discover_observation (cmd_gap_discover(2)) and receive advertisement packets every 500 ms as expected, but all at once I don't receive any more advertisement packets for seconds - sometimes more than 30s, and suddenly everything works again as before.
I am sure that my device is sending an advertisement packet every 500 ms because I measured / assert this with other BLE hardware, and I can connect the device even during this pause period.
What can it be? Is there any configuration parameter that I need to set?
Hi,
I have a hard time understanding when exactly data transfer occurs when calling stack functions (I'm using BGM13P modules). Suppose, we have an established connection between two devices (M and S) with connection interval = 100 ms. If I understand correctly, stack will wake both devices from EM2 every 100 ms without any need of software timer. If I call function gecko_cmd_gatt_read_characteristic_value() on Master after wake up, will stack send read command during this connection event or will it wait another 100 ms to send it in next connection event? And how much time do I have to call the command before Master sends its Data PDU upon waking up? The same goes for the Slave: will Slave respond to this command during this connection event or will it wait for the next one?
Target device is made up of Mighty Gecko Radio board + Giant Gecko Master board and Tiny Gecko Slave board.
The Giant Gecko and Tiny Gecko is connected to Mighty Gecko Radio board over UART interface. The Bluetooth client communicated to the target device via the target radio board
Based on above connection. I want to grab the debug console of all three target device from my bluetooth client. Kindly guide me how to achieve this.
we use a bluetooth SDK 2.11 running a ncp-empty-target application connected over uart to a linux uart with 115200 Baud 8,N,1.
If we start scanning with command cmd_le_gap_start_discovery for LE Coded PHY devices.
As BLE chip we use the BGM13S32.
The princip of working is this:
start discovery
scan for devices
stop discovery with cmd_le_gap_end_procedure
make a connection
transfer data needs about 1-2 sec.
close the connectiona
continue with 1.
This works nearly half a day, the suddendly we got no longer evt_le_gap_scan_response events.
If I try at the console start scanning again cmd_le_gap_start_discovery I will receive 0x0181 "Device is in wrong state to receive commands", so I think ok the chip is already in scanning mode.
if I try cmd_le_gap_end_procedure the response is OK for stopping the scan.
After that I can cmd_le_gap_start_discovery again with response OK, but I don't receive any evt_le_gap_scan_response events.
The only command at the moment which brings back the events is cmd_system_reset(0). After the reboot event I can start again.
Can you please help me how I can receive the evt_le_gap_scan_response events whitout make a reset of the chip.
The new iOS Blue Gecko app v.1.5.1 successfully updates the apploader but then after rebooting fails with the message "Unable to find "OTA" device." On a side note, it works fine with a partial update. After the error message of being unable to find the OTA device, I can see the "OTA" device in the Bluetooth Browser. At this point, it seems the dfu process has erased the application but the 1.5.1 Blue Gecko app is unable to perform a partial update and continues to report "Unable to find "OTA" device. My device would be bricked at this point if it weren't for the fact that the old version of the iOS Blue Gecko app v. 1.4.2 can then successfully perform a partial update of the application. Do I need to make an update to my project in order to support version 1.5.1? I tested with Bluetooth 2.11 and 2.12.
All of this testing is with the security features (such as encryption,signing, and secure boot) turned off.
Forum
Bluetooth Knowledge Base Article List
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
SoC-Empty Example Improvements in Bluetooth SDK 2.11
As you may have noticed, a new Bluetooth SDK (2.11.0) was recently released as part of the Gecko SDK Suite v2.5.0. This post highlights some of the developer experience (DX) improvements in this release.
One of the changes introduced in this SDK is refactoring of the soc-empty example. The example code itself has not changed much, but the project has been slightly restructured. The target here is to:
For more details on the new soc-empty structure, see the following KB article: Bluetooth SoC-Empty example
If you are currently using an older SDK version (between 2.6.x and 2.10.x), no need to worry - the new soc-empty is still quite similar, there are no drastic changes.
Some additional improvements that will help you get started:
More details are found in the KB article linked above.
If you have any questions or comments about the new soc-empty example, feel free to post comments in this thread!
Provisioning mesh nodes (BGM13P) from Bluez 5.50
Hi folks,
I'm currently working on implementing Bluetooth mesh features for BGM13P chips. We want to provision and access the mesh nodes from linux embedded side. Unfortunatly a Bluetooth mesh library (which was described in the Mesh webinar) is not available. My starting point is your "mesh light node" sample which works fine with your demo app. Porting this knowledge to linux (based on Bluez 5.50 as an alternative) I currently face some issue in the provisioning phase. In your documentation refering the light sample you explain that only an android client sdk is currently available. Could you also give some advice/requirement that is needed to run provisioning successful? Do you also offer or has some plans to support linux as well too? If so I will now follow up with some more detailled error description. It would be great to access your devices from linux as well. I think many people are really interested in that! I'm also more interested in having a SiliconLabs mesh library which is able to run on ARM and x86.
Under linux I build Bluez 5.50 with mesh support to have access to the commandline tool (meshctl). Running meshctl I follow the provisioning process. After connecting to the the development board and exchanging some piece of data, the provisioning failed.
Running meshctl from Bluez 5.50 (build with option --enable-mesh)
$ meshctl
[meshctl]# discover-unprovisioned on
SetDiscoveryFilter success
Discovery started
Adapter property changed
[CHG] Controller 6D:10:51:73:84:E3 Discovering: yes
Mesh Provisioning Service (00001827-0000-1000-8000-00805f9b34fb)
Device UUID: 53696c6162734465762dc6838c570b00
OOB: 0000
[NEW] Device 00:0B:57:8C:83:C6 light node 83:c6
[meshctl]# provision 53696c6162734465762dc6838c570b00
Trying to connect Device 00:0B:57:8C:83:C6 light node 83:c6
Adapter property changed
[CHG] Controller 6D:10:51:73:84:E3 Discovering: no
Connection successful
Services resolved yes
Found matching char: path /org/bluez/hci0/dev_00_0B_57_8C_83_C6/service0009/char000a, uuid 00002adb-0000-1000-8000-00805f9b34fb
Found matching char: path /org/bluez/hci0/dev_00_0B_57_8C_83_C6/service0009/char000c, uuid 00002adc-0000-1000-8000-00805f9b34fb
Start notification on /org/bluez/hci0/dev_00_0B_57_8C_83_C6/service0009/char000c
Characteristic property changed /org/bluez/hci0/dev_00_0B_57_8C_83_C6/service0009/char000c
AcquireNotify success: fd 7 MTU 69
Notify for Mesh Provisioning Out Data started
Open-Node: 0x2f0bce0
Open-Prov: 0x2f21310
Open-Prov: proxy 0x2f1c390
Initiated provisioning
Characteristic property changed /org/bluez/hci0/dev_00_0B_57_8C_83_C6/service0009/char000a
AcquireWrite success: fd 8 MTU 69
GATT-TX: 03 00 10
GATT-RX: 03 01 01 00 01 00 00 00 00 00 00 00 00
Got provisioning data (12 bytes)
01 01 00 01 00 00 00 00 00 00 00 00
Provisioning failed
Attempting to disconnect from 00:0B:57:8C:83:C6
Characteristic property changed /org/bluez/hci0/dev_00_0B_57_8C_83_C6/service0009/char000c
Write closed
Services resolved no
Characteristic property changed /org/bluez/hci0/dev_00_0B_57_8C_83_C6/service0009/char000a
The development board with BGM13P shows following state changes on its display
1) unprovisioned
2) provisioning - connected
3) prov failed
4) unprovisioned
BGX13P not pairing automatically
I have a project where two BLE modules exchange data. The slave should constantly send data and the master (Central) should read the data automatically after starting. I miss in the command set of the BGX the option to connect e.g. the last slave automatically again.
At the moment I connect via "scan" and later via "con 1" which is not very satisfying. Alternatively I wanted to try the assignment of a hardware pin: GPIO0: ufu 0 scan and GPIO1: ufu 0 con 1 each with "Function Trigger" Rising Edge. But that didn't work.
I tried a lot of things - but didn't find the right solution.
I would be very grateful for a suggestion on how the connection can be re-established automatically after a first contact. (or a certain address, e.g. BGX-3425)
(I have two BGX13P Dev Boards and several BGX13P to try out.)
Best regards,
Ralf
Bluetooth Xpress and MIT APP Inventor?
Transfer file for STM32 firmware update over BLE (BLED112 and BGM13P32)
Hi !
I've been trying to update an STM32 firmware. I am able to send a file using the SPP example. I have a BLED112 connected with my pc (cygwin terminal).
The other MCU have a Bootloader that use Ymodem to transfer files. I have connected the UART of my board with the UART of the STM32 MCU). I can send the file, and it's properly sent but my firmware is not updated. I assume that it comes from the Ymodem protocol that does not recognise the data that I transmit.
1) At this point I want to send Ymodem Packets over BLE (with CRC) but the size of the data exchanged by this protocol is about 1k, and with Bluetooth I can't obviously send 1k by 1k packets. So how can i do that ?
2) Is there a better way of doing this firmware update over BLE, knowing I can modify the Bootloader firmware ? An other protocol that better match with BLE ?
Thanks in advance for your help.
Florian
BLE connectivity issues with RAIL 2.7.0
Hi,
we are currently working on a DMP project using 2.4 GHz IEEE 180.15.4 and BLE on a EFR32MG13P732.
After upgrading to SDK 2.6.0.0, RAIL 2.7.0 Build 24 [BLE Gecko v2.12-0 Build 69], we have issues to establish BLE connections. The fast majority of connection attempts fail, ofthen this causes the advertisements to stop. Many of these connection attempts do not lead to any additional Link layer aktivity.
This problem does NOT occur on MG12 (BRD4162A).
The problem also does not occur on RAIL v2.6-2 Build 2. It is suffiicient to downgrade the file librail_multiprotocol_efr32xg13_iar_release.a to version 2.6.2 to solve the issue, not changing any of the other RAIL files. We can also reproduce this behavoiour with Demo software on Silabs Eval Boards, not using our own hardware or firmware. Also on Silabs Eval hardware, downgrading librail_multiprotocol_efr32xg13_iar_release.a solves the issue.
Steps to reproduce:
Please let us now whether you can re-create this and how we can fix this without downgrading.
Thanks in advance
cmuClock_ADC0 undeclared?
Hello!
I'm currently following this article : https://www.silabs.com/documents/public/training/wireless/getting-started-bluetooth-sdk.pdf
I had a problem on the section 3.6, reading and writing the Local Database, when I follow the example to the letter, it said that cmuClock_ADC0 is not declared in app.c
I'm currently using Bluetooth SDK 2.12, and program using the template soc-empty.
Thank you in advance!
Connecting mobile phone to the module
BLED112 Dongle does not transfer every advertisement packets sent by my devices
I use the BLED112 with firmware version ble-1.6.0-140 and the dongle does not transmit to the COM port every advertisement packets my devices send.
I start scanning using GAP Discover Mode gap_discover_observation (cmd_gap_discover(2)) and receive advertisement packets every 500 ms as expected, but all at once I don't receive any more advertisement packets for seconds - sometimes more than 30s, and suddenly everything works again as before.
I am sure that my device is sending an advertisement packet every 500 ms because I measured / assert this with other BLE hardware, and I can connect the device even during this pause period.
What can it be? Is there any configuration parameter that I need to set?
Thanks
Timings of GATT operations of BLE Stack
Hi,
I have a hard time understanding when exactly data transfer occurs when calling stack functions (I'm using BGM13P modules). Suppose, we have an established connection between two devices (M and S) with connection interval = 100 ms. If I understand correctly, stack will wake both devices from EM2 every 100 ms without any need of software timer. If I call function gecko_cmd_gatt_read_characteristic_value() on Master after wake up, will stack send read command during this connection event or will it wait another 100 ms to send it in next connection event? And how much time do I have to call the command before Master sends its Data PDU upon waking up? The same goes for the Slave: will Slave respond to this command during this connection event or will it wait for the next one?
Thank you.
Enable COEX feature with WT32i Development Kit
Hi!
Please advice how to enable coex feature with WT32i Development kit.
I can't find any document about it.
Thanks!
grab debug console of multiple target device on bluetooth client.
I have one bluetooth client and 3 target devices.
Target device is made up of Mighty Gecko Radio board + Giant Gecko Master board and Tiny Gecko Slave board.
The Giant Gecko and Tiny Gecko is connected to Mighty Gecko Radio board over UART interface. The Bluetooth client communicated to the target device via the target radio board
Based on above connection. I want to grab the debug console of all three target device from my bluetooth client. Kindly guide me how to achieve this.
Thanks and appreciated for your response.
reg.
-prajose
NCP empty target stops suddendly evt_le_gap_scan_response events
Hi all,
we use a bluetooth SDK 2.11 running a ncp-empty-target application connected over uart to a linux uart with 115200 Baud 8,N,1.
If we start scanning with command cmd_le_gap_start_discovery for LE Coded PHY devices.
As BLE chip we use the BGM13S32.
The princip of working is this:
This works nearly half a day, the suddendly we got no longer evt_le_gap_scan_response events.
If I try at the console start scanning again cmd_le_gap_start_discovery I will receive 0x0181 "Device is in wrong state to receive commands", so I think ok the chip is already in scanning mode.
if I try cmd_le_gap_end_procedure the response is OK for stopping the scan.
After that I can cmd_le_gap_start_discovery again with response OK, but I don't receive any evt_le_gap_scan_response events.
The only command at the moment which brings back the events is cmd_system_reset(0). After the reboot event I can start again.
Can you please help me how I can receive the evt_le_gap_scan_response events whitout make a reset of the chip.
Thank you in advance for your help.
Latest iOS Blue Gecko v1.5.1 app OTA DFU failure
The new iOS Blue Gecko app v.1.5.1 successfully updates the apploader but then after rebooting fails with the message "Unable to find "OTA" device." On a side note, it works fine with a partial update. After the error message of being unable to find the OTA device, I can see the "OTA" device in the Bluetooth Browser. At this point, it seems the dfu process has erased the application but the 1.5.1 Blue Gecko app is unable to perform a partial update and continues to report "Unable to find "OTA" device. My device would be bricked at this point if it weren't for the fact that the old version of the iOS Blue Gecko app v. 1.4.2 can then successfully perform a partial update of the application. Do I need to make an update to my project in order to support version 1.5.1? I tested with Bluetooth 2.11 and 2.12.
All of this testing is with the security features (such as encryption,signing, and secure boot) turned off.