| Release Item | Version | Release Date | Release Notes | Key Features | API Changes | Bug Fixes | Chip Enablement |
|---|---|---|---|---|---|---|---|
|
RS9116 Platform |
2.14.0 |
June 2, 2026 |
|
|
|
|
|
|
Wi-Fi |
2.14.0 |
June 2, 2026 |
|
|
|
|
|
|
Network Stack |
2.14.0 |
June 2, 2026 |
|
|
|
|
|
|
Bluetooth |
2.14.0 |
June 2, 2026 |
|
|
|
|
|
|
Multi-Protocol |
2.14.0 |
June 2, 2026 |
|
|
|
|
| Software | Compatible Version or Variant |
|---|---|
| Connectivity firmware |
|
| SAPI | 2.14.0 |
| RTOS | FreeRTOS v11.1.0 |
| Feature Name | Description | Quality | Related API Names | Chip Revision, Hardware, Host Interfaces | Related Example Names |
|---|---|---|---|---|---|
| Wi-Fi Station (STA) | Wi-Fi Station mode with 802.11n support | GA |
|
||
| Wi-Fi Access Point (SoftAP) | Wi-Fi Access Point mode with 802.11n support | GA |
|
||
| Wi-Fi Station (STA) + Access Point (SoftAP) |
Wi-Fi concurrent mode support over the same channel. Station with 802.11n + Access Point with 802.11n |
GA |
|
||
| Wi-Fi Enterprise Client |
Support for EAP-TLS, EAP-TTLS, EAP-FAST, and PEAP security. |
GA |
|
||
| Wi-Fi Transmit Test Mode |
Custom, connection-less testing. |
GA |
|
| Feature Name | Description | Quality | Related API Names | Chip Revision, Hardware, Modes, Host Interfaces | Related Example Names |
|---|---|---|---|---|---|
| IEEE 802.11b/g/n (2.4 GHz and 5 GHz) |
IEEE 802.11b/g/n Wi-Fi standards supported over the 2.4 GHz and 5 GHz band. |
GA |
|
||
| Wi-Fi Multimedia (WMM) Quality of Service (QoS) |
Wi-Fi Multimedia (WMM) Quality of Service (QoS) |
GA |
|
||
| 2.4 GHz Band | See Supported channels on 2.4 GHz band | GA |
|
|
|
| 5 GHz band | See and | GA |
|
|
|
| Wi-Fi Alliance (WFA) Certification |
Pre-testing completed for WFA certification. |
GA |
|
None |
| Feature Name | Description | Quality | Related API Names | Chip Revision, Hardware, Host Interfaces | Related Example Names |
|---|---|---|---|---|---|
| Selective Scan |
Channel-specific scan |
GA |
|
||
| Active / Passive Scan |
Active scanning to send probe requests to discover networks; and passive scanning to listen for beacon frames from access points. |
GA |
|
||
| Background (BG) Scan |
Background scan is a scan triggered after connection in station mode |
GA |
|
| Feature Name | Description | Quality | Related API Names | Chip Revision, Hardware, Modes, Host Interfaces | Related Example Names |
|---|---|---|---|---|---|
| Wi-Fi Re-join |
Enable a device to automatically re-connect to a previously connected wireless network after disconnection. |
GA |
|
Note: This application needs to be modified to check for rejoin. See the Note section of rsi_wlan_connect. |
|
| Wi-Fi Security |
|
GA |
|
| Feature Name | Description | Quality | Related API Names | Chip Revision, Hardware, Modes, Host Interfaces | Related Example Names |
|---|---|---|---|---|---|
| 4-client Support |
Allow up to 4 clients to connect to the access point. |
GA |
|
||
| Hidden SSID Mode |
Prevents a Wi-Fi network’s SSID from being broadcast in beacon frames, making the network name invisible to casual scans. |
GA |
|
Note: Enable CUSTOM_FEAT_AP_IN_HIDDEN_MODE. See the RSI_CUSTOM_FEATURE_BIT_MAP. |
|
| Auto Channel Selection |
Dynamically select the optimal Wi-Fi channel to minimize interference and improve network performance. |
GA |
|
||
| Scan in Access Point Mode |
Wi-Fi scanning in access point mode |
GA |
|
||
| Wi-Fi Security |
|
GA |
|
| Feature Name | Description | Quality | Related API Names | Chip Revision, Hardware, Modes, Host Interfaces | Related Example Names |
|---|---|---|---|---|---|
| Standby Associated |
Standby Associated (connected sleep) with Max Power Save Profile (PSP), Enhanced MAX PSP and Max PSP |
GA |
|
||
| Network Processor (NWP) Deep Sleep |
NWP Deep Sleep with and without RAM retention |
GA |
|
| Feature Name | Description | Quality | Related API Names | Chip Revision, Hardware, Modes, Host Interfaces | Related Example Names |
|---|---|---|---|---|---|
| Wi-Fi AT Command |
Host shall use AT Commands for interacting with RS9116 Module. |
GA |
|
| Feature Name | Description | Quality | Related API Names | Chip Revision, Hardware, Modes, Host Interfaces | Related Example Names |
|---|---|---|---|---|---|
| Core Network Protocols | IPv4, UDP, TCP, ARP, ICMP, ICMPv6 | GA |
|
||
| Internet Protocol version 6 (IPv6) | Connect and exchange data with other hosts using the IPv6 protocol in the networking layer of the network stack. | Beta |
|
||
| TLS Client | Supported versions 1.0, 1.2 | GA |
|
||
| DHCP Client | Support for DHCPv4 and DHCPv6 | Beta |
|
|
|
| DHCP Server | Support for DHCPv4 and DHCPv6 | GA |
|
|
|
| BSD | BSD | GA |
|
| Feature Name | Description | Quality | Related API Names | Chip Revision, Hardware, Modes, Host Interfaces | Related Example Names |
|---|---|---|---|---|---|
| Advanced Network Protocols |
|
GA |
|
||
| mDNS over IPv6 | Host a Multicast Domain Name (mDNS) service over Internet Protocol version 6 (IPv6) to allow other network devices to look up your IPv6 address based on your host name. | Alpha |
|
|
|
| SNTP Client | Retrieve date and time information from an SNTP server. | GA |
|
||
| IGMP | Add the multicast group and exchange multicast data on a UDP socket. | GA |
|
|
| Feature Name | Description | Quality | Related API Names | Chip Revision, Hardware, Modes, Host Interfaces | Related Example Names |
|---|---|---|---|---|---|
| AWS IoT Core | Configure RS9116 as an IoT device and securely connect to the AWS IoT cloud to subscribe and publish on topics using the AWS MQTT library (version 3.1.0). | GA |
|
|
|
| Azure IoT | Configure the RS9116 as an Azure device endpoint, connect, and exchange messages with the Azure IoT Hub. | Beta |
|
|
| Feature Name | Description | Quality | Related API Names | Chip Revision, Hardware, Modes, Host Interfaces | Related Example Names |
|---|---|---|---|---|---|
| BT Classic AT Commands | Host shall use AT Commands for interacting with RS9116 Module. | GA |
|
|
|
| Generic Access Profile (GAP) |
GAP defines how Bluetooth devices discover each other, establish and manage connections, and control access modes (discoverable, connectable, etc.). It governs the fundamental behavior of device interactions, including pairing and authentication. |
GA |
|
|
|
| Serial Port Profile (SPP) |
SPP enables devices to emulate serial port communication over Bluetooth Classic using RFCOMM. It is widely used in industrial, medical, and embedded systems for wireless serial communication between devices like sensors, printers, and terminals. |
GA |
|
|
|
| Secure Simple Pairing (SSP) | Secure Simple Pairing is a feature that simplifies device pairing while providing strong protection against eavesdropping and man-in-the-middle attacks. | GA |
|
|
|
| Advanced Audio Distribution Profile (A2DP) – Source Streaming |
A2DP Source functionality allows the device to stream high-quality stereo audio from a source (e.g., smartphone or embedded device) to a sink (e.g., headphones or speakers) over Bluetooth. It supports standard SBC and optionally other audio codecs. |
GA |
|
|
|
| Audio/Video Remote Control Profile (AVRCP) |
AVRCP functionality allows the device to control audio/video playback remotely over Bluetooth. It supports standard remote control operations such as play, pause, stop, volume control, and track navigation for multimedia applications. |
GA |
|
|
|
| Role Switch |
Role switching allows a Bluetooth device to dynamically change roles between master and slave during an active connection. This is essential for topology flexibility, improved connection robustness, and compliance with role preference requirements in many applications. |
GA |
|
|
|
| Sniff Mode |
Sniff mode is a low-power mode that reduces power consumption by allowing the device to periodically wake up and check for activity. This is particularly important for battery-operated Bluetooth peripherals like keyboards, mice, and remote controls. |
GA |
|
|
|
| Human Interface Device (HID) Profile |
HID allows Bluetooth devices to interact as input devices, such as keyboards, mice, game controllers, or styluses. It supports both interrupt and control channels for low-latency and command communication, making it suitable for consumer electronics and PC peripherals. |
GA |
|
|
|
| Feature Name | Description | Quality | Related API Names | Supported Software Variants, Hardware, Modes, Host Interfaces | Related Example Names |
|---|---|---|---|---|---|
| BLE AT Commands | Host shall use AT Commands for interacting with RS9116 Module. | GA |
|
|
|
| GAP |
Advertising, Scanning, Connection Initiation, Establishment and Bonding Handling of access modes and procedures of the device including device discovery, link establishment, link termination, initiation of security features, and device configuration. |
GA |
|
|
|
| Generic Attribute Protocol (GATT) |
Defines how data is organized and exchanged between devices. It builds on the Attribute Protocol (ATT) by organizing data into hierarchical structures of profiles, services, and characteristics. |
GA |
|
|
|
| Attribute Protocol (ATT) | Fundamental layer responsible for managing data transmission and handling between devices, particularly within the context of the Generic Attribute Profile (GATT) | GA |
|
|
|
| Security |
Security in LE is handled by Security Manager Protocol. The Security Manager (SM) defines the protocol and behavior to manage pairing, authentication and encryption. It uses a key distribution approach to perform identity and encryption functionalities in radio communication. |
GA |
|
|
|
| Human Interface Device (HID) Profile |
HID allows Bluetooth devices to interact as input devices, such as keyboards, mice, game controllers, or styluses. It supports both interrupt and control channels for low-latency and command communication, making it suitable for consumer electronics and PC peripherals. |
GA |
|
|
|
| LL Privacy 1.2 | Enhanced privacy by allowing devices to use temporary, non-identifiable addresses (Resolvable Private Addresses or RPAs) instead of their public identity address | GA |
|
|
|
| Accept List | Feature responsible for restricting connection allowed to a particular BLE device. | GA |
|
|
|
| Directed Advertising | Broadcasting information to a specific device (the scanner) identified by its address. | GA |
|
|
|
| LE PHY and Coded PHY |
LE PHY (1 Mbps, 2 Mbps, 2M PHY): Higher data throughput physical layer (2 Mbps) enabling faster data transfers while maintaining power efficiency for high-bandwidth applications. Coded PHY (125 kbps, 500 kbps): Extended range capability utilizing Forward Error Correction (FEC) allowing connectivity at up to 4x the standard distance in open environments. |
GA |
|
|
|
| LE dual role topology | Demonstrates ability to function as both a central and a peripheral simultaneously on different connections. | GA |
|
|
|
| LE data packet length extensions (DLE) | DLE allows Bluetooth LE devices to transmit data packets with larger payloads, increasing the maximum data rate and potentially improving throughput. | GA |
|
|
|
| Asymmetric PHYs | The concept of asymmetric PHYs is where different PHYs (Physical Layers) are used for transmission (TX) and reception (RX). | GA |
|
|
|
| LE channel selection algorithm 2 (CSA#2) |
The LE channel selection algorithm 2 (CSA#2), also known as Channel Selection Algorithm #2, is a more complex algorithm used to determine the channel index for the next connection event. It is designed to improve channel hopping and minimize interference, especially in high-throughput and high-interference scenarios. |
GA |
|
|
|
| LE Secure connections | LE Secure Connections uses Elliptic-Curve Diffie-Hellman (ECDH) cryptography to generate a public-private key pair. | GA |
|
|
| Feature Name | Description | Quality | Related API Names | Hardware Modules, Hardware Chipsets, Host Interfaces | Related Example Names |
|---|---|---|---|---|---|
| Extended Advertising |
Use secondary advertising channels to offload data that would otherwise be transmitted on the primary advertising channel. Enables multiple sets of advertisements, each with their own data, intervals, duration, address types, filter policies and PHY rates. |
GA |
|
|
|
| Extended Scanning |
Extended scanning allows scanning for different PHY rates and supports different sets of scan interval, scan window, and scan type for each. |
GA |
|
|
|
| Periodic Advertising Synchronization | Periodic Advertising Synchronization in BLE allows multiple devices to wake up and receive data from a single source at the same time, enabling energy-efficient communication and data sharing. | GA |
|
|
|
| Simultaneous scanning on 1 Mbps and Coded PHY | Involves listening for advertisements on both PHYs at the same time. | GA |
|
|
|
| Periodic Advertising | Periodic Advertising enables sending non connectable advertisements at fixed intervals. | GA |
|
|
See example. |
| Periodic Advertising List |
A list of periodic advertising events that provides a schedule or timetable of when a device will send its advertisement data at regular intervals. This allows devices to synchronize with the advertiser and receive data at the specified times, saving power and improving efficiency. |
GA |
|
|
|
| Periodic Advertising Scanning | Scan for periodic advertisements. | GA |
|
|
| Feature Name | Description | Quality | Related API Names | Hardware Modules, Hardware Chipsets, Host Interfaces | Related Example Names |
|---|---|---|---|---|---|
| Wireless Power Save |
|
GA |
|
|
| Feature Name | Description | Quality | Related API Names | Chip Revision, Hardware, Modes, Host Interfaces | Related Example Names |
|---|---|---|---|---|---|
| Wi-Fi Station (STA) + BT Mode |
Co-existence of Wi-Fi Station (STA) mode and Bluetooth (BT) on the same radio, supporting complex use cases with minimal interference. This solution is built on a Time Division Multiplexing (TDM) architecture that schedules radio access between Wi-Fi and BT with optimal performance. |
GA |
|
Note: This release does not include a standalone Wi-Fi + BT example. To use the Wi-Fi + BT + BLE examples for Wi-Fi + BT functionality only, disable the RSI_ENABLE_BLE_TEST macro. |
|
| Wi-Fi Station (STA) + BLE Mode |
Co-existence of Wi-Fi STA mode and BLE on the same radio, supporting complex use cases with minimal interference. This solution is built on a TDM architecture that schedules radio access between Wi-Fi and BLE with optimal performance. |
GA |
|
||
| Wi-Fi + BLE PTA 3-wire Co-existence |
Enable connecting two devices via GPIOs, with Wi-Fi as primary and external BLE as secondary, ensuring better performance on the same radio without interference. The solution relies on a radio-sharing mechanism using request, priority, and grant signals. The PTA secondary manages the request and priority, while the PTA primary handles the grant to ensure optimal performance without interference. |
GA |
Note: Flow control must be disabled to support PTA in NCP mode. |
||
| Wi-Fi + Zigbee / OpenThread PTA 3-wire Co-existence |
Enable connecting two devices via GPIOs, with Wi-Fi as primary and external Zigbee or OpenThread as secondary, ensuring better performance on the same radio without interference. The solution relies on a radio-sharing mechanism using request, priority, and grant signals. The PTA secondary manages the request and priority, while the PTA primary handles the grant to ensure optimal performance without interference. |
GA |
Note: Flow control must be disabled to support PTA in NCP mode. |
||
| Wi-Fi STA + BT + BLE Co-existence |
Co-existence of Wi-Fi Station (STA) mode, classic Bluetooth and Bluetooth Low Energy (BLE) on the same radio, supporting complex use cases with minimal interference. This solution is built on a Time Division Multiplexing (TDM) architecture that schedules radio access between Wi-Fi and BLE with optimal performance. |
GA |
|
| Feature Name | Description | Quality | Related API Names | Chip Revision, Hardware, Modes, Host Interfaces | Related Example Names |
|---|---|---|---|---|---|
| Firmware Loading through UART and SPI |
Load firmware via ISP using UART interface or SPI interface. |
GA |
|
||
| Secure Over-the-Air (OTA) Update |
Perform OTA firmware update via Wi-Fi from a remote HTTP/HTTPS server. |
GA |
|
| Feature Name | Description | Quality | Related API Names | Chip Revision, Hardware, Modes, Host Interfaces | Related Example Names |
|---|---|---|---|---|---|
| Store configuration |
Store the profile information in the flash, so that it can be used for consecutive connection or reconnection. |
GA |
|
||
| Auto join. |
Auto join to the profile stored using store configuration. |
GA |
|
None |
| ID | Issue Description | GitHub / Salesforce Reference (if any) | Affected Chip Revision, Hardware, Host Interfaces |
|---|---|---|---|
| 1599779 | Fixed LP GPIO based wakeup powersave issue. | None |
|
| ID | Issue or Limitation Description | GitHub / Salesforce Reference (if any) | Workaround (if any) | Affected Chip Revision, Hardware, Host Interfaces |
|---|---|---|---|---|
| 1502403 | When coexistence (coex) is configured, the RS9116 may enter powersave mode before the configured monitor interval for inactivity. | None | None |
|
| 1502453 | The FTP client application does not work with EFx32/STM32 when an RTOS is used. | None | None |
|
| 1502452 | The HTTP OTA update application does not work with EFR32 and EFM32 when an RTOS is used. | None | None |
|
| 1502446 | Firmware update does not work for the EFM32 platform. | None | None |
|
| 1502450 | SAPI driver with the UART host interface is only supported on bare metal. | None | None |
|
| 1502400 | Powersave without RAM retention does not work when the SPI interface is used. | None | None |
|
| 1077954 | MQTT receive may encounter failures in STA + AP concurrent mode. | None | None |
|
| 1221686 | On the EFM platform, standby-associated listen interval current consumption is higher than expected. | None | None |
|
| 1557514 | USB-CDC enumeration has an issue with USB 1.1. Although the negotiated maximum packet size is 512 bytes, only 64‑byte operation is successful. | None | None |
|
| ID | Issue Description | GitHub / Salesforce Reference (if any) | Affected Chip Revision, Hardware, Host Interfaces |
|---|---|---|---|
| 1581054 | EAP-TLS Client Does Not Send Complete Certificate Chain During Mutual Authentication. | None |
|
| 1528028 | Improve RSI_CFG_GET Error Message for Missing Configuration. | None |
|
| 1589922 | Socket termination due to GARP failure from RS9116. | None |
|
| 1535421 | Beacon drops should not be seen in power save mode in 5 GHz | None |
|
| ID | Issue or Limitation Description | GitHub / Salesforce Reference (if any) | Workaround (if any) | Affected Chip Revision, Hardware, Host Interfaces |
|---|---|---|---|---|
| 1582409 | Station forward compatibility with APs advertising various AKMs in the RSN IE is currently failing. | None | None |
|
| 1638284 | The PTK reinstallation test with a random ANonce in the 4-way handshake is passing functionally, but the certification suite is reporting an incorrect failure status. | None | None |
|
| 1484360 | The new cipher suites ECDHE-RSA-AES256-SHA and ECDHE-RSA-AES128-SHA are not recognized in the latest versions of radisus server. | None | None |
|
| 1592218 | WPA3_Personal and WPA2_Enterprise with wrong PSK is triggering Timeout callback handler. | None | None |
|
| NA | WPA3 Connection with Hunting and Pecking algorithm takes about three to four seconds. | None | None |
|
| NA | If the station performs a scan in concurrent mode (Wi-Fi STA + AP), stations connected to the AP may be disconnected. Enable AP after the STA connection is completed. | None | None |
|
| NA | With powersave, PTA 3-wire co-existence does not work. However, if a weak pull-up is applied on the GRANT pin, the PTA 3-wire functionality works while the power is saved. For further information, refer to Application Notes. | None | None |
|
| NA | EAP security in the aws_device_shadow application is unsupported on the EFR platform due to memory constraints. | None | None |
|
| NA | In STA + AP, if AP started first station scan is supported only in channel in which AP is brought up. If multiple channel scan is requested, AP behaviour is undefined. | None | None |
|
| NA | Auto channel selection is not supported in AP mode when the EXT_FEAT_IEEE_80211J feature is enabled. | None | None |
|
| 1250359, 1532130 | This build is not WFA-certifiable due to RSNO and WMM issues; fixes are planned for the next release. | None | None |
|
| NA | In Wi-Fi client mode, disconnections may occur if the AP does not acknowledge QoS null frames when powersave is enabled. | None | None |
|
| 1535439 | Observed repeated beacon misses every 5 seconds when using 1.4A7 board 5G band. | None | None |
|
| NA | During mutual authentication in EAP‑TLS, the client transmits both the leaf and intermediate certificates to the server only when using combined certificate chain loading. Intermediate certificate support is not available in individual certificate loading. | None | None |
|
| ID | Issue Description | GitHub / Salesforce Reference (if any) | Affected Chip Revision, Hardware, Host Interfaces |
|---|---|---|---|
| 1588871 | Fixed MQTT publish failure (0x0030 / TX_DATA_PACKET_SIZE_EXCEEDED) for MQTT topics exceeding 99 bytes in AT mode. | None |
|
| 1534531 | Fixed SNTP subcommands returning 0xFFF8 (ERROR_IN_CMD) and resolved stale time reporting in SNTP_CLIENT_GET_TIME in AT mode. | None |
|
| 1639460 | Fixed WLAN initialization failure in the wlan_https_bt_spp_ble_dual_role_v6 example when WPA3-Personal is enabled along with 802.11W (PMF). | None |
|
| 1635489 | Fixed DUT hang and missing BLE advertise/scan packets over the air in the wlan_throughput_bt_spp_ble_dual_role application. | None |
|
| 1600627 | Fixed AWS publish failures with power save enabled in the wlan_station_ble_provisioning_aws application. | None |
|
| 1603789 | Corrected the documented security_type values for the rsi_wlan_ap_start() API to match the actual supported security modes. | None |
|
| 1347675 | Added a readme for the wlan_ble_power_save example. | None |
|
| 1616763 | Updated the RSI_IP_TOS value table to match the IEEE 802.11e / WMM Access Category mapping. | None |
|
| 1603928 | Fixed IP configuration failure (error code 0x21) observed in the station_ping example when CONNECT_WITH_PMK was enabled, by documenting the required SECURITY_TYPE setting (RSI_WPA2_PMK). | None |
|
| 1543833 | Updated the HTTP GET and HTTP PUT documentation to clarify SNI usage, custom cipher suite configuration, and the required parameter sequence. | None |
|
| 1498081 | Replaced the Silabs Connect mobile app with the Simplicity Connect app in the wlan_station_ble_provisioning example for compatibility with the latest Android versions. | None |
|
| 1453571 | Documented the upper and lower limits of the MQTT keep_alive_interval parameter in the rsi_emb_mqtt_client_init API. | None |
|
| 1649389 | Fixed BLE disconnection issues observed during HTTP GET operation in BLE + WLAN coexistence mode over the UART interface. | None |
|
| ID | Issue or Limitation Description | GitHub / Salesforce Reference (if any) | Workaround (if any) | Affected Chip Revision, Hardware, Host Interfaces |
|---|---|---|---|---|
| NA | Embedded MQTT does not support reassembly of fragmented MQTT packets. MQTT transactions may fail if fragmented packets are received from the broker. | None | None |
|
| NA | TLS handshakes may occasionally fail due to incorrect ECC curve parameter generation, resulting in a BBD2 error. The issue resolves on the next attempt. | None | None |
|
| NA | MQTT disconnects may occur during firmware updates if powersave is enabled. Disable powersave during the update and re-enable it after completion. | None | None |
|
| NA | All GCM-based cipher suites are software-implemented and may exhibit limited performance. | None | None |
|
| NA | The recommended MQTT publish payload is 1 kB. | None | None |
|
| NA | If HTTP server functionality is enabled, do not use port 80 for the MQTT client. | None | None |
|
| NA | Randomize the client port if using rapid connect/disconnect of the MQTT session on the same client port with powersave. | None | None |
|
| NA | Secure TLS renegotiation is not supported in the embedded networking stack. | None | None |
|
| NA | In WPA2 enterprise security mode, getting wireless statistics using rsi_wlan_get() API has restrictions. | None | None |
|
| NA | The wlan_throughput_bt_spp_ble_dual_role example is not supported on bare metal platforms. | None | None |
|
| NA | In concurrent mode, communication loss could occur on the STA application when, simultaneously, multiple clients are connected to the APUT. | None | None |
|
| NA | IP address conflict detection has limitations in STA + AP concurrent mode, and failures are not reported to host. | None | None |
|
| NA | mqtt_client and mqtt_client_v6 applications do not support the SDIO host interface. | None | None |
|
| NA | If a corrupted firmware image is received during OTA updates via TCP/HTTP, the module may become unresponsive on the next bootup. | None | None |
|
| NA | TLS connection problems may occur when attempting to revoke public and private keys using existing keys. | None | None |
|
| NA | Observed inconsistencies in TCP and UDP RX throughput in AP-alone mode. | None | None |
|
| NA | Observed that a duplicate IPv6 address is assigned to multiple STAs in AP mode. | None | None |
|
| NA | Ping timeouts may occur when configured with a 1-second timeout. | None | None |
|
| NA | Applications using the USB interface support Wi-Fi-only, Wi-Fi + BLE, and Wi-Fi + BTC modes. The Wi-Fi + BLE + BTC coexistence mode is not supported in OS-enabled (Linux) environments and is limited to bare-metal and FreeRTOS only. | None | None |
|
| NA | Command-based soft reset using the USB interface is not supported. The application must perform a chip reset. | None | None |
|
| NA | ULP Power Save mode is not supported. | None | None |
|
| 1557290 | TCP TX/RX throughput may be ~30% lower than UDP. | None | None |
|
| 1629919 | HTTP GET requests fail when downloading large files (~1 MB) on RS9116W in UART + SAPI mode. | None | None |
|
| 1649047 | In STA + BLE coexistence throughput scenarios, UDP RX and TCP RX operations fail when Robust Mode is enabled. | None | None |
|
| 1648571 | UDP TX throughput operations fail in STA + BLE coexistence mode, irrespective of whether Robust Mode is enabled or disabled. | None | None |
|
| 1648555 | SSL TX and SSL RX throughput operations yield no data transfer in the STA + BLE coexistence throughput application, irrespective of whether Robust Mode is enabled or disabled. | None | None |
|
| ID | Issue Description | GitHub / Salesforce Reference (if any) | Affected Chip Revision, Hardware, Host Interfaces |
|---|---|---|---|
| 1601307 | Fixed an issue where the peripheral disconnected immediately when reading coded PHY rates on A7 boards with power save enabled, occurring only when LE Coded PHY (LR) was configured. | None |
|
| 1614985 | Fixed a hang issue that occurred when a connection cancel request was triggered with an invalid remote BD address. | None |
|
| 1378574, 1596704 | Repeated passkey strings occur when the RS9116 module operates as a peripheral with power-save functionality during multiple reconnection iterations. | None |
|
| 1354933 | Fixed the BLE re-pairing attack vulnerability by adding a new API, rsi_ble_vendor_set_SMP_min_enc_keysize, which sets the minimum encryption key size (typically 7–16). | None |
|
| ID | Issue or Limitation Description | GitHub / Salesforce Reference (if any) | Workaround (if any) | Affected Chip Revision, Hardware Modules, Host Interfaces |
|---|---|---|---|---|
| 1633218 | When the RC clock is enabled, the DUT stops BLE advertising at –20 °C. This issue is observed only on the A7 board. | None | None |
|
| 1533268 | BTC and BLE Power Save is not supported with the USB interface. | None | None |
|
| None | The 9116 uses a software-based HRNG for BLE operations because the on-chip Hardware Random Number Generator (HRNG) may exhibit limited entropy or repeated output patterns under certain operating conditions. | None | None |
|
| ID | Issue or Limitation Description | GitHub / Salesforce Reference (if any) | Workaround (if any) | Affected Chip Revision, Hardware, Host Interface |
|---|---|---|---|---|
| NA | In Wi-Fi + BLE mode, BLE may disconnect if the supervision timeout is set below 16 seconds. | None | None |
|
| NA | WPS is not supported. | None | None |
|
| NA | In Wi-Fi + BLE or BLE-only modes, BT/BLE reconnection issues may occur when Wi-Fi disconnects. | None | None |
|
| 1215476 | In Wi-Fi + BT mode, Wi-Fi throughput logs are not displayed in serial terminals (for example, TeraTerm) when BT SPP is connected using the wlan_bt_throughput_app demo. | None | None |
|
| NA | In Wi-Fi + BT/BLE CoEx mode, high Wi-Fi broadcast traffic may cause BT/BLE disconnections. | None | None |
|
| NA | In Wi-Fi + BT mode, continuous Wi-Fi data may prevent BT from reconnecting after disconnection. | None | None |
|
| NA | In Wi-Fi + BLE mode, Wi-Fi connection attempts may be unsuccessful when the BLE scan interval and scan window parameters are equal. | None | None |
|
| NA |
In Wi-Fi + AE Coexistence:
|
None | None |
|
| NA | Wi-Fi STA + BT + BLE multiprotocol use cases requires a detailed understanding of the use cases and associated configurations. Contact Silicon Labs support for additional details. | None | None |
|
| Type | Direction | Argument Name | Description |
|---|---|---|---|
| uint32_t | [in] | code | - Configuration code. The possible values are as below: - XO_CTUNE_FROM_HOST: used to configure NWP's XO Ctune value. - SET_XTAL_GOOD_TIME_FROM_HOST: used to configure XTAL(crystal) good time. - SET_PMU_GOOD_TIME_FROM_HOST: used to configure PMU good time. |
| uint16_t | [in] | value | - Value to be configured |Code|Value Range| |---|---| |XO_CTUNE_FROM_HOST|0 - 255| |SET_XTAL_GOOD_TIME_FROM_HOST|2000µs - 10000µs| |SET_PMU_GOOD_TIME_FROM_HOST|1100µs - 2000µs| |
| Type | Direction | Argument Name | Description |
|---|---|---|---|
| uint16_t | [in] | flags | - Select version and security |Flags|Macro|Description| |---|---|---| |BIT(0)|RSI_IPV6|Set this bit to enable IPv6 , by default it is configured to IPv4| |BIT(1)|RSI_SSL_ENABLE|Set this bit to enable SSL feature| |BIT(2)|RSI_SSL_V_1_0|Set this bit to support SSL TLS Version 1.0 if HTTPS is enabled| |BIT(3)|RSI_SSL_V_1_2|Set this bit to support SSL_TLS Version 1.2 if HTTPS is enabled| |BIT(4)|RSI_SSL_V_1_1|Set this bit to support SSL_TLS Version 1.1 if HTTPS is enabled| |BIT(5)|HTTP_POST_DATA|Set this bit to enable Http_post large data feature| |BIT(6)|HTTP_V_1_1|Set this bit to use HTTP version 1.1| |BIT(9)|HTTPS_CERT_INDEX_1|Set this bit to indicate certificate at index 1 to be used for HTTPS| |BIT(10)|HTTPS_CERT_INDEX_2|Set this bit to indicate certificate at index 2 to be used for HTTPS| |
| uint8_t * | [in] | ip_address | - Server IP address |
| uint16_t | [in] | port | - Port number, default : 80 - HTTP, 443 - HTTPS |
| uint8_t * | [in] | resource | - URL string for requested resource |
| uint8_t * | [in] | host_name | - Host name |
| uint8_t * | [in] | extended_header | - Extender header if present |
| uint8_t * | [in] | user_name | - Username for server Authentication |
| uint8_t * | [in] | password | - Password for server Authentication |
| void(*)(uint16_t status, const uint8_t *buffer) | [in] | http_otaf_response_handler | - Callback is called when asynchronous response is received from module for HTTP firmware update request |
| [out] | status | - Status code | |
| [out] | buffer | - NULL |
| Type | Direction | Argument Name | Description |
|---|---|---|---|
| uint8_t | [in] | enable | - Enable, BIT map for Enable ```c 0 - Enable Periodic Advertising \n 1 - Include the ADI field in AUX_SYNC_IND PDUs \n handle - Advertising_Handle - Used to Identify an Advertsing Set \n ``` |
| uint8_t | N/A | handle |
| Type | Direction | Argument Name | Description |
|---|---|---|---|
| uint8_t | [in] | mqtt_flags | - Network flags. Each bit in the flag has its own significance |Flags|Description| |---|---| |BIT(6) - pwdFlag|1 - Enable pwdFlag | |0 - Disable pwdFlag| |BIT(7) - usrFlag|1 - Enable usrFlag | |0 - Disable usrFlag| |
| int8_t * | [in] | will_topic | - Will topic that the MQTT client wants the MQTT Server to publish when disconnected unexpectedly. |
| uint16_t | [in] | will_message_len | - Length of will message |
| int8_t * | [in] | will_message | - Will message issued by the MQTT Server for a broken client. |
| Type | Direction | Argument Name | Description |
|---|---|---|---|
| uint32_t | N/A | callback_id | If it's a Success - RSI_SUCCESS, else the possible error response codes are 0x0021, 0xFF74, 0xFF40, 0xFF87. |
| void(*)(uint16_t status, uint8_t *buffer, const uint32_t length) | [in] | call_back_handler_ptr | - Callback function pointer |
| [out] | status | - Success - RSI_SUCCESS. Failure - Possible error codes are : 0x0030, 0x0036, 0x0065, 0xBBF1, 0xBBF2, 0xBBF3, 0xFFF6 |
|
| [out] | buffer | - Pointer to buffer which holds data |
|
| [out] | length | - Length of the buffer - ### Prototypes of the callback functions with given callback id ### |Callback id|Function Description| |---|---| |RSI_WLAN_NWK_EMB_MQTT_REMOTE_TERMINATE_CB|Called to notify the remote termination of embedded MQTT socket | || |
| Type | Direction | Argument Name | Description |
|---|---|---|---|
| int32_t | [in] | sockID | - Socket descriptor ID |
| int | [in] | level | - Set the socket option, take the socket level |
| int | [in] | option_name | - Provide the name of the ID. SO_MAXRETRY - To Enable max tcp retry count SO_SOCK_VAP_ID - To Configure the socket VAP ID. VAP ID to differentiate between station and AP in concurrent mode. 0 – for station, 1 – for Access point SO_TCP_KEEP_ALIVE - To configure the TCP keep alive (initial time in seconds) SO_RCVBUF - To configure the application buffer for receiving server certificate SO_SSL_ENABLE - To open an SSL/TLS connection over TCP socket. By default supports versions of both TLS 1.0 and TLS 1.2 SO_SSL_V_1_0_ENABLE - To open an SSL/TLS connection over TCP socket with TLS version 1.0 SO_SSL_V_1_1_ENABLE - To open an SSL/TLS connection over TCP socket with TLS version 1.1 SO_SSL_V_1_2_ENABLE - To open an SSL/TLS connection over TCP socket with TLS version 1.2 SO_TCP_ACK_INDICATION - To enable tcp ack indication feature SO_CERT_INDEX - To enable set certificate index SO_HIGH_PERFORMANCE_SOCKET - To Configure the high performance socket SO_TCP_MSS - To Configure the tcp mss SO_TCP_RETRY_TRANSMIT_TIMER - To Configure the tcp retry transmit timer SO_TLS_SNI - To Configure the TLS SNI extension SO_RCVTIMEO - To configure the socket-receive timeout using this option. If no data is received within this time, the sapi driver will unblock this API. SO_CHECK_CONNECTED_STATE - To check for the connected state IP_TOS - To configure the type of service value [0-7] |User Priority (UP)|Value Description|Access Category (AC)| |---|---|---| |0|Best Effort (default)|AC_BE| |1|Background|AC_BK| |2|Spare / Background|AC_BK| |3|Excellent Effort|AC_BE| |4|Controlled Load|AC_VI| |5|Video|AC_VI| |6|Voice|AC_VO| |7|Network Control|AC_VO| |
| const void * | [in] | option_value | - Value of the parameter |
| rsi_socklen_t | [in] | option_len | - Length of the parameter |
| Type | Direction | Argument Name | Description |
|---|---|---|---|
| nw_app_protocol | [in] | protocol | - The following table lists in below |Protocol|Value| |---|---| |RSI_HTTP|0| |
| nw_app_config | [in] | config_type | - The following table lists in below |config_type|Value| |---|---| |RSI_CIPHER_SELECTION|0| |
| void * | [in] | config | - The following table lists in below |Protocol|config_type|config| |---|---|---| |RSI_HTTP|RSI_CIPHER_SELECTION|Configure the Cipher values as explained on the [SSL/TLS Cipher Selection](ssl-ciphers-selection) page.| |
| uint16_t | [in] | config_length | - Length of the config parameter |
| Type | Direction | Argument Name | Description |
|---|---|---|---|
| uint16_t | [in] | flags | - Network flags. Each bit in the flag has its own significance |Flags|Description| |---|---| |BIT(0) - RSI_IPV6|Set this bit to enable IPv6. By default, it is configured to IPv4| |BIT(1) to BIT(15)|Reserved for future use| |
| int8_t * | [in] | server_ip | - FTP server IP address to connect |
| int8_t * | [in] | username | - Username for server authentication |
| int8_t * | [in] | password | - Password for server authentication |
| uint32_t | [in] | server_port | - Port number of FTP server |
| Type | Direction | Argument Name | Description |
|---|---|---|---|
| uint16_t | [in] | flags | - Network flags. |Flags|Description| |---|---| |BIT(0) - RSI_IPV6|Set this bit to enable IPv6. By default, it is configured to IPv4| |BIT(1) to BIT(15)|Reserved for future use| |
| int8_t * | [in] | file_content | - Data stream to be written into the file |
| int16_t | [in] | content_length | - File content length |
| uint8_t | [in] | end_of_file | - Flag that indicates the end of file. 1 – Represent the end of content to be written into the file, 0 – Extra data that is pending to write into the file |
| Type | Direction | Argument Name | Description |
|---|---|---|---|
| uint16_t | [in] | flags | - Select version and security |Flags|Macro|Description| |---|---|---| |BIT(0)|RSI_IPV6|Set this bit to enable IPv6, by default it is configured to IPv4| |BIT(1)|RSI_SSL_ENABLE|Set this bit to enable SSL featuree| |BIT(2)|RSI_SSL_V_1_0|Set this bit to support SSL TLS Version 1.0 if HTTPS is enabled| |BIT(3)|RSI_SSL_V_1_2|Set this bit to support SSL_TLS Version 1.2 if HTTPS is enabled| |BIT(4)|RSI_SSL_V_1_1|Set this bit to support SSL_TLS Version 1.1 if HTTPS is enabled| |BIT(5)|HTTP_POST_DATA|Set this bit to enable Http_post large data feature| |BIT(6)|HTTP_V_1_1|Set this bit to use HTTP version 1.1| |BIT(8)|RSI_SSL_V_1_3|Set this bit to support SSL_TLS Version 1.3 if HTTPS is enabled| |BIT(9)|HTTPS_CERT_INDEX_1|Set this bit to indicate certificate at index 1 to be used for HTTPS| |BIT(10)|HTTPS_CERT_INDEX_2|Set this bit to indicate certificate at index 2 to be used for HTTPS| |BIT(11)|RSI_HTTPS_USE_SNI|Enable this to utilize the SNI extension for HTTPS socket provided by [rsi_set_sni_emb_socket()](network9#rsi-set-sni-emb-socket)| |
| uint8_t * | [in] | ip_address | - Server IP address |
| uint16_t | [in] | port | - Port number of HTTP server |
| uint8_t * | [in] | resource | - URL string for requested resource |
| uint8_t * | [in] | host_name | - Host name |
| uint8_t * | [in] | extended_header | - User-defined extended header, each member header should end by \r`\n` |
| uint8_t * | [in] | user_name | - Username for server authentication |
| uint8_t * | [in] | password | - Password for server authentication |
| #if RSI_HTTP_STATUS_INDICATION_EN void(*)(uint16_t status, const uint8_t *buffer, const uint16_t length, const uint32_t moredata, uint16_t status_code) http_client_response_handler #else void(*)(uint16_t status, const uint8_t *buffer, const uint16_t length, const uint32_t moredata) http_client_response_handler # | [in] | endif | - Callback when asynchronous response comes for the request |
| [out] | status | - Status of response from module. This will return failure upon an internal error only. | |
| [out] | buffer | - Buffer pointer | |
| [out] | length | - Length of data | |
| [out] | more_data | - 1 No more data, 0 More data present |
|
| [out] | status_code | - HTTP response code as returned by server in HTTP header. e.g., 200, 201, 404, etc. This field is valid only when status field (first argument) is successful, indicating a response is received from HTTP server. A status_code equal to 0 indicates that there was no HTTP header in the received packet, probably a continuation of the frame body received in the previous chunk. This field is available, if the feature RSI_HTTP_STATUS_INDICATION_EN is enabled in rsi_wlan_config.h |
| Type | Direction | Argument Name | Description |
|---|---|---|---|
| uint16_t | [in] | flags | - Select version and security |Flags|Macro|Description| |---|---|---| |BIT(0)|RSI_IPV6|Set this bit to enable IPv6, by default, it is configured to IPv4| |BIT(1)|RSI_SSL_ENABLE|Set this bit to enable SSL feature| |BIT(2)|RSI_SSL_V_1_0|Set this bit to support SSL TLS Version 1.0 if HTTPS is enabled| |BIT(3)|RSI_SSL_V_1_2|Set this bit to support SSL_TLS Version 1.2 if HTTPS is enabled| |BIT(4)|RSI_SSL_V_1_1|Set this bit to support SSL_TLS Version 1.1 if HTTPS is enabled| |BIT(5)|HTTP_POST_DATA|Set this bit to enable Http_post large data feature| |BIT(6)|HTTP_V_1_1|Set this bit to use HTTP version 1.1| |BIT(8)|RSI_SSL_V_1_3|Set this bit to support SSL_TLS Version 1.3 if HTTPS is enabled| |BIT(9)|HTTPS_CERT_INDEX_1|Set this bit to indicate certificate at index 1 to be used for HTTPS| |BIT(10)|HTTPS_CERT_INDEX_2|Set this bit to indicate certificate at index 2 to be used for HTTPS| |BIT(11)|RSI_HTTPS_USE_SNI|Enable this to utilize the SNI extension for HTTPS socket provided by [rsi_set_sni_emb_socket()](network9#rsi-set-sni-emb-socket)| |
| uint8_t * | [in] | ip_address | - Server IP address |
| uint16_t | [in] | port | - Port number of HTTP server |
| uint8_t * | [in] | resource | - URL string for requested resource |
| uint8_t * | [in] | host_name | - Host name |
| uint8_t * | [in] | extended_header | - User-defined extended header, each member header should end by \r`\n` |
| uint8_t * | [in] | user_name | - Username for server authentication |
| uint8_t * | [in] | password | - Password for server authentication |
| uint8_t * | [in] | post_data | - HTTP data to be posted to server |
| uint32_t | [in] | post_data_length | - Post data length |
| #if RSI_HTTP_STATUS_INDICATION_EN void(*)(uint16_t status, const uint8_t *buffer, const uint16_t length, const uint32_t moredata, uint16_t status_code) http_client_response_handler #else void(*)(uint16_t status, const uint8_t *buffer, const uint16_t length, const uint32_t moredata) http_client_response_handler # | [in] | endif | - Callback when asynchronous response comes for the request |
| [in] | status | - Status of response from module. This will return failure upon an internal error only. | |
| [in] | buffer | - Buffer pointer | |
| [in] | length | - Length of data | |
| [in] | moredata | - 1 No more data, 0 More data present, 2 HTTP post success response | |
| [in] | status_code | HTTP response code as returned by server in HTTP header. e.g., 200, 201, 404, etc. This field is valid only when status field (first argument) is successful, indicating a response is received from HTTP server. A status_code equal to 0 indicates that there was no HTTP header in the received packet, probably a continuation of the frame body received in the previous chunk. This field is available, if the feature RSI_HTTP_STATUS_INDICATION_EN is enabled in rsi_wlan_config.h |
| Type | Direction | Argument Name | Description |
|---|---|---|---|
| uint8_t | [in] | type | - 0 RSI_HTTP_GET, 1 RSI_HTTP_POST |
| uint16_t | [in] | flags | - Select version and security |Flags|Macro|Description| |---|---|---| |BIT(0)|RSI_IPV6|Set this bit to enable IPv6, by default, it is configured to IPv4| |BIT(1)|RSI_SSL_ENABLE|Set this bit to enable SSL feature| |BIT(2)|RSI_SSL_V_1_0|Set this bit to support SSL TLS Version 1.0 if HTTPS is enabled| |BIT(3)|RSI_SSL_V_1_2|Set this bit to support SSL_TLS Version 1.2 if HTTPS is enabled| |BIT(4)|RSI_SSL_V_1_1|Set this bit to support SSL_TLS Version 1.1 if HTTPS is enabled| |BIT(5)|HTTP_POST_DATA|Set this bit to enable Http_post large data feature| |BIT(6)|HTTP_V_1_1|Set this bit to use HTTP version 1.1| |BIT(8)|RSI_SSL_V_1_3|Set this bit to support SSL_TLS Version 1.3 if HTTPS is enabled| |BIT(9)|HTTPS_CERT_INDEX_1|Set this bit to indicate cert at index 1 to be used for HTTPS| |BIT(10)|HTTPS_CERT_INDEX_2|Set this bit to indicate cert at index 2 to be used for HTTPS, Leave both unset for cert index 0| |BIT(11)|RSI_HTTPS_USE_SNI|Enable this to utilize the SNI extension for HTTPS socket provided by [rsi_set_sni_emb_socket()](network9#rsi-set-sni-emb-socket)| |
| uint8_t * | [in] | ip_address | - Server IP address |
| uint16_t | [in] | port | - Port number of HTTP server |
| uint8_t * | [in] | resource | - URL string for requested resource. Note: HTTP server port is also configurable on a non-standard port |
| uint8_t * | [in] | host_name | - Host name |
| uint8_t * | [in] | extended_header | - User-defined extended header, each member header should end by \r`\n` |
| uint8_t * | [in] | user_name | - Username for server authentication |
| uint8_t * | [in] | password | - Password for server authentication |
| uint8_t * | [in] | post_data | - HTTP data to be posted to server |
| uint32_t | [in] | post_data_length | - This is the post data length |
| #if RSI_HTTP_STATUS_INDICATION_EN void(*)(uint16_t status, const uint8_t *buffer, const uint16_t length, const uint32_t moredata, uint16_t status_code) callback #else void(*)(uint16_t status, const uint8_t *buffer, const uint16_t length, const uint32_t moredata) callback # | [in] | endif | - Callback when asynchronous response comes for the request |
| [out] | status | - Status of response from module. This will return failure upon an internal error only. | |
| [out] | buffer | - Buffer pointer | |
| [out] | length | - Length of data | |
| [out] | moredata | - 1 - No more data, 0 - More data present | |
| [in] | status_code | HTTP response code as returned by server in HTTP header. e.g., 200, 201, 404, etc. This field is valid only when status field (first argument) is successful, indicating a response is received from HTTP server. A status_code equal to 0 indicates that there was no HTTP header in the received packet, probably a continuation of the frame body received in the previous chunk. This field is available, if the feature RSI_HTTP_STATUS_INDICATION_EN is enabled in rsi_wlan_config.h. |
| Type | Direction | Argument Name | Description |
|---|---|---|---|
| uint16_t | [in] | flags | - Select version and security |Flags|Macro|Description| |---|---|---| |BIT(0)|RSI_IPV6|Set this bit to enable IPv6, by default, it is configured to IPv4| |BIT(1)|RSI_SSL_ENABLE|Set this bit to enable SSL feature| |BIT(2)|RSI_SSL_V_1_0|Set this bit to support SSL TLS Version 1.0 if HTTPS is enabled| |BIT(3)|RSI_SSL_V_1_2|Set this bit to support SSL_TLS Version 1.2 if HTTPS is enabled| |BIT(4)|RSI_SSL_V_1_1|Set this bit to support SSL_TLS Version 1.1 if HTTPS is enabled| |BIT(5)|HTTP_POST_DATA|Set this bit to enable Http_post large data feature| |BIT(6)|HTTP_V_1_1|Set this bit to use HTTP version 1.1| |BIT(7)|HTTP_USER_DEFINED_CONTENT_TYPE|Set this bit to enable user defined http_content type| |BIT(9)|HTTPS_CERT_INDEX_1|Set this bit to indicate certificate at index 1 to be used for HTTPS| |BIT(10)|HTTPS_CERT_INDEX_2|Set this bit to indicate certificate at index 2 to be used for HTTPS| |
| uint8_t * | [in] | ip_address | - Server IP address |
| uint32_t | [in] | port_number | - Port number of HTTP server |
| uint8_t * | [in] | resource | - URL string for requested resource |
| uint8_t * | [in] | host_name | - Host name |
| uint8_t * | [in] | extended_header | - User-defined extended header, each member header should end by \r`\n` |
| uint8_t * | [in] | user_name | - Username for server authentication |
| uint8_t * | [in] | password | - Password for server authentication |
| uint32_t | [in] | content_length | - Total length of HTTP data |
| void(*)(uint16_t status, uint8_t type, const uint8_t *buffer, uint16_t length, const uint8_t end_of_put_pkt) | [in] | callback | - HTTP data length to be posted to server |
| [in] | callback | - Callback when asyncronous response comes for the request | |
| [in] | status | - Status code | |
| [in] | type | - HTTP Client PUT command type. 2 - Put start response, 3 - Put packet response, 4 - Put delete response, 5 - Data from HTTP server |
|
| [in] | buffer | - Buffer pointer | |
| [in] | length | - Length of data | |
| [in] | end_of_put_pkt | - End of file or HTTP resource content. 0 - More data is pending from host, 1 - End of HTTP file/resource content, 8 - More data pending from server, 9 - End of HTTP file from server |
| Type | Direction | Argument Name | Description |
|---|---|---|---|
| uint8_t | [in] | type | - 0 - HTTPGET - 1 - HTTPPOST |
| uint16_t | [in] | flags | - Select version and security: |Flags|Macro|Description| |---|---|---| |BIT(0)|RSI_IPV6|Set this bit to enable IPv6 , by default it is configured to IPv4| |BIT(1)|RSI_SSL_ENABLE|Set this bit to enable SSL feature| |BIT(2)|RSI_SSL_V_1_0|Set this bit to support SSL TLS Version 1.0 if HTTPS is enabled| |BIT(3)|RSI_SSL_V_1_2|Set this bit to support SSL_TLS Version 1.2 if HTTPS is enabled| |BIT(4)|RSI_SSL_V_1_1|Set this bit to support SSL_TLS Version 1.1 if HTTPS is enabled| |BIT(6)|HTTP_V_1_1|Set this bit to use HTTP version 1.1| |BIT(9)|HTTPS_CERT_INDEX_1|Set this bit to indicate certificate at index 1 to be used for HTTPS| |BIT(10)|HTTPS_CERT_INDEX_2|Set this bit to indicate certificate at index 2 to be used for HTTPS| |
| uint8_t * | [in] | ip_address | - Server IP address |
| uint16_t | [in] | port | - Port number, default : 80 - HTTP, 443 - HTTPS |
| uint8_t * | [in] | resource | - URL string for requested resource |
| uint8_t * | [in] | host_name | - Post name |
| uint8_t * | [in] | extended_header | - Extender header if present, after each header member append \r`\n` |
| uint8_t * | [in] | user_name | - Username for server Authentication |
| uint8_t * | [in] | password | - Password for server Authentication |
| uint8_t * | [in] | post_data | - HTTP data to be posted to server |
| uint32_t | [in] | post_data_length | - HTTP data length to be posted to server |
| void(*)(uint16_t status, const uint8_t *buffer) | [in] | callback | - Callback is called when asynchronous response is received from module for HTTP firmware update request |
| [out] | buffer | - NULL | |
| [out] | status | - This is the status response from module. This returns failure upon an internal error only. |
| Type | Direction | Argument Name | Description |
|---|---|---|---|
| uint8_t | [in] | flags | - Select IP version and security |Flags|Description| |---|---| |BIT(0) - RSI_IPV6|Set this bit to enable IPv6. Configured to IPv4 by default.| |BIT(1) - RSI_SSL_ENABLE|Set this bit to enable SSL feature| |BIT(2) to BIT(7)|Reserved for future use| |
| uint8_t * | [in] | server_ip | - Server IP address |
| uint8_t | [in] | sntp_method | - SNTP methods to use 1-For Broadcast method, 2-For Unicast method |
| uint16_t | [in] | sntp_retry_count | - Configures SNTP max retry count The number of times the client request is retried when the server response is failed to receive. For each retry, the client waits for 5 secs to receive server response before initiating next attempt. Need to set the value based on the network quality. For ex: The value should be <= 5 for good network quality and > 10 for bad network quality. |
| void(*)(uint16_t status, const uint8_t cmd_type, const uint8_t *buffer) | [in] | rsi_sntp_client_create_response_handler | - Callback function when asynchronous response comes for the request. status: Status code. Expected error codes are : 0xBB0A, 0xFF5F, 0xBB0B, 0xBB15, 0xBB10 cmd_type: Command type buffer: Buffer pointer |
| Type | Direction | Argument Name | Description |
|---|---|---|---|
| int8_t * | [in] | buffer | - Buffer pointer to allocate memory for MQTT Client information |
| uint32_t | [in] | length | - Buffer length |
| int8_t * | [in] | server_ip | - IPv4 address of the MQTT broker |
| uint32_t | [in] | server_port | - MQTT broker port number |
| uint32_t | [in] | client_port | - MQTT client port number |
| uint16_t | [in] | flags | - Each bit has its own significance |Flags|Description| |---|---| |Bit(0) - Server IP version|1 - IPv6 | ^ 0 - IPv4 |
| uint16_t | [in] | keep_alive_interval | - MQTT client keep alive interval value in seconds If there are no transactions between MQTT client and broker within this time period, MQTT Broker disconnects the MQTT client If 0, Server does not disconnect |
| Type | Direction | Argument Name | Description |
|---|---|---|---|
| int8_t * | [in] | ssid | - SSID of an access point to connect. SSID should be less than or equal to 32 bytes. |
| rsi_security_mode_t | [in] | sec_type | - Security type of the access point to connect. |Value|Security Type| |---|---| |0|RSI_OPEN| |1|RSI_WPA| |2|RSI_WPA2| |3|RSI_WEP| |4|RSI_WPA_EAP| |5|RSI_WPA2_EAP| |6|RSI_WPA_WPA2_MIXED| |7|RSI_WPA_PMK| |8|RSI_WPA2_PMK| |9|RSI_WPS_PIN| |10|RSI_USE_GENERATED_WPSPIN| |11|RSI_WPS_PUSH_BUTTON| |12|RSI_WPA_WPA2_MIXED_PMK| |13|RSI_WPA3| |
| void * | [in] | secret_key | - Pointer to a buffer that contains security information based on sec_type. |Security type(sec_type)|Secret key structure format (secret_key)| |---|---| |RSI_OPEN|No secret key in open security mode.| |RSI_WPA|PSK string terminated with NULL. Length of PSK should be at least 8 and less than 64 bytes.| |RSI_WPA2|PSK string terminated with NULL. Length of PSK should be at least 8 and less than 64 bytes.| |RSI_WEP|WEP keys should be in the following format:| ^ typedef struct [rsi_wep_keys_s](rsi-wep-keys-s) ^ { ^ uint8_t index[2]; ^ uint8_t key[4][32]; ^ } rsi_wep_keys_t; ^ index: WEP key index to use for TX packet encryption. ^ key: 4 WEP keys, last three WEP keys are optional. If only first WEP key is valid then index should be 0. RSI_WPA_EAP | Enterprise credentials should be in the following format: ^ typedef struct [rsi_eap_credentials_s](rsi-eap-credentials-s) ^ { ^ uint8_t username[64]; ^ uint8_t password[128]; ^ } rsi_eap_credentials_t; ^ username: username to be used in enterprise ^ password: password for the given username RSI_WPA2_EAP | Enterprise credentials should be in the following format: ^ typedef struct [rsi_eap_credentials_s](rsi-eap-credentials-s) ^ { ^ uint8_t username[64]; ^ uint8_t password[128]; ^ } rsi_eap_credentials_t; ^ username: username to be used in enterprise ^ password: password for a given username. RSI_WPA_WPA2_MIXED | PSK string terminated with NULL. Length of PSK should be at least 8 and less than 64 bytes RSI_WPA_PMK | PMK string, should be 32 bytes in length RSI_WPA2_PMK | PMK string, should be 32 bytes in length RSI_WPS_PIN | 8-byte WPS PIN RSI_USE_GENERATED_WPSPIN| NULL string indicate to use PIN generated using rsi_wps_generate_pin API RSI_WPS_PUSH_BUTTON | NULL string indicate to generate push button event RSI_WPA3 | PSK string terminated with NULL. Length of PSK should be at least 8 and less than 64 bytes. |
| Type | Direction | Argument Name | Description |
|---|---|---|---|
| int8_t * | [in] | ssid | - SSID of an access point to connect. SSID should be less than or equal to 32 bytes. |
| rsi_security_mode_t | [in] | sec_type | - Security type of the access point to connect. |Value|Security Type| |---|---| |0|RSI_OPEN| |1|RSI_WPA| |2|RSI_WPA2| |3|RSI_WEP| |4|RSI_WPA_EAP| |5|RSI_WPA2_EAP| |6|RSI_WPA_WPA2_MIXED| |7|RSI_WPA_PMK| |8|RSI_WPA2_PMK| |9|RSI_WPS_PIN| |10|RSI_USE_GENERATED_WPSPIN| |11|RSI_WPS_PUSH_BUTTON| |12|RSI_WPA_WPA2_MIXED_PMK| |13|RSI_WPA3| |
| void * | [in] | secret_key | - Pointer to a buffer that contains security information based on sec_type. |Security type(sec_type)|Secret key structure format (secret_key)| |---|---| |RSI_OPEN|No secret key in open security mode.| |RSI_WPA|PSK string terminated with NULL. Length of PSK should be at least 8 and less than 64 bytes.| |RSI_WPA2|PSK string terminated with NULL. Length of PSK should be at least 8 and less than 64 bytes.| |RSI_WEP|WEP keys should be in the following format:| ^ typedef struct [rsi_wep_keys_s](rsi-wep-keys-s) ^ { ^ uint8_t index[2]; ^ uint8_t key[4][32]; ^ } rsi_wep_keys_t; ^ index: WEP key index to use for TX packet encryption. ^ key: 4 WEP keys, last three WEP keys are optional. If only first WEP key is valid then index should be 0. RSI_WPA_EAP | Enterprise credentials should be in the following format: ^ typedef struct [rsi_eap_credentials_s](rsi-eap-credentials-s) ^ { ^ uint8_t username[64]; ^ uint8_t password[128]; ^ } rsi_eap_credentials_t; ^ username: username to be used in enterprise ^ password: password for the given username RSI_WPA2_EAP | Enterprise credentials should be in the following format: ^ typedef struct [rsi_eap_credentials_s](rsi-eap-credentials-s) ^ { ^ uint8_t username[64]; ^ uint8_t password[128]; ^ } rsi_eap_credentials_t; ^ username: username to be used in enterprise ^ password: password for a given username. RSI_WPA_WPA2_MIXED | PSK string terminated with NULL. Length of PSK should be at least 8 and less than 64 bytes RSI_WPA_PMK | PMK string, should be 32 bytes in length RSI_WPA2_PMK | PMK string, should be 32 bytes in length RSI_WPS_PIN | 8-byte WPS PIN RSI_USE_GENERATED_WPSPIN| NULL string indicate to use PIN generated using rsi_wps_generate_pin API RSI_WPS_PUSH_BUTTON | NULL string indicate to generate push button event RSI_WPA3 | PSK string terminated with NULL. Length of PSK should be at least 8 and less than 64 bytes. |
| void(*)(uint16_t status, const uint8_t *buffer, const uint16_t length) | [in] | join_response_handler | - Called when the response for join has been received from the module. Parameters involved are status, buffer, & length |
| [out] | Status | - Response status. | |
| [out] | Buffer | - Response buffer. On successful execution of the command. GO_Status (1 byte, hex): 0x47 (ASCII "G") - If the module becomes a Group Owner (GO) after the GO negotiation stage or becomes an Access Point. 0x43 (ASCII "C") - If the module does not become a GO after the GO negotiation stage or becomes a client (or station). |
|
| [out] | length | - Length of the response buffer. |
| Type | Direction | Argument Name | Description |
|---|---|---|---|
| uint8_t | [in] | target | - 0 - BURN_INTO_EFUSE (Burns calibration data to EFuse) 1 - BURN_INTO_FLASH (Burns calibration data to Flash) |
| uint32_t | [in] | flags | - Validate information |Bit|MACRO|Description| |---|---|---| |0|RESERVED_0|Reserved| |1|BURN_FREQ_OFFSET|1 - Update XO Ctune to calibration data 0 - Skip XO Ctune update| |2|SW_XO_CTUNE_VALID|1 - Use XO Ctune provided as argument to update calibration data 0 - Use XO Ctune value as read from hardware register| |3|BURN_XO_FAST_DISABLE|Used to apply patch for cold temperature issue(host interface detection) observed on CC0/CC1 modules. appendix| |4|BURN_GAIN_OFFSET_LOW|1 - Update gain offset for low sub-band (2 GHz) 0 - Skip low sub-band gain-offset update| |5|BURN_GAIN_OFFSET_MID|1 - Update gain offset for mid sub-band (2 GHz) 0 - Skip mid sub-band gain-offset update| |6|BURN_GAIN_OFFSET_HIGH|1 - Update gain offset for high sub-band (2 GHz) 0 - Skip high sub-band gain-offset update| |8|ENABLE_DPD_CALIB|1 - Collect dpd coefficients data 0 - Skip dpd coefficients calibration| |9|BURN_DPD_COEFFICIENTS|1 - Burn dpd coefficients data 0 - Skip dpd coefficients calibration| |31-4||Reserved| |
| int8_t | [in] | gain_offset_low | - gain_offset as observed in dBm in channel-1 |
| int8_t | [in] | gain_offset_mid | - gain_offset as observed in dBm in channel-6 |
| int8_t | [in] | gain_offset_high | - gain_offset as observed in dBm in channel-11 |
| uint8_t | [in] | xo_ctune | - Allow user to directly update xo_ctune value to calibration data bypassing the freq offset loop, valid only when BURN_FREQ_OFFSET & SW_XO_CTUNE_VALID of flags is set. The range of xo_ctune is [0, 255], and the typical value is 80. |
| Type | Direction | Argument Name | Description |
|---|---|---|---|
| rsi_ip_version_t | [in] | version | - IP version to be used. RSI_IP_VERSION_4 (4) – to select IPv4, RSI_IP_VERSION_6 (6) – to select IPv6 |
| uint8_t | [in] | mode | - 1 - DHCP mode ; 0 - static mode |
| uint8_t * | [in] | ip_addr | - Pointer to IP address |IPv6 Address Description|Indices in the ip_addr| |---|---| |Prefix Length|ip_addr[0]| |Link Local Address (128 bits)|ip_addr[1] to ip_addr[4]| |Global Address (128 bits)|ip_addr[5] to ip_addr[8]| |Gateway Address (128 bits)|ip_addr[9] to ip_addr[12]| |
| uint8_t * | [in] | mask | - Pointer to network mask |
| uint8_t * | [in] | gw | - Pointer to gateway address |
| uint8_t * | [in] | ipconfig_rsp | - Hold the IP configuration received using DHCP. |
| uint16_t | [in] | length | - Length of ipconfig_rsp buffer |
| uint8_t | [in] | vap_id | - VAP id to differentiate between AP and station in concurrent mode. 0 – for station, 1 – for Access point |
| Type | Direction | Argument Name | Description |
|---|---|---|---|
| uint8_t | [in] | certificate_type | - Type of certificate These are the certificate types: |Value|Certificate type| |---|---| |1|TLS client certificate | |2|FAST PAC file | |3|SSL Client Certificate | |4|SSL Client Private Key | |5|SSL CA Certificate | |6|SSL Server Certificate | |7|SSL Server Private Key | |17|EAP Private Key | |33|EAP Public Key | |49|EAP CA Certificate | |
| uint8_t * | [in] | buffer | - Pointer to a buffer which contains the certificate |
| uint32_t | [in] | certificate_length | - Certificate length |
| Type | Direction | Argument Name | Description |
|---|---|---|---|
| rsi_wlan_query_cmd_t | [in] | cmd_type | - Query command type: |Value|Command Type| |---|---| |1|RSI_FW_VERSION | |2|RSI_MAC_ADDRESS | |3|RSI_RSSI | |4|RSI_WLAN_INFO | |5|RSI_CONNECTION_STATUS | |6|RSI_STATIONS_INFO | |7|RSI_SOCKETS_INFO | |8|RSI_CFG_GET | |9|RSI_GET_WLAN_STAT | |10|RSI_WLAN_EXT_STATS | |11|RSI_WMM_PARAMS | |12|RSI_GET_DEVICE_ID | |
| uint8_t * | [out] | response | - Response of the requested command.
|cmd_type|Request Structure|
|---|---|
|RSI_FW_VERSION|uint8_t response[20] | |RSI_MAC_ADDRESS|uint8_t response[6] | |RSI_RSSI|uint8_t response[2] | |RSI_WLAN_INFO|struct [rsi_rsp_wireless_info_s](rsi-rsp-wireless-info-s) | |RSI_CONNECTION_STATUS|It returns 0x0001 if the WLAN is connected else 0x0000. | |RSI_STATIONS_INFO|struct [rsi_rsp_stations_info_s](rsi-rsp-stations-info-s) | |RSI_SOCKETS_INFO|struct [rsi_rsp_sockets_info_s](rsi-rsp-sockets-info-s) | |RSI_CFG_GET|struct [rsi_cfgGetFrameRcv](rsi-cfg-get-frame-rcv) | |RSI_GET_WLAN_STAT|struct [rsi_rsp_wlan_stats_s](rsi-rsp-wlan-stats-s) | |RSI_WLAN_EXT_STATS|struct [rsi_wlan_ext_stats_s](rsi-wlan-ext-stats-s) | |RSI_WMM_PARAMS|struct [rsi_wmm_ps_parms_s](rsi-wmm-ps-parms-s) | |RSI_GET_DEVICE_ID|uint8_t response[2] 0x9116 for 9116 chipsets 0x917 for 917 chipsets | |
| uint16_t | [in] | length | - Length of the response buffer in bytes to hold result. |
| Type | Direction | Argument Name | Description |
|---|---|---|---|
| rsi_wlan_set_cmd_t | [in] | cmd_type | - Set command type: : |Value|Command Type| |---|---| |1|RSI_SET_MAC_ADDRESS | |2|RSI_MULTICAST_FILTER | |3|RSI_JOIN_BSSID | |4|RSI_CFG_SAVE | |5|RSI_CFG_STORE | |
| uint8_t * | [in] | request | - Request buffer |
| uint16_t | [in] | length | - Length of the request buffer in bytes
|cmd type|Request structure|
|---|---|
|RSI_SET_MAC_ADDRESS|uint8_t mac_address[6]|
|RSI_MULTICAST_FILTER|typedef struct [rsi_req_multicast_filter_info_s](rsi-req-multicast-filter-info-s)|
^ { uint8_t cmd_type; ^ uint8_t mac_address[6]; ^ }rsi_req_multicast_filter_info_t; ^ cmd_type are : ^ 1 . RSI_ MULTICAST_MAC_ADD_BIT (To set particular bit in multicast bitmap) ^ 2 . RSI_MULTICAST_MAC_CLEAR_BIT (To reset particular bit in multicast bitmap ^ 3 . RSI_MULTICAST_MAC_CLEAR_ALL (To clear all the bits in multicast bitmap) ^ 4 . RSI_MULTICAST_MAC_SET_ALL (To set all the bits in multicast bitmap) RSI_JOIN_BSSID | uint8_t join_bssid[6] RSI_CFG_SAVE | This cmd_type is used to save the parameters into non-volatile memory which are used either to join to an Access point (auto-join mode) or to create an Access point(auto-create mode). RSI_CFG_STORE | This cmd_type is used to give the configuration values which are supposed to be stored in the module's non-volatile memory and that are used in auto-join or auto-create modes. ^ User configurations are stored in rsi_user_store_config_t structure. |
| Type | Direction | Argument Name | Description |
|---|---|---|---|
| int8_t * | [in] | ssid | - SSID of the access point. Length of the SSID should be less than or equal to 32 bytes. |
| uint8_t | [in] | channel | - Channel number. Refer the following channels for the valid channel numbers supported: 2.4GHz Band Channel Mapping, 5GHz Band Channel Mapping Channel number 0 is to enable ACS feature. The following table maps the channel number to the actual radio frequency in the 2.4 GHz spectrum. |Channel numbers (2.4GHz)|Center frequencies for 20MHz channel width| |---|---| |1|2412| |2|2417| |3|2422| |4|2427| |5|2432| |6|2437| |7|2442| |8|2447| |9|2452| |10|2457| |11|2462| |12|2467| |13|2472| |14|2484| The following table maps the channel number to the actual radio frequency in the 5 GHz spectrum. |Channel Numbers(5GHz)|Center frequencies for 20MHz channel width| |---|---| |36|5180| |40|5200| |44|5220| |48|5240| |144|5700| |149|5745| |153|5765| |157|5785| |161|5805| |165|5825| |
| rsi_security_mode_t | [in] | security_type | - Type of the security modes on which an access point needs to be operated: |Value|Security type| |---|---| |0|RSI_OPEN | |1|RSI_WPA | |2|RSI_WPA2 | |6|RSI_WPA_WPA2_MIXED | |13|RSI_WPA3_PERSONAL | |14|RSI_WPA3_PERSONAL_TRANSITION| |
| rsi_encryption_mode_t | [in] | encryption_mode | - Type of the encryption mode: |Value|Encryption mode| |---|---| |0|RSI_NONE | |1|RSI_TKIP | |2|RSI_CCMP| |
| uint8_t * | [in] | password | - PSK to be used in security mode. Minimum and maximum length of PSK is 8 bytes and 63 bytes respectively |
| uint16_t | [in] | beacon_interval | - Beacon interval in ms. Allowed values are integers from 100 to 1000 which are multiples of 100. |
| uint8_t | [in] | dtim_period | - DTIM period. Allowed values are integers between 1 and 255. |
| Type | Direction | Argument Name | Description |
|---|---|---|---|
| uint8_t | [in] | psp_mode | - PSP modes available are mentioned below
|Parameter|Description|
|---|---|
|Active(0)|In this mode, module is active and power save is disabled. | |RSI_SLEEP_MODE_1 (1)|Connected sleep mode. | ^ In this sleep mode, SoC will never turn off, therefore no handshake is required before sending data to the module. RSI_SLEEP_MODE_2 (2) | In this sleep mode, SoC will go to LP/ULP (with/without RAM RETENTION) sleep based on the selected value set for RSI_SELECT_LP_OR_ULP_MODE in rsi_wlan_config.h. ^ Therefore handshake is required before sending data to the module. RSI_SLEEP_MODE_8 (8) | Deep sleep mode with ULP RAM RETENTION. In deep sleep mode, module will turn off the SoC and a GPIO or Message based handshake is required before sending commands to the module. RSI_SLEEP_MODE_10 (10) | Deep sleep mode without ULP RAM RETENTION. |
| uint8_t | [in] | psp_type | - PSP types available are mentioned below
|Parameter|Description|
|---|---|
|RSI_MAX_PSP (0)|This psp_type will be used for max power saving. | |RSI_FAST_PSP (1)|This psp_type allows module to disable power save for any Tx / Rx packet for monitor interval of time | ^ (monitor interval can be set by RSI_MONITOR_INTERVAL in rsi_wlan_config.h file, default value is 50 ms). ^ If there is no data for monitor interval of time then module will again enable power save. RSI_UAPSD (2) | This psp_type is used to enable WMM power save. |
| uint16_t | [in] | listen_interval | - Used to configure sleep duration in power save and should be less than the listen interval configured by RSI_LISTEN_INTERVAL Macro in join command parameters in rsi_wlan_config.h file. Valid only if BIT (7) in join_feature_bit_map is set. This value is given in time units (1024 microsecond). |
| Type | Direction | Argument Name | Description |
|---|---|---|---|
| uint8_t | [in] | psp_mode | - PSP modes available are mentioned below
|Parameter|Description|
|---|---|
|Active(0)|In this mode, module is active and power save is disabled. | |RSI_SLEEP_MODE_1 (1)|Connected sleep mode. | ^ In this sleep mode, SoC will never turn off, therefore no handshake is required before sending data to the module. RSI_SLEEP_MODE_2 (2) | In this sleep mode, SoC will go to LP/ULP (with/without RAM RETENTION) sleep based on the selected value set for RSI_SELECT_LP_OR_ULP_MODE in rsi_wlan_config.h. ^ Therefore handshake is required before sending data to the module. RSI_SLEEP_MODE_8 (8) | Deep sleep mode with ULP RAM RETENTION. In deep sleep mode, module will turn off the SoC and a GPIO or Message based handshake is required before sending commands to the module. RSI_SLEEP_MODE_10 (10) | Deep sleep mode without ULP RAM RETENTION. |
| uint8_t | [in] | psp_type | - PSP types available are mentioned below
|Parameter|Description|
|---|---|
|RSI_MAX_PSP (0)|This psp_type will be used for max power saving. | |RSI_FAST_PSP (1)|This psp_type allows module to disable power save for any Tx / Rx packet for monitor interval of time | ^ (monitor interval can be set by RSI_MONITOR_INTERVAL in rsi_wlan_config.h file, default value is 50 ms). ^ If there is no data for monitor interval of time then module will again enable power save. RSI_UAPSD (2) | This psp_type is used to enable WMM power save. |
| Type | Direction | Argument Name | Description |
|---|---|---|---|
| uint16_t | [in] | power | - Set TX power in dbm. The valid values are from 2dBm to 18dBm. |
| uint32_t | [in] | rate | - Set transmit data rate. |
| uint16_t | [in] | length | - Configure length of the TX packet. The valid values are in the range of 24 to 1500 bytes in the burst mode and range of 24 to 260 bytes in the continuous mode. |
| uint16_t | [in] | mode | - Below mentioned are the available modes
|Value|Parameter|Description|
|---|---|---|
|0|Burst Mode|DUT transmits a burst of packets with the given power, rate, length in the channel configured.|
^ The burst size will be determined by the |
| uint16_t | [in] | channel | - Set the channel number in 2.4 GHz / 5GHz. |
| Type | Direction | Argument Name | Description |
|---|---|---|---|
| uint16_t | [in] | power | - Set TX power in dbm. The valid values are from 2dBm to 18dBm. |
| uint32_t | [in] | rate | - Set transmit data rate. |
| uint16_t | [in] | length | - Configure length of the TX packet. The valid values are in the range of 24 to 1500 bytes in the burst mode and range of 24 to 260 bytes in the continuous mode. |
| uint16_t | [in] | mode | - Below mentioned are the available modes
|Value|Parameter|Description|
|---|---|---|
|0|Burst Mode|DUT transmits a burst of packets with the given power, rate, length in the channel configured.|
^ The burst size will be determined by the |
| uint16_t | [in] | channel | - Set the channel number in 2.4 GHz / 5GHz. |
| uint16_t | [in] | number_pkts | - Set the number packets in TX mode. |
| Type | Direction | Argument Name | Description |
|---|---|---|---|
| uint8_t | [in] | enable | - 0 - Disable the auto configuration feature. 1 - Enable the auto configuration feature on power up. 2 - Enable the auto configuration for profile based. |
| uint32_t | [in] | type | - Profile type |Value|Parameter|Macro| |---|---|---| |0|Client profile|RSI_WLAN_PROFILE_CLIENT| |1|P2P profile|RSI_WLAN_PROFILE_P2P| |2|EAP profile|RSI_WLAN_PROFILE_EAP| |6|AP profile|RSI_WLAN_PROFILE_AP| |0xF|All profiles|RSI_WLAN_PROFILE_ALL| |
| Type | Direction | Argument Name | Description |
|---|---|---|---|
| uint8_t | [in] | target | 0 - BURN_INTO_EFUSE (Burns calibration data to EFuse)(Not supported) 1 - BURN_INTO_FLASH (Burns calibration data to Flash) |
| uint32_t | [in] | flags | - Validate information |Bit|MACRO|Description| |---|---|---| |0|EVM_OFFSET_CUST_0|1 - Update evm_offset_11B rate calibration data 0 - Skip evm_offset update| |1|EVM_OFFSET_CUST_1|1 - Update evm_offset_11G_6M_24M_11N_MCS0_MCS2 rate calibration data 0 - Skip evm_offset update| |2|EVM_OFFSET_CUST_2|1 - Update evm_offset_11G_36M_54M_11N_MCS3_MCS7 rate calibration data 0 - Skip evm_offset update| |3|EVM_OFFSET_CUST_3|1 - Update evm_offset_11N_MCS0 rate calibration data 0 - Skip evm_offset update| |4|EVM_OFFSET_CUST_4|1 - Update evm_offset_11N_MCS7 rate calibration data 0 - Skip evm_offset update| 31-5| Reserved |
| int8_t | [in] | evm_offset_11B | - evm_offset for 11B rate |
| int8_t | [in] | evm_offset_11G_6M_24M_11N_MCS0_MCS2 | - evm_offset for 11G_6M_24M_11N_MCS0_MCS2 rate |
| int8_t | [in] | evm_offset_11G_36M_54M_11N_MCS3_MCS7 | - evm_offset for 11G_36M_54M_11N_MCS3_MCS7 rate |
| int8_t | [in] | evm_offset_11N_MCS0 | - evm_offset for 11N_MCS0 rate |
| int8_t | [in] | evm_offset_11N_MCS7 | - evm_offset for 11N_MCS7 rate Recalibration is not possible if EFuse is being used instead of flash as calibration data storage |
| Type | Direction | Argument Name | Description |
|---|---|---|---|
| int32_t | [in] | sockID | - Socket descriptor ID |
| int | [in] | level | - Set the socket option, take the socket level |
| int | [in] | option_name | - Provide the name of the ID. SO_MAXRETRY - To Enable max tcp retry count SO_SOCK_VAP_ID - To Configure the socket VAP ID. VAP ID to differentiate between station and AP in concurrent mode. 0 – for station, 1 – for Access point SO_TCP_KEEP_ALIVE - To configure the TCP keep alive (initial time in seconds) SO_RCVBUF - To configure the application buffer for receiving server certificate SO_SSL_ENABLE - To open an SSL/TLS connection over TCP socket. By default supports versions of both TLS 1.0 and TLS 1.2 SO_SSL_V_1_0_ENABLE - To open an SSL/TLS connection over TCP socket with TLS version 1.0 SO_SSL_V_1_1_ENABLE - To open an SSL/TLS connection over TCP socket with TLS version 1.1 SO_SSL_V_1_2_ENABLE - To open an SSL/TLS connection over TCP socket with TLS version 1.2 SO_TCP_ACK_INDICATION - To enable tcp ack indication feature SO_CERT_INDEX - To enable set certificate index SO_HIGH_PERFORMANCE_SOCKET - To Configure the high performance socket SO_TCP_MSS - To Configure the tcp mss SO_TCP_RETRY_TRANSMIT_TIMER - To Configure the tcp retry transmit timer SO_TLS_SNI - To Configure the TLS SNI extension SO_RCVTIMEO - To configure the socket-receive timeout using this option. If no data is received within this time, the sapi driver will unblock this API. SO_CHECK_CONNECTED_STATE - To check for the connected state IP_TOS - To configure the type of service value [0-7] |User Priority (UP)|Value Description|Access Category (AC)| |---|---|---| |0|Best Effort (default)|AC_BE| |1|Background|AC_BK| |2|Spare / Background|AC_BK| |3|Excellent Effort|AC_BE| |4|Controlled Load|AC_VI| |5|Video|AC_VI| |6|Voice|AC_VO| |7|Network Control|AC_VO| |
| const void * | [in] | option_value | - Value of the parameter |
| rsi_socklen_t | [in] | option_len | - Length of the parameter |
| Type | Direction | Argument Name | Description |
|---|---|---|---|
| nw_app_protocol | [in] | protocol | - The following table lists in below |Protocol|Value| |---|---| |RSI_HTTP|0| |
| nw_app_config | [in] | config_type | - The following table lists in below |config_type|Value| |---|---| |RSI_CIPHER_SELECTION|0| |
| void * | [in] | config | - The following table lists in below |Protocol|config_type|config| |---|---|---| |RSI_HTTP|RSI_CIPHER_SELECTION|Configure the Cipher values as explained on the [SSL/TLS Cipher Selection](ssl-ciphers-selection) page.| |
| uint16_t | [in] | config_length | - Length of the config parameter |