Network Stack SDK Version 2.15.0 (November 20, 2026) - Release Notes#
The Netstack software development kit (SDK) provides robust network protocol support, including TCP/IP, UDP, and DNS capabilities for embedded applications.
Click here for earlier releases.
Release Summary#
Key Features | API Changes | Bug Fixes | Chip Enablement
Key Features#
None
API Changes#
None
Bug Fixes#
Fixed an issue that caused mDNS service registration to reject valid TXT strings without an
=character and silently generate an empty TXT record.Fixed an issue that caused the firmware to generate malformed mDNS PTR, SRV, TXT, and A records from valid service-registration parameters.
Fixed incorrect PLLMODE selection for OPERMODE SoC clock configurations. The firmware now rejects invalid combinations of 120 MHz and 160 MHz clock settings and automatically sets PLLMODE based on the selected clock.
Chip Enablement#
None
Key Features#
New Features | Enhancements | Removed Features | Deprecated Features
Note: See Feature Matrix for a list of any applicable APIs, examples, software variants, modes, hardware, and host interfaces for each feature.
New Features#
None
Enhancements#
None
Removed Features#
None
Deprecated Features#
None
API Changes#
New APIs | Modified APIs | Removed APIs | Deprecated APIs
New APIs#
None
Modified APIs#
None
Removed APIs#
None
Deprecated APIs#
None
Bug Fixes#
| ID | Issue Description | GitHub / Salesforce Reference (if any) | Affected Chip Revision, Hardware, Host Interfaces |
|---|---|---|---|
| 1843927 | Fixed an issue that caused mDNS service registration to reject valid TXT strings without an `=` character and silently generate an empty TXT record. | None |
|
| 1778698 | Fixed an issue that caused the firmware to generate malformed mDNS PTR, SRV, TXT, and A records from valid service-registration parameters. | None |
|
| 1601927 | Fixed incorrect PLLMODE selection for OPERMODE SoC clock configurations. The firmware now rejects invalid combinations of 120 MHz and 160 MHz clock settings and automatically sets PLLMODE based on the selected clock. | None |
|
Chip Enablement#
None
Application Example Changes#
New Examples | Modified Examples | Removed Examples | Deprecated Examples
New Examples#
None
Modified Examples#
None
Removed Examples#
None
Deprecated Examples#
None
Known Issues and Limitations#
| ID | Issue or Limitation Description | GitHub / Salesforce Reference (if any) | Workaround (if any) | Affected Chip Revision, Hardware, Host Interfaces |
|---|---|---|---|---|
| NA | TLS handshakes may occasionally fail due to incorrect ECC curve parameter generation, resulting in a BBD2 error. The handshake typically succeeds on a subsequent retry. | 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 | In WPA2-Enterprise security mode, there are limitations when retrieving wireless statistics using the rsi_wlan_get() API. | None | None |
|
| NA | In Concurrent Mode, communication loss may occur on the STA application when multiple clients are connected to the AP simultaneously. | None | None |
|
| NA | In STA + AP Concurrent Mode, IP address conflict detection has limitations, and any conflict detection failures are not reported to the host. | None | None |
|
| NA | During firmware update via OTA (TCP/HTTP), a corrupted firmware image can leave the module unresponsive on the next boot. | None | None |
|
| NA | TLS connection problems may occur when attempting to revoke public and private keys using existing keys. | None | None |
|
| 1237582 | Observed inconsistencies in TCP and UDP RX throughput in AP-alone mode. | None | None |
|
| NA | A duplicate IPv6 address is observed to be assigned to multiple STAs operating 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 |
|
| 1557290 | TCP TX/RX throughput is observed to be approximately 30% lower than UDP throughput. | None | None |
|
| 1649047 | UDP RX and TCP RX operation failures are observed in STA + BLE coexistence throughput scenarios 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 | No data transfer is observed during SSL TX and SSL RX throughput operations in the STA + BLE coexistence throughput application, regardless of whether Robust Mode is enabled or disabled. | None | None |
|
| 1629919 | HTTP GET requests fail when downloading large files (~1 MB) on RS9116W in UART + SAPI mode. | None | None |
|
| C00000685 | TLS connection may still succeed after the Root CA is deleted or replaced at runtime. Certificate store changes take effect only after a power cycle. | None | None |
|
| 1827944 | TLS socket connection may fail after a power cycle, and later connection attempts may not recover until a hardware reset. | None | None |
|