Socket Select in coex mode#
1. Purpose / Scope#
This application demonstrates how to create the multiple sockets in RS9116W EVK and monitor multiple sockets for a certain activity to occur. If there is some data to be read on one of the sockets, the Select provides the response about the socket whether the data is to be read on the socket or not. This also can be used in Coex mode(BLE & Wlan mode).
2. Prerequisites / Setup Requirements#
Before running the application, the user will need the following things to setup.
2.1 Hardware Requirements#
Windows PC with Host interface (UART / SPI/ SDIO).
Silicon Labs RS9116 Wi-Fi Evaluation Kit
Host MCU Eval Kit. This example has been tested with:
Silicon Labs WSTK + EFR32MG21
Silicon Labs WSTK + EFM32GG11
Wireless Access point
TCP client application running in Windows PC2 (This uses iperf application to open TCP client socket in remote PC)
2.2 Software Requirements#
Embedded Development Environment
For STM32, use licensed Keil IDE
For Silicon Labs EFx32, use the latest version of Simplicity Studio
Iperf Application in the remote PC.
User can install any of the below apps to verify WLAN Station BLE Provisioning.
Install Android based Silicon labs Connect APK:
Access the apk provided in the path:
<SDK>/utilities/Silicon_lab_connectApp.apk
Install windows Silicon labs connect application in laptop.
Refer the application provided in the path:
<SDK>/utilities/windows_ble_provisioning_appFollow the instructions provided in the path:
<SDK>/utilities/windows_ble_provisioning_app/Installation_steps_to_run_silabs_connect_windows_application.docx
3. Application Build Environment#
3.1 Platform#
The Application can be built and executed on below Host platforms
3.2 Host Interface#
By default, the application is configured to use the SPI bus for interfacing between Host platforms(STM32F411 Nucleo / EFR32MG21) and the RS9116W EVK.
This application is also configured to use the SDIO bus for interfacing between Host platforms(EFM32GG11) and the RS9116W EVK.
3.3 Project Configuration#
The Application is provided with the project folder containing Keil and Simplicity Studio project files.
Keil Project
The Keil project is used to evaluate the application on STM32.
Project path:
<SDK>/examples/snippets/wlan_ble/wlan_station_ble_provisioning_select/projects/wlan_station_ble_provisioning_select-nucleo-f411re.uvprojx
Simplicity Studio
The Simplicity Studio project is used to evaluate the application on EFR32MG21.
Project path:
If the Radio Board is BRD4180A or BRD4181A, then access the path
<SDK>/examples/snippets/wlan_ble/wlan_station_ble_provisioning_select/projects/wlan_station_ble_provisioning_select-brd4180a-mg21.slsprojIf the Radio Board is BRD4180B or BRD4181B, then access the path
<SDK>/examples/snippets/wlan_ble/wlan_station_ble_provisioning_select/projects/wlan_station_ble_provisioning_select-brd4180b-mg21.slsprojUser can find the Radio Board version as given below
EFM32GG11 platform
The Simplicity Studio project is used to evaluate the application on EFM32GG11.
Project path:
<SDK>/examples/snippets/wlan_ble/wlan_station_ble_provisioning_select/projects/wlan_station_ble_provisioning_select-brd2204a-gg11.slsproj
3.4 Bare Metal/RTOS Support#
This application supports bare metal and RTOS environment. By default, the application project files (Keil and Simplicity studio) are provided with bare metal configuration in the SDK. Steps to configure project settings in Keil IDE - Open project in Keil IDE and click on 'Options for Target' - Go to 'C/C++' tab and remove 'RSI_WITH_OS' macro present under Preprocessor Symbols - Click on 'OK' button to save the settings
Steps to configure project settings in Simplicity Studio - Open project in Simplicity Studio - Right click on the project and choose 'Properties' - GO to 'C/C++ Build' | 'Settings' | 'GNU ARM C Compiler' | 'Symbols' and remove macro 'RSI_WITH_OS=1' - Click on 'Apply' and 'OK' to save the settings
4. Application Configuration Parameters#
The application can be configured to suit user requirements and development environment. Read through the following sections and make any changes needed.
4.1 Open main.c file#
Memory length for driver
#define GLOBAL_BUFF_LEN 15000The following parameters are configured if OS is used.
Task Priotrities should be given as below. Application task priority should be given as low priority and Driver task priority should be given as highest priority
#define RSI_APPLICATION_TASK_PRIORITY 1
#define RSI_BLE_TASK_PRIORITY 2
#define RSI_DRIVER_TASK_PRIORITY 3Application Task stack size is configured by this macro
#define RSI_APPLICATION_TASK_STACK_SIZE 1000BLE Task stack size is configured by this macro
#define RSI_BLW_TASK_STACK_SIZE 1000Driver Task stack size is configured by this macro
#define RSI_DRIVER_TASK_STACK_SIZE 20004.2 Open rsi_wlan_app.c file#
4.2.1 The desired parameters are provided below. User can also modify the parameters as per their needs and requirements.#
To configure IP address
DHCP_MODE refers whether IP address configured through DHCP or STATIC
#define DHCP_MODE 1Note: If user wants to configure STA IP address through DHCP then set DHCP_MODE to "1" and skip configuring the following DEVICE_IP, GATEWAY and NETMASK macros. (Or) If user wants to configure STA IP address through STATIC then set DHCP_MODE macro to "0" and configure following DEVICE_IP, GATEWAY and NETMASK macros.
IP address to be configured to the device in STA mode should be in long format and in little endian byte order.
Example: To configure "192.168.10.10" as IP address, update the macro DEVICE_IP as 0x0A0AA8C0.
#define DEVICE_IP 0X0A0AA8C0IP address of the gateway should also be in long format and in little endian byte order
Example: To configure "192.168.10.1" as Gateway, update the macro GATEWAY as 0x010AA8C0.
#define GATEWAY 0x010AA8C0IP address of the network mask should also be in long format and in little endian byte order
Example: To configure "255.255.255.0" as network mask, update the macro NETMASK as 0x00FFFFFF.
#define NETMASK 0x00FFFFFFThe following parameters are configured if OS is used. WLAN task should be of low priority
#define RSI_WLAN_TASK_PRIORITY 1Driver task should have the highest priority among all threads
#define RSI_DRIVER_TASK_PRIORITY 2WLAN Task stack size is configured by this macro
#define RSI_WLAN_TASK_STACK_SIZE 500Driver Task stack size is configured by this macro
#define RSI_DRIVER_TASK_STACK_SIZE 500Application memory length which is required by the driver
#define GLOBAL_BUFF_LEN 15000User can connect to access point through PMK
To Enable keep 1 else 0
#define CONNECT_WITH_PMK 0Note: If CONNECT_WITH_PMK is enabled, SECURITY_TYPE is set to RSI_WPA2_PMK.
4.3 Open rsi_wlan_config.h file#
#define CONCURRENT_MODE RSI_DISABLE
#define RSI_FEATURE_BIT_MAP (FEAT_SECURITY_OPEN | FEAT_AGGREGATION)
#define RSI_TCP_IP_BYPASS RSI_DISABLE
#define RSI_TCP_IP_FEATURE_BIT_MAP (TCP_IP_FEAT_DHCPV4_CLIENT | TCP_IP_TOTAL_SOCKETS_1 | TCP_IP_FEAT_EXTENSION_VALID)
#define RSI_CUSTOM_FEATURE_BIT_MAP FEAT_CUSTOM_FEAT_EXTENTION_VALID
#define RSI_EXT_CUSTOM_FEATURE_BIT_MAP 0
#define RSI_EXT_TCPIP_FEATURE_BIT_MAP (EXT_DYNAMIC_COEX_MEMORY | EXT_TCP_IP_TOTAL_SELECTS_1)
#define RSI_BAND RSI_BAND_2P4GHZ
#define RSI_BT_FEATURE_BITMAP (BT_RF_TYPE | ENABLE_BLE_PROTOCOL)Note: RSI_EXT_TCPIP_FEATURE_BIT_MAP-- has been added with EXT_TCP_IP_TOTAL_SELECTS_1 rsi_wlan_config.h, rsi_bt_config.h and rsi_ble_config.h files are already set with the above desired configuration for this example.
4.4 Open rsi_ble_app.c file and update/modify following macros#
RSI_BLE_CHAR_SERV_UUID refers to the attribute type of the characteristics to be added in a service.
#define RSI_BLE_CHAR_SERV_UUID 0x2803RSI_BLE_CLIENT_CHAR_UUID refers to the attribute type of the client characteristics descriptor to be added in a service.
#define RSI_BLE_CLIENT_CHAR_UUID 0x2902RSI_BLE_NEW_SERVICE_UUID refers to the attribute value of the newly created service.
#define RSI_BLE_NEW_SERVICE_UUID 0xAABBRSI_BLE_ATTRIBUTE_1_UUID refers to the attribute type of the first attribute under this service (RSI_BLE_NEW_SERVICE_UUID).
#define RSI_BLE_ATTRIBUTE_1_UUID 0x1AA1RSI_BLE_ATTRIBUTE_2_UUID refers to the attribute type of the second attribute under this service (RSI_BLE_NEW_SERVICE_UUID).
#define RSI_BLE_ATTRIBUTE_2_UUID 0x1BB1RSI_BLE_ATTRIBUTE_3_UUID refers to the attribute type of the third attribute under this service (RSI_BLE_NEW_SERVICE_UUID).
#define RSI_BLE_ATTRIBUTE_3_UUID 0x1CC1RSI_BLE_MAX_DATA_LEN refers to the Maximum length of the attribute data.
#define RSI_BLE_MAX_DATA_LEN 66RSI_BLE_APP_DEVICE_NAME refers to the name of the RS9116W EVK to appear during scanning by remote devices.
#define RSI_BLE_APP_DEVICE_NAME "BLE_CONFIGURATOR"The following are the non-configurable macros in the application.
RSI_BLE_ATT_PROPERTY_READ is used to set the READ property to an attribute value.
#define RSI_BLE_ATT_PROPERTY_READ 0x02RSI_BLE_ATT_PROPERTY_WRITE is used to set the WRITE property to an attribute value.
#define RSI_BLE_ATT_PROPERTY_WRITE 0x08RSI_BLE_ATT_PROPERTY_NOTIFY is used to set the NOTIFY property to an attribute value.
#define RSI_BLE_ATT_PROPERTY_NOTIFY 0x10BT_GLOBAL_BUFF_LEN refers to the number of bytes required by the application and the driver.
#define BT_GLOBAL_BUFF_LEN 150005. Testing the Application#
Follow the below steps for the successful execution of the application.
5.1 Loading the RS9116W Firmware#
Refer Getting started with a PC to load the firmware into RS9116W EVK. The firmware file is located in <SDK>/firmware/
5.2 Building the Application on the Host Platform#
5.2.1 Using STM32#
Refer Getting started with STM32
Open the project
<SDK>/examples/snippets/wlan_ble/wlan_station_ble_provisioning_select/projects/wlan_station_ble_provisioning_select-nucleo-f411re.uvprojxin Keil IDE.Build and Debug the project
Check for the RESET pin:
If RESET pin is connected from STM32 to RS9116W EVK, then user need not press the RESET button on RS9116W EVK before free run.
If RESET pin is not connected from STM32 to RS9116W EVK, then user need to press the RESET button on RS9116W EVK before free run.
Free run the project.
Then continue the common steps from 5.3
5.2.2 Using EFX32#
Refer Getting started with EFX32, for settin-up EFR & EFM host platforms
Open Simplicity Studio and import the EFR32/EFM32 project from
<SDK>/examples/snippets/wlan_ble\wlan_station_ble_provisioning_select\projectsSelect the appropriate .slsproj as per Radio Board type mentioned in Section 3.3 for EFR32 board. (or)
Select the *.brd4180b-mg21.slsproj for EFR32mg21 board.
Compile and flash the project in to Host MCU
Debug the project
Check for the RESET pin:
If RESET pin is connected from EFX32 to RS9116W EVK, then user need not press the RESET button on RS9116W EVK before free run
If RESET pin is not connected from EFX32 to RS9116W EVK, then user need to press the RESET button on RS9116W EVK before free run
Free run the project
Then continue the common steps from 5.3
5.3 Common Steps#
5.3.1 Steps to verify the WLAN Station BLE Provisioning Example#
Steps to be followed to verify WLAN Station BLE Provisioning with Android Silicon Labs Connect App
Configure the Access point with internet connection in OPEN/WPA-PSK/WPA2-PSK mode to connect the RS9116W EVK in STA mode.
Connect any serial console for prints.
When RS9116W EVK enters BLE advertising mode, launch the EFR Connect App.
Enable the Location services
Click on Start Scanning
Once you scan you will find the module displayed
Connect to an module
Pass the appropriate commands and pass the ssid psk
Refer the below figure for console prints
5.3.2 Steps to be followed to verify WLAN Station BLE Provisioning with windows based Silicon Labs Connect App#
Configure the Access point with internet connection in OPEN/WPA-PSK/WPA2-PSK mode to connect the RS9116W EVK in STA mode.
Connect any serial console for prints.
Note: Turn on BT in the PC.
Go to folder
<SDK>/utilities/windows_ble_provisioning_appand Run Silabs_Connect.py in the command prompt.Executing the application in the command prompt as stated in the above point will open the GUI (with the “BLE SCAN ON� button).
When click on the BLE SCAN ON button, all the RS9116 BLE Devices that are available nearby are displayed in the window.
Note: - RS9116 BLE device will advertise with different names based on the application configuration.
Once RS9116 BLE device displayed on the scanning list, initiate the connection by clicking a button on the available RS9116 BLE device.
Once the BLE get connected, Firmware version and list of available Access Points get displayed on the screen.
By clicking on one of the scanned AP’s, RS9116 will connect to that particular AP. If Access Point is secured it will ask the password as input but if that Access point as not secured, then directly connect to that Access Point.
After successful connection, “IP & Mac address� of connected Access point get displayed.
To disconnect from Access Point, click on connected AP.
After successful disconnection of WLAN, pop-up comes like WLAN GOT DISCONNECTED. Click on the “ok�.
Note: For more information refer Silabs_Connect_Windows_Application_User_Guide.pdf in the path
<SDK>/utilities/windows_ble_provisioning_app/
5.3.3 Steps to follow to create socket connection and run iperf on client#
After the program gets executed, RS9116W EVK is configured as client and connects to AP and gets IP.
After successful connection with the access point, the socket select is issued for the desired socket.
Open TCP client from WindowsPC2 and connect to TCP server opened on the device on port number DEVICE_PORT. The Iperf command to start the TCP client is:
C:\> iperf.exe -c <Module_IP> -p <DEVICE_PORT> -i 1 -t <time interval in sec>For example ...
C:\> iperf.exe -c 192.168.0.100 -p 5001 -i 1 -t 30
Select provides the response about the socket whether the data is to be read on the socket or not.
If data is to be received on the socket, then the receive function is called on the socket.
Compressed Debug Logging#
To enable the compressed debug logging feature please refer to Logging User Guide