WiSeConnect Release Notes#

Release notes are provided with each version of the WiSeConnect™ SDK.

• WiSeConnect™ 2.5.2

• WiSeConnect™ 2.5.1

• WiSeConnect™ 2.5

• WiSeConnect™ 2.4.1

• WiSeConnect™ 2.4

• WiSeConnect™ 2.3

• WiSeConnect™ 2.0

WiSeConnect 2.5.2 Release Notes#

Last updated: April 13, 2022

Highlights#

• Issue fixes

Release Details#

Updates in this Release#

RS9116W 2.5.2 release consists of two components

• Firmware - RS9116 Firmware Binary

• SAPI Library - SAPI Library runs on Host

This release contains bug-fixes and firmware binary updates. It is strongly recommended to update SAPI and firmware together.

Changes and Fixes#

• Fix for Bluetooth SPP Rx latency with SDIO as host interface

• Fix for Bluetooth host application freeze issue with SDIO as host interface

• Documentation updates to address following issues

  • SNTP Error BB08

  • BT Classic and BLE PER Stats command responses are NULL

Known Issues#

• PTA 3-Wire is not supported with power save being enabled.

WiSeConnect 2.5.1 Release Notes#

Last updated: March 29, 2022

Highlights#

• PTA 3-Wire Co-Existence support in Wi-Fi only mode with Thread protocol

• Issue fixes

Release Details#

Updates in this Release#

RS9116W 2.5.1 release consists of two components

• Firmware - RS9116 Firmware Binary

• SAPI Library - SAPI Library runs on Host

This release contains bug-fixes and firmware binary updates. It is strongly recommended to update SAPI and firmware together.

Changes and Fixes#

• PTA 3-Wire Co-existence support in Wi-Fi only mode with Thread protocol

• Fix for rsi_timer_left() to return the remaining time for expiry instead of total time expired so far

• Fix for low transmit power issue reported on latest AA0 modules

• Fix for firmware version showing differently in the package and in the software

• Fix for configuration of SPI_INTR to active low

• Fix for regulator voltages (VOUTLDOAFE, UULP_VOUTSCDC) not matching data sheet specifications

• Fix for HTTP OTAF upgrade issue when done with corrupt firmware in loop

• Fix for EAP TLS certificate loading issue in TCP/IP bypass enabled mode

• Fix for SNTP BB08 error

WiSeConnect 2.5 Release Notes#

Index#

• Highlights

• Release Details

• Updating to this Release

• New Features

• Changes and Fixes

• New APIs

• Recommendations and New Options

• Known Issues

• Limitations and Unsupported Features

• SDK Refactor

• Terminology

Highlights#

• Support for RS9116 chip revision 1.5

• WPA2 Security Enhancements support

• WPA3 Personal support for Station Mode

• Support for Enhanced MaxPSP in Co-Ex Mode

• Support for FAST PSP

• PTA 3-Wire Co-existence Support for Wi-Fi as PTA Master

• BT/BLE User Gain API support

• WRECK Vulnerability fixes

• FragAttacks vulnerability fixes

• SDIO Interface support

• A2DP Source support with Co-existence

• EFM32 (Silicon Labs MCU SLSTK3701A) platform support

Release Details#

Updates in this Release#

RS9116W 2.5 release consists of two components, as follows:

• Firmware - RS9116 Firmware Binary

• SAPI Library - SAPI Library runs on Host

This release is meant only for use with designs based on RS9116 Silicon rev 1.4 (RS9116X-xxx-xxx-Bxx) and RS9116 Silicon rev 1.5 (RS9116X-xxx-xxx-Cxx).
Customers using the RS9116X-xxx-xxx-Xxx parts (Silicon rev 1.3) can also upgrade to the latest firmware. However, you will have to disable the power optimization feature enabling macro EXT_FEAT_LOW_POWER_MODE.

Choose the firmware to match the silicon revision used in your design, as follows:

• RS9116W.2.5.0.26.rps

  • RS9116X-xxx-xxx-Xxx (Silicon rev 1.3)

  • RS9116X-xxx-xxx-Bxx (Silicon rev 1.4)

• RS916W.2.5.0.26.rps

  • RS9116X-xxx-xxx-Cxx (Silicon rev 1.5)

This release has bug-fixes, enhancements, relevant AT command updates, new SAPI features, and firmware. Most of the new features have associated APIs, which are available in the latest SAPI implementation only. It is strongly recommended to upgrade SAPI and Firmware together.

New Features#

Wi-Fi#

• WPA2 Security Enhancements

• WPA3 Personal Support for Station Mode

• Support for Enhanced MaxPSP in Co-Ex Mode

• Support for FAST PSP

• WRECK Vulnerability Fixes

• FragAttacks Vulnerability Fixes

• PTA 3-Wire Co-Existence Support in Wi-Fi only mode (with external Zigbee and BLE)

Bluetooth - Common#

• BT/BLE User Gain API support

Bluetooth - Classic#

• Support for BT Advanced Audio Distribution Profile Source in Co-Ex mode. An example application project is included for the RT595 host platform. This is supported for Chip Revision 1.5 only.

Power Save#

• None

General#

• Support for chip revision 1.5

• Support for SDIO interface

• Logging Infrastructure support for SAPI logging

• 802.11b Tx gain table improvements for chip revision 1.5 QMS

• Chip revision 1.5 B00 certified FCC/ETSI/TELEC gain tables included

• RS9116X-DB00-CCX-BXX certified TELEC gain tables included

• TELEC certified

• Support for examples on EFM32 (Silicon Labs MCU SLSTK3701A) platform for SDIO interface only

• Certified gain tables for FCC/IC, CE and TELEC are included in the release package in the folder .../resources/gain_tables

Changes and Fixes#

• Fix for BT connectivity issue with HID profile with Windows 10 PC

• New API, which allows destroying a driver task before driver de-initialization to facilitate clean termination

• Fix for WLAN scan issue with error code 3 in some of the 1.3-based AA0 modules(RS9116X-SB00-AAX-XXX)

• Fix for Module not responsive after few iterations of SPP profile data transfer in AT mode

• Fix for SPP throughput issue

• Fix for UDP Server socket issue in AP mode

New APIs#

For a complete list of new APIs, see SAPI Changelog

Recommendations and New Options#

Wi-Fi#

• Enable bit 16 of the 'Extended TCP IP Feature' bit map in opermode command for all Wi-Fi socket operations from host to ensure graceful handling during asynchronous closures from peer.

• Enable aggregation (bit 2 of feature_bit_map) in opermode.

• TCP retransmission count value should be 30 or higher, so that the TCP does not disconnect while the rejoin happens.

• For low throughput applications, such as smart lock, disabling the highest MCS rates, such as MCS7 and MCS6 might help reducing packet retransmissions and ensure robust connection during heavy interference.

• To restart the module, the application needs to call rsi_driver_deinit() followed by rsi_driver_init() and rsi_device_init(). For OS cases, additionally call rsi_task_destroy(driver_task_handle) to delete the driver task before calling rsi_driver_deinit() and create again after rsi_device_init() using rsi_task_create().

• Register 'Join Fail Callback' function every time when join is called, as in the rejoin failure path the callback is deregistered. If not done, this might result in a scan not functioning on rejoin failure.

BT/BLE#

• In BLE, the recommended range of the connection interval is as follows:

  • Power Save (BLE Only) - 100 ms to 1.28 s

  • BT Classic + BLE Dual Mode is >= 200 ms

  • Wi-Fi + BLE coex - 30 ms to 250 ms

• In BLE during connection, the configuration of scan interval and scan window with the same value is not recommended.

• In BT Classic, the recommended sniff interval configuration during power save is limited to 100 ms (<= 100).

• In BLE, if a device is acting as central, the scan window (in set_scan_params and create_connection command) must be less than the existing connection interval.

• In BLE mode, if scanning and advertising is in progress and subsequently gets connected and moves to the central role, scanning and advertising stops. To further establish connection to another peripheral device or to a central device, the application should - give a command for starting advertising and scanning again.

• Device Power save need to be disabled before BT init and de-init.

Co-Existence#

• For Wi-Fi + BLE, during Wi-Fi connection, lesser BLE scan Window and larger BLE scan Interval are recommended (1:3 or 1:4).

• Wi-Fi + BLE Advertising

  • All advertising intervals are supported, as per the BT Spec. If the Wi-Fi transactions are more, you may see a slight difference in on-air advertisements compared to the configured intervals.

  • BLE Advertising will be stopped for intervals that collide with Wi-Fi activity.

• Wi-Fi + BLE scanning

  • All scan intervals are supported as per BT Spec. For better scan results, use scan-window and scan interval in 1:3 or 1:4 ratio when the Wi-Fi scan activity is present.

  • BLE scanning will be stopped for intervals that collide with Wi-Fi activity.

• Wi-Fi + BLE Central/Peripheral Connections

  • All connection intervals are supported as per BT Spec.

  • For a stable connection, use optimal connection intervals and max supervision timeout in the presence of Wi-Fi activity.

• Wi-Fi + BLE Central/Peripheral Data Transfer

  • To get better throughputs in both Wi-Fi and BLE, use medium connection intervals, such as 45 to 80 ms with maximum supervision timeout.

  • Ensure Wi-Fi activity consumes lesser intervals.

• For Wi-Fi + BT + BLE, Wi-Fi + BT, Wi-Fi + BLE operating modes, connect Wi-Fi ahead of BT/BLE connections to ensure seamless, stable connection for all 3 protocols.

• For Wi-Fi + BT + BLE, Wi-Fi + BT, Wi-Fi + BLE operating modes, if BT/BLE needs to be connected ahead of Wi-Fi connection, use with high supervision timeout and high connection interval for BLE and high sniff interval for BT, to ensure seamless, stable - connection. This configuration will also ensure a stable BT/BLE connection when Wi-Fi connects/disconnects/rejoins.

• Wi-Fi + BLE Central/Peripheral Data Transfer

System#

• For User Store configuration and Configuration Save, do not enable power save or save it as a configuration. If power save is enabled and saved as a configuration, upon boot up, the module will come up with the saved configuration and will go to power save without any indication to the host.

• Set Optimization level to O0 in project settings for IDE (KEIL).

• Memory Configuration must be 384K for BT/BLE and Co-Ex Operating Modes

  • Usage of Low Power Flash mode bit (Bit 19 in Extended customer feature bitmap). Enable this bit for ultra low power standby associated scenarios. This results in about 20µA lower Wi-Fi standby associated current consumption.

• Memory Configuration in SAPI functions: The default memory configuration is 384K. You can configure it to 256/320/384kB by changing the macros defined in the below two files:

  • In rsi_wlan_config.h : RSI_EXT_CUSTOM_FEATURE_BIT_MAP EXT_FEAT_256K_MODE or EXT_FEAT_320K_MODE or EXT_FEAT_384K_MODE

  • In rsi_common.c : rsi_uint32_to_4bytes(rsi_opermode->ext_custom_feature_bit_map, (EXT_FEAT_256K_MODE (or) EXT_FEAT_320K_MODE (or) EXT_FEAT_384K_MODE | RSI_EXT_CUSTOM_FEATURE_BIT_MAP));

• Apply opermode commands in AT mode correctly. The wrong opermode in some cases might lead to unspecified behavior.

• Set the recommended Power Save Profile (PSP) type to Enhanced Max PSP.

• Disable power save during firmware upgrade and re-enable on upgrade completion.

• Disable power save for high throughput applications.

• The application needs to ensure that it sets RTC with correct timestamp when the feature is enabled before establishing the SSL connection.

• Timeout value should be minimum 1 second for socket select and socket receive calls. Timeout value less than 1 second is not currently supported.

• For more details, see 'Configuration parameters' in the SAPI Reference Manual.

Known Issues#

Network Stack#

• Sometimes during the SSL Handshake, the generated ECC curve parameters are incorrect, resulting in connection failure with BBD2 error. However, this recovers in the next attempt.

• MQTT disconnects during firmware upgrade using OTAF, when power save is enabled. Disable power save during firmware upgrade and re-enable on upgrade completion.

• Newly Added GCM Based Strong Cipher Suites will have performance issues as Hardware support is not available in the current platform.

• Recommended MQTT Publish payload is 1 kB.

• If the HTTP Server is configured in the module, MQTT client port should not be port configured on port 80.

• Randomize the client port if using rapid connect/disconnect of the MQTT session on the same client port with the power save.

• Secure SSL Renegotiation not supported in Embedded Networking Stack.

• IPv6 support is not available in this release.

Wi-Fi#

• WPA3 known issues

  • Connection takes about 1 second

  • SAE H2E (Hash to Element) is not supported

  • Transition disable indication is not supported

  • PMK SA caching is not supported

• If the station performs the scan in concurrent mode (Wi-Fi STA+AP), it is possible for stations connected to the AP to get disconnected. Enable AP after STA connection is completed.

• Issue observed with WPA2 Enterprise Connectivity using Microsoft RADIUS Server.

• If BG Scan is enabled along with custom feature bit map bit (8) configuration of the DFS channel support, issues may occur in getting IP address for the Wi-Fi STA.

• In FAST PSP, a configuration socket close is observed in full duplex communication in long duration tests.

BT/BLE#

• Wake on Wireless not supported for BLE.

• BT-HID might not inter-operate with Apple devices.

• In Wi-Fi + BT/BLE Co-Ex mode, high Wi-Fi broadcast traffic might cause BT/BLE disconnections.

• In Wi-Fi + BT mode when there is continuous Wi-Fi data, you might observe BT not re-connecting to remote after disconnection.

• BT-A2DP interoperability issue might be observed with some headsets.

• For BLE, dual role scenario issues might occur when connecting as central if the advertising is also going out for the peripheral role. Central connections can be made after the peripheral connections are established and advertising is stopped.

• BLE disconnection is observed if both peer and module already have bond info and module initiating security as part of BLE secure connections. A possible workaround in the application is not to initiate a security request if the bond information is already available.

• LMP timeout BLE disconnection observed with latest Realme mobile handsets.

• Some of the A2DP music streaming glitches are observed if the Wi-Fi download is in progress at the same time.

• Issue with EDR-3DH5 packet reception, where in bit error rate of more than 50% is observed.

Co-Existence#

• In Co-ex mode if power save is enabled, it stays in enabled state even after Wi-Fi disconnection. Disable power save after every radio_init() and enable it when intended by application.

• BLE may disconnect with Wi-Fi + BLE configuration and Wi-Fi continuous data transfer when the low BLE supervision timeout is configured. When the supervision timeout is configured with the value of 16 seconds, no disconnections are observed.

• WiFi + BLE mode WPS is not working.

• Wi-Fi +BLE/BLE only mode: For SPI as host interface, continuous BLE TX notification might cause the host interface to hang needing a hardware reset. The issue is not seen with discrete burst BLE data.

• In Wi-Fi + BT/BLE configuration with Wi-Fi disconnects, BT/BLE reconnection issue is observed (see the earlier section 'Recommended Configurations and Application Development options' in this document).

Interoperability#

• QoS null frames indicating going to power save if not acknowledged by AP may cause AP not to sync with the power save state, resulting in possible disconnections.

• If 3rd party access points are periodically not sending beacons, in some scenarios unicast probe requests are not sent from the module, as expected, which might result in disconnections.

System#

• Chip Revision 1.3 doesn't support low power mode optimization using bit setting defined by EXT_FEAT_LOW_POWER_MODE, setting, which results in hang issue.

• Sometimes the module goes to power save before the configured monitor interval for inactivity when Co-Ex mode is configured.

• Wake on Wireless support is tested only for UART AT command interface.

• Power save without RAM retention is not working for the SPI interface.

• FTP Client application is not working with EFx32/STM32 in the OS scenario. The demo app to be tested only for non-OS scenario.

• HTTP OTAF application is not working with EFR32 and EFM32 in OS scenario. The demo app to be tested only for non-OS scenario on EFR32.

• Firmware upgrade for both OS and non-OS scenarios is not working for EFM32 application

Limitations and Unsupported Features#

Wi-Fi/Network Stack#

• AMSDU TX is not supported.

• Fragmentation is not supported.

• AMSDU's within AMPDU is not supported.

• Currently, the module does not support Radio Measurement Requests feature of CCX V2

• 802.11k is not supported

• Short GI is not supported

• 40 MHz bandwidth for both 2.4 & 5 GHz band is not supported.

• 802.11J channels less than 16 are not supported.

• USB host interface and USB Power save are not supported.

• Total MQTT Command Length, apart from MQTT Publish, should not exceed 150 bytes. This includes at+rsi (start of command) to (end of command)\r\n.

• Configure MQTT_VERSION in rsi_mqtt_client.h based on the server configuration; only version 3 and 4 are supported.

• 3xSSL connections or 1xTCP and 2xSSL connection, connections are supported concurrently in Wi-Fi only mode.

• SSL Curve IDs supported are 15-28. SSL handshake with 3rd party clients depends on the SSL Curve ID.

BT/BLE#

• BT A2DP is supported on chip version 1.5 only

• BT Sniff mode does not work if BT multiple slaves feature is enabled.

• For BLE, if the connection is established with a small connection interval (< 15 ms), simultaneous roles (i.e., Central/Peripheral + Advertising/Scanning) are not supported.

• BLE maximum 2 concurrent connections are supported, which can be either a connection to two peripheral devices or to 1 central and 1 peripheral device.

• For BT Classic, only 1 connection is supported at any time

• BLE Slave latency value is valid up to 32 only.

• BT-A2DP encoder is not supported in the firmware

• BT-A2DP not supported in AT mode

Co-Existence#

• In Wi-Fi + BLE during Wi-Fi connection, if both BLE scan interval and window are the same, an issue will occur in successfully making the Wi-Fi connection.

• For AT commands, Wi-Fi + BT + BLE (Opermode 9) B + BLE (Opermode 8) are not working. However, BT, Wi-Fi + BT modes (Opermode 5) works fine. Also, all combinations work fine with SAPI.

• Wi-Fi STA + BT + BLE multiprotocol cases require detailed understanding of use cases and associated configurations. Contact Silicon Labs support for more details.

• Wi-Fi AP + BLE, Wi-Fi AP + BT & Wi-Fi AP + BT + BLE modes are not supported.

SDK Refactor#

The SDK folder structure and names were significantly changed in the 2.4 release. For detailed information, see SAPI Changelog

Terminology#

WiSeConnect 2.4.1 Release Notes#

Last updated: September 10, 2021

Highlights#

• FragAttack Vulnerability Fixes

• Wi-Fi Interoperability issue fixes

Release Details#

Updating to this Release#

RS9116W 2.4.1 release consists of two components

• Firmware - RS9116 Firmware Binary

• SAPI Library - SAPI Library runs on Host

This release has bug-fixes and Firmware. It is strongly recommended to upgrade SAPI and Firmware together.

Changes and Fixes#

• Fix for FragAttack Vulnerabilities

• Fix for issues on Swyentooth Vulnerability fixes

• Fix for few Wi-Fi interoperability issues with certain Access Points

• Fix for issue in BLE local attribute setting, when notification not enabled in remote, resulting in error 4046

• Fix for issue in AP mode, switching to 5 GHz band results in 0x5B error

• Fix for UDP Asynchronous socket not storing and providing remote IP and Port information

• Fix for Wi-Fi low RF transmit power output issue for AA0 modules

• Fix for ping failure after reconnection to AP in concurrent mode

• Fix for HTTP OTAF upgrade failing in subsequent iterations if first iteration fails due to network connections resulting in 0xBBED error

• Fix for issue with BLE connection 2nd iteration onwards after connect/disconnect when remote device is advertising as connectable

• Fix for issue of BT disconnection with continous SPP_rx traffic, sometime due to LMP timeout

Known Issues#

• FragAttack Vulnerability CVE-2020-24588: Aggregation Attack (accepting non SPP A-MSDU frames) is not addressed in this release, as this needs a change in specification

• FragAttack Vulnerability CVE-2020-26146: Aggregation Attack (reassemble fragments with non-consecutive packet numbers) is not addressed in this release

Workarounds#

CC0/CC1 Host Interface Detection at Low Temperatures#

One or more of the serial host interfaces of RS9116 CC0/CC1 modules may fail to respond to host detection at ambient temperatures lower than approximately -20 degC. Execute the following sequence of commands to adjust the module calibration to workaround this issue.

#define BURN_INTO_FLASH      1 
#define BURN_XO_FAST_DISABLE 8

rsi_wireless_init(8, 0);  // Set the operating mode of the module
rsi_wlan_radio_init();    // Set the operating band and initialize the module
rsi_calib_write(BURN_INTO_FLASH, BURN_XO_FAST_DISABLE, 0, 0);   // Trigger the calibration write process to update the 
                                                                // information in flash and wait for a response from the firmware.

Note!

• The workaround must be executed at room temperature, ~25 degC.

• The command sequence must be executed once ONLY.

• Ensure the power supply to the module is stable while issuing commands.

• The workaround is needed for existing products/boards already mounted with CC0/CC1 modules only.

• Once executed, the module must be power-cycled before it can be used for normal operation.

WiSeConnect 2.4 Release Notes#

Index#

• Highlights

• Release Details

• Updating to this Release

• New Features

• Changes and Fixes

• New APIs

• Recommendations and New Options

• Known Issues

• Limitations and Unsupported Features

• SDK Refactor

• Terminology

Highlights#

• Azure and AWS cloud connectivity support

• SweynTooth vulnerabilities fixes

• Strong cipher suite support

• Co-Existence Algorithm Enhancements

• EN 300 328 v.2.2.2 certification support

• TELEC certification support

• Wi-Fi interoperability fixes and enhancements

• Crystal calibration support (Needed for RS9116 QMS)

• Significant reorganization and refactoring of the SDK

• Integrated support for EFR32MG21 hosts and Simplicity Studio

Release Details#

Updating to this Release#

RS9116W 2.4 release consists of two components

• Firmware - RS9116 Firmware Binary

• SAPI Library - SAPI Library runs on Host

This release has bug-fixes, enhancements, new SAPI features and Firmware. Most of the new features have associated APIs, which are available in the latest SAPI implementation only. It is strongly recommended to upgrade SAPI and Firmware together.

New Features#

Wi-Fi#

• Azure support for cloud connectivity

• AWS support for cloud connectivity

• Support for dynamic switching between AP and STA mode of operation (see config_feature_bit_map[16])

• Support for loading certificate without requiring a reboot of the chip

• Configurability option for disabling transmit data rates MCS5, MCS6 and MCS7

• Support for stronger cipher suites

• Support for enhanced max-PSP mode for better interoperability, see config_feature_bit_map[26] and refer to API rsi_wlan_power_save_profile(). This PSP type is supported for STA-only mode.

• Enhancements for better interoperability. Keep alive configuration, graceful closure of previous WLAN connections.

• Enhancements to Wi-Fi Auto Rate adaptation algorithm

• Enhancements to Wi-Fi + BLE Co-Existence support

• Improvements to Wi-Fi + BLE provisioning examples

Bluetooth - Common#

• Resolution to SweynTooth family of BT vulnerabilities

Bluetooth - Classic#

• Support for BT Advanced Audio Distribution Profile Source (BT alone mode only). Example Application project included for RT595 host platform

Power Save#

• Fixes for functional issues in power save mode at high temperature, 85°C

General#

• WLAN EN 300 328 v.2.2.2 ETSI Certification Compliance support added for the following modules and SoC Versions: B00 1.4, QMS 1.3, QMS 1.4, CC0/CC1 1.3, CC0/CC1 1.4, and AA0/AA1 1.3

• Certified gain tables are added for these modules for different antennas, which can be configured using the user gain table API for Wi-Fi and rsi_bt_set_antenna_tx_power_level() API for BT/BLE. Default firmware configuration is for the internal PCB/Chip Antenna

  • B00: Internal Antenna (Fractus FR05-S1-N-0-102) and Dipole antenna (Taoglas GW.34.5153)

  • CC0/CC1 1.4 FCC/ETSI: dipole antenna (GW.71.5153), dipole antenna (Inside WLAN PRO-IS 299), PCB antenna (RSIA7), PIFA antenna (Smarteq 4211613980), PIFA antenna (MARS-31A8 Wi-Fi antenna)

  • CC0/CC1 1.3 : PCB antenna , dipole antenna

  • AA0/AA1-1.3: Chip antenna, heavy-duty screw mount antenna

• TELEC certification support

• Support for chip manufacturing software (Crystal Calibration support for RS9116 QMS chip integration)

• Support for examples on the EFR Platform

• Package and documentation restructure

Changes and Fixes#

• Fixes for memory leak in SSL, ensuring stability for longer connection

• Resolved issue with TCP long data transfer with low power configuration for memory configuration greater than 256k.

• Fix for setting device local name for BLE

• Fix for rsi_ble_white_list_using_adv_data() failure

• Fix for store config/auto-config keep-alive timeout not working.

• Fix for HID Keyboard notifications not being seen on the iOS mobile side

• Configurability support in Firmware update APIs for the SAFE and FAST upgrade

• Mishandling of SDIO interrupts addressed in SAPI driver by calling rsi_hal_intr_pin_status() API. MCU HAL APIs will need to port this API for respective platform. Refer to SAPI porting guide for more information.

• Boot up issue at low temperature (refer to API rsi_calib_write() Bit of 3)

New APIs#

For a complete list of new APIs, see SAPI Changelog

Recommendations and New Options#

Wi-Fi#

• It is recommended to enable bit 16 of the 'Extended TCP IP Feature' bit map in opermode command for all Wi-Fi Socket Operations from host to ensure graceful handling during asynchronous closures from peer.

• Aggregation (bit 2 of feature_bit_map) is recommended to be enabled in opermode.

• TCP retransmission count value is recommended to be 30 or higher, so that the TCP does not disconnect while the rejoin happens.

• For low throughput applications, such as a Smart lock, disabling the highest MCS rates, such as MCS7 and MCS6 might help reducing packet retransmissions and ensure robust connection during heavy interference.

• To restart the module, the application needs to call rsi_driver_deinit() followed by rsi_driver_init() and rsi_device_init(). For OS cases, additionally call rsi_task_destroy(driver_task_handle) to delete the driver task before calling rsi_driver_deinit() and create again after rsi_device_init() using rsi_task_create()

• Register 'Join Fail Callback' function every time when join is called, as in the rejoin failure path the callback is deregistered. If not done, this might result in a scan not functioning on rejoin failure.

BT/BLE#

• In BLE, recommended range of Connection Interval in

  • Power Save (BLE Only) - 100 ms to 1.28 s.

  • BT Classic + BLE Dual Mode is >= 200 ms.

  • Wi-Fi + BLE coex - 30 ms to 250 ms

• In BLE, during Connection, the configuration of Scan Interval and Scan Window with same value is not recommended.

• In BT Classic, recommended Sniff Interval configuration during Power Save is limited to 100 ms (<= 100).

• In BLE, if a device is acting as Central, the scan window (in set_scan_params and create_connection command) must be less than the existing Connection Interval.

• In BLE mode, if scanning and advertising is in progress and subsequently gets connected and moves to the central role, scanning and advertising stops. To further establish connection to another peripheral device or to a central device, the application should give a command for starting advertising and scanning again.

• Device Power save need to be disabled before BT init and de-init.

Co-Existence#

• For Wi-Fi + BLE, during Wi-Fi connection, lesser BLE scan window and larger BLE scan interval are recommended (1:3 or 1:4).

• Wi-Fi + BLE Advertising

  • All the advertising intervals are supported, as per the BT Spec. If the Wi-Fi transactions are more, you may observe a slight difference in on-air advertisements compared to the configured intervals.

  • BLE Advertising will be stopped for intervals that collide with Wi-Fi activity.

• Wi-Fi + BLE scanning

  • All scan intervals are supported as per BT Spec. For better scan results, use scan-window and scan interval in 1:3 or 1:4 ratio when the Wi-Fi scan activity is present.

  • BLE scanning will be stopped for intervals that collide with Wi-Fi activity.

• Wi-Fi + BLE Central/Peripheral Connections

  • All connection intervals are supported as per BT Spec.

  • For stable connection, use optimal connection intervals and max supervision timeout in the presence of Wi-Fi activity.

• Wi-Fi + BLE Central/Peripheral Data Transfer

  • To get better throughputs in both Wi-Fi and BLE, use medium connection intervals, such as 45 to 80 ms with Maximum supervision timeout.

  • Ensure Wi-Fi activity consumes lesser intervals.

• For Wi-Fi + BT + BLE, Wi-Fi + BT, Wi-Fi + BLE operating modes, connect Wi-Fi ahead of BT/BLE connections to ensure seamless, stable connection for all 3 protocols.

• For Wi-Fi + BT + BLE, Wi-Fi + BT, Wi-Fi + BLE operating modes, if BT/BLE needs to be connected ahead of Wi-Fi connection, use with high supervision timeout and high connection interval for BLE and high sniff interval for BT, to ensure seamless, stable connection. This configuration will also ensure a stable BT/BLE connection when Wi-Fi connects/disconnects/rejoins.

• Wi-Fi + BLE Central/Peripheral data transfer

System#

• For User Store configuration and Configuration Save, do not enable power save or save it as a configuration. If power save is enabled and saved as a configuration, upon boot up, the module will come up with the saved configuration and will go to power save without any indication to the host.

• Set Optimization level to O0 in project settings for IDE (KEIL).

• Memory Configuration must be 384K for BT/BLE and Co-Ex Operating Modes

  • Usage of Low Power Flash mode bit (Bit 19 in Extended customer feature bitmap). Enable this bit for Ultra low power standby associated scenarios. This results in about 20µA lower Wi-Fi standby associated current consumption.

• Memory Configuration in SAPI functions: The default memory configuration is 384K. Users can configure it to 256/320/384kB by changing the macros defined in the below two files

  • In rsi_wlan_config.h : RSI_EXT_CUSTOM_FEATURE_BIT_MAP EXT_FEAT_256K_MODE or EXT_FEAT_320K_MODE or EXT_FEAT_384K_MODE

  • In rsi_common.c : rsi_uint32_to_4bytes(rsi_opermode->ext_custom_feature_bit_map, (EXT_FEAT_256K_MODE (or) EXT_FEAT_320K_MODE (or) EXT_FEAT_384K_MODE | RSI_EXT_CUSTOM_FEATURE_BIT_MAP));

• Apply Opermode commands in AT mode correctly. The wrong opermode in some cases might lead to unspecified behavior.

• Set the recommended Power Save Profile (PSP) type to Enhanced Max PSP for Wi-Fi alone mode and MAX PSP for Wi-Fi Co-Ex Modes.

• Disable power save during firmware upgrade and re-enable on upgrade completion.

• Disable power save for high throughput applications.

• The application needs to ensure that it sets RTC with correct timestamp when the feature is enabled before establishing the SSL connection.

• Timeout value should be minimum 1 second for socket select and socket receive calls. Timeout value less than 1 second is not currently supported.

• For more details, see 'Configuration parameters' in the SAPI Reference Manual.

Known Issues#

Network Stack#

• MQTT disconnects during firmware upgrade using OTAF, when power save is enabled. Disable power save during firmware upgrade and re-enable on upgrade completion.

• Newly Added GCM Based Strong Cipher Suites will have performance issues as Hardware support is not available in the current platform.

• Recommended MQTT Publish payload is 1 kBytes.

• If HTTP Server is configured in the module, MQTT client port should not be port configured on port 80.

• Randomize the client port if using rapid connect/disconnect of the MQTT session on the same client port with the power save.

• Secure SSL Renegotiation not supported in Embedded Networking Stack.

• IPv6 support is not available in this release.

Wi-Fi#

• If the station performs the scan in concurrent mode (Wi-Fi STA+AP), it is possible for stations connected to the AP to get disconnected. Enable AP after STA connection is completed.

• Issue observed with WPA2 Enterprise Connectivity using Microsoft RADIUS Server.

• If BG Scan is enabled along with custom feature bit map bit (8) configuration of the DFS Channel support, issues may occur in getting IP address for the Wi-Fi STA.

BT/BLE#

• Wake on Wireless not supported for BLE.

• BT-HID might not inter-operate with Apple devices.

• In Wi-Fi + BT/BLE Co-Ex mode, high Wi-Fi broadcast traffic might cause BT/BLE disconnections.

• Continuous data transfer on SPP (Rx/Tx) with packet size ~800 bytes in some scenarios might lead to BT disconnection. Introduce delay in between transfers to work around this issue.

• In Wi-Fi + BT mode when there is continuous Wi-Fi data, you might observe BT not re-connecting to remote after disconnection.

• BT-A2DP interoperability issue might be observed with some headsets.

• For BLE, dual role scenario issues might occur when connecting as central if the advertising is also going out for the peripheral role. Central connections can be made after the peripheral connections are established and advertising is stopped.

Co-Existence#

• In Co-Ex Mode if power save is enabled, it stays in enabled state even after Wi-Fi disconnection. Disable power save after every radio_init() and enable it when intended by application.

• BLE may disconnect with Wi-Fi + BLE configuration and Wi-Fi continuous data transfer when the low BLE supervision timeout is configured. When the supervision timeout is configured with the value of 16 seconds, no disconnections are observed.

• WiFi + BLE mode WPS is not working.

• Wi-Fi +BLE/BLE only mode: For SPI as host interface, continuous BLE TX Notification might cause the host interface to hang needing a hardware reset. The issue is not seen with discrete burst BLE data.

• In Wi-Fi + BT/BLE configuration with Wi-Fi disconnects, BT/BLE reconnection issue is observed (see the earlier section 'Recommended Configurations and Application Development options' in this document).

Interoperability#

• QoS Null frames indicating going to Power Save if not acknowledged by AP may cause AP not to sync with the power save state, resulting in Possible disconnections.

• If 3rd Party Access Points are periodically not sending beacons, in some scenarios unicast probe requests are not sent from the module, as expected, which might result in disconnections.

System#

• A known issue exists with FAST-PSP mode. Use Enhanced MAX-PSP power save.

• Wake on Wireless support is tested only for UART AT command interface.

• 802.11b transmit power of some AA0 modules might be 4 dBm less than that mentioned in data sheets. As a result, connectivity issues might be observed at 2.4 GHz when the AP is far.

• Power Save without RAM retention is not working for the SPI interface.

Limitations and Unsupported Features#

Wi-Fi/Network Stack#

• AMSDU TX is not supported.

• Fragmentation is not supported.

• AMSDU's within AMPDU is not supported.

• Currently, the module does not support Radio Measurement Requests feature of CCX V2

• 802.11k is not supported

• Short GI is not supported

• 802.11w is not supported

• 40 MHz bandwidth in 2.4 GHz band is not supported.

• 802.11J channels less than 16 are not supported.

• USB host interface and USB Power save are not supported.

• Total MQTT Command Length, apart from MQTT Publish, should not exceed 150 bytes. This includes at+rsi (start of command) to (end of command)\r\n.

• Configure MQTT_VERSION in rsi_mqtt_client.h based on the server configuration; only version 3 and 4 are supported.

• 3xSSL connections or 1xTCP and 2xSSL connection, connections are supported concurrently in Wi-Fi only mode.

• SSL Curve IDs supported are 15-28. SSL handshake with 3rd party clients depends on the SSL Curve ID.

BT/BLE#

• BT Sniff mode does not work if BT multiple slaves feature is enabled.

• For BLE, if the connection is established with a small connection interval (< 15 ms), simultaneous roles (i.e., Central/Peripheral + Advertising/Scanning) are not supported.

• BLE maximum 2 concurrent connections are supported, which can be either a connection to two peripheral devices or to 1 central and 1 peripheral device.

• For BT Classic, only 1 connection is supported at any time

• BLE Slave latency value is valid up to 32 only.

• BT-A2DP Encoder is not supported in the firmware

• BT-A2DP not supported in AT mode

• User Gain Table API is not available for BT/BLE Path. Limit the BT/BLE TX power for a specific antenna using rsi_bt_set_antenna_tx_power_level API.

Co-Existence#

• In Wi-Fi + BLE during Wi-Fi connection, if both BLE scan interval and window are the same, an issue will occur in successfully making the Wi-Fi connection.

• For AT commands, Wi-Fi + BT + BLE (Opermode 9) B + BLE(Opermode 8) are not working. However, BT, Wi-Fi + BT modes (Opermode 5) works fine. Also, all combinations work fine with SAPI.

• Wi-Fi STA + BT + BLE multiprotocol cases require detailed understanding of use cases and associated configurations. Contact Silicon Labs Support for more details.

• Wi-Fi AP + BLE, Wi-Fi AP + BT & Wi-Fi AP + BT + BLE modes are not supported.

SDK Refactor#

The SDK folder structure and names were significantly changed in the 2.4 release. For detailed information, see SAPI Changelog

Terminology#