| Item | Details |
|---|---|
| Release date | May 7th, 2024 |
| SDK Version | 3.2.0 |
| Firmware Version | 1711.2.11.1.0.0.7 |
| GSDK Version | 4.4.3 |
| Package Name | WiSeConnect3_SDK_3.2.0 |
| Supported RTOS | FreeRTOS |
| Operating Modes Supported | Wi-Fi STA, Wi-Fi AP, Wi-Fi STA+BLE, Wi-Fi STA+AP |
- SiWx917 release consists of two components
- Wireless Firmware - SiWx917 Firmware Binary available as SiWG917-B.2.11.1.0.0.7.rps
- Wiseconnect3 Library - Wiseconnect3 SDK library runs on the external host in NCP mode.
- Expansion kits: SiWx917-EB4346A (based on Radio board SiWx917-4346A + 8045A Co-Processor Adapter board)
- Expansion Kits: Si917-8036B (Beta version)
- IC OPNs: SiWN917M100LGTBA (Wi-Fi 6 NCP IC, QFN 7x7, 2.4 GHz, 4MB stacked flash, -40 to +85C)
- Operating Modes
- Wi-Fi STA (802.11ax, 802.11n), Wi-Fi 802.11n AP, Wi-Fi STA (802.11ax, 802.11n) + 802.11n AP, Wi-Fi STA (802.11ax, 802.11n) + BLE
- Security
- Secure Boot, Secure Key storage and HW device identity with PUF, Secure Zone, Secure XIP (Execution in place) from flash, Secure Attestation, Anti Rollback, Secure Debug. Flash Protection
- Secure firmware upgrade options:
- Firmware loading through UART, SPI Interface
- Secure Over the Air (OTA) Upgrade
- Firmware update via Bootloader
- Crypto Support
- Crypto API's for Hardware Accelerators:
- Advanced Encryption Standard (AES) 128/256/192, Secure Hash Algorithm (SHA) 256/384/512, Hash Message Authentication Code (HMAC), Random Number Generator (RNG), SHA3, AES-Galois Counter Mode (GCM)/ Cipher based Message Authentication Code (CMAC), ChaCha-poly, True Random Number Generator (TRNG)
- Software Accelerators: RSA, ECC
- Wrapping Secret keys (Symmetric crypto).
- Added ECDSA Sign and Verify APIs.
- System Power Save
- Deep Sleep with RAM retention and without RAM retention
- Wireless Power Save: Connected Sleep (Wi-Fi Standby Associated), BLE Advertising with powersave, BLE Scan with powersave , BLE connection with powersave. Only Max PSP power save mode is supported in BLE
- Wi-Fi Protocols
- IEEE 802.11 b/g/n/ax (2.4GHz)
- Access Point (AP) Mode
- 4 Client Support, Hidden SSID Mode, Auto Channel Selection, Scan in AP mode (Alpha)
- Wi-Fi Security
- WPA2 Personal, WPA3 Personal (H2E method only) (Alpha), WPA Mixed mode (WPA/WPA2)
- Wi-Fi Scan
- Selective Scan, Active/Passive Scan (world domain)
- Wi-Fi STA (Security Modes)
- Open Mode, WPA2 Personal, WPA2 Enhancements, WPA3 Personal, Mixed Mode (WPA/WPA2), WPA3 Personal Transition Mode (WPA2/WPA3)
- WPA2 Enterprise security (STA)
- Method
- PEAP/TTLS/TLS 1.0/TLS 1.2/FAST/LEAP
- Method
- Wi-Fi STA Rejoin
- Wi-Fi STA Roaming
- BG Scan, OKC (Opportunistic Key caching), PMK (Pairwise Master Key) caching, Pre-Authentication
- Wi-Fi Protocol Power Save
- Deep sleep (unconnected state), Max PSP, Enhanced Max PSP, Fast PSP, TWT
- QoS
- WMM-QoS
- Wi-Fi 6 Feature
- MUMIMO (DL), OFDMA (UL/DL), iTWT, TWT I-Frame & TWT Enhancements (Automatic TWT Configuration), BSS coloring, MBSSID
- Wi-Fi Concurrency
- AP+STA (Same channel)
- Wi-Fi Band/Channels
- 2.4GHz CH1-11, 2.4GHz CH1-13, 2.4GHz CH1-14
- Known Security Vulnerabilities Handled
- WPA2 KRACK Attacks, Fragment and Forge Vulnerability
- Core Networking Features
- TCP/IP Bypass (LWIP as Hosted stack for reference), IPv4/IPv6/UDP/TCP/ARP/ICMP/ICMPv6
- SSL client versions TLSV1.0, TLSV1.2, TLSV1.3
- SSL server versions TLSV1.0 and TLSV1.2
- DHCPv4 (Client/Server)/ DHCPv6 Client
- Advanced Network Features
- HTTP Client/HTTPS Client//DNS Client/SNTP Client, Embedded MQTT/MQTT on host
- Wi-Fi IoT Cloud Integration
- AWS IOT Core
- BSD and IoT sockets application programming interface(API)
- GAP(Advertising, Scanning, initiation, Connection and Bonding)
- Generic Attribute Protocol(GATT)
- Attribute protocol(ATT)
- Security
- LL Privacy 1.2
- Accept list
- Directed Advertising
- Extended Advertising
- Periodic Advertising
- Periodic Advertising scanning
- Extended Advertising scanning
- Periodic Advertising list
- LE periodic advertising synchronization
- LE PHY(1Mbps, 2Mbps) & Coded PHY(125Kbps, 500kbps)
- Simultaneous scanning on 1Mbps and Coded PHY
- LE dual role topology
- LE data packet length extensions(DLE)
- Asymmetric PHYs
- LE channel selection algorithm 2 (CSA#2)
- LE Secure connections
- Bluetooth 5.4 Qualified
- Simplified and Unified DX for Wi-Fi API
- Simplifies application development and presents clean and standardized APIs
- BSD and ARM IoT-compliant socket API
- Available through Simplicity Studio and GitHub
- Wi-Fi STA + BLE
- 3 wire coex acting as Wi-Fi with external Bluetooth
- 3 wire coex acting as Wi-Fi with external Zigbee/OT
- None
- Enhancements
- Added sl_si91x_mem_pool_buffers_with_quota component
- API reference guide enhancement with a callback usage note
- Readme enhancements of the example application
- Fixed Issues
- Fixed data transfer halt issues in NCP over EFR.
- Fixed TCP RX failure in concurrent mode in multithreading_application example
- Image path and setup diagrams correction in example Readme
- Handle RPS header corruption during firmware update
- Fixed the issue of DUT returning SL_STATUS_TIMEOUT after multiple iterations during wifi init and deinit sequence
- Fixed the issue where DUT is getting hang while running aws_device_shadow application with Power save enabled
- Fixed handling of EAP-FAST PAC file loading manually.
-
Enhancements
- Added long url support (max 2048 bytes) for HTTP OTAF.
- Removed a limitation in Embedded where MQTT keep alive interval should be either 0 or a value greater than 35 seconds. Now allowing keep alive interval less than 35 seconds also.
- Added support for LEAP security in EAP mode
- Added hostname support to HTTP client request
- For Flash less parts support added to update customer gain offset and xo_ctune offset to external flash.
- Added support for firmware_update_from_host_uart, wifi_data_transfer_application_ncp, wifi_ap_throughput_ncp, wifi_firmware_flashing_from_host_uart_xmodem_bootloader_ncp example application.
-
Fixed Issues
- Fixed Embedded mqtt sequence issues when remote terminate and wlan disconnection is triggered .
- Fixed issues with MDNS services not responding to the queries from other devices
- Fixed same MAC address being generated for AP and Station address incase of concurrent mode.
- Fixed the issue where DUT is getting hang while running HTTP_PUT Method in http client application
- Fixed the issue where sl_net_set_credential API is failed with 0x10026 (SL_STATUS_SI91X_WRONG_PARAMETERS) error when trying to load HTTP certificate(SL_NET_HTTP_CLIENT_CREDENTIAL_ID) for HTTPs
- Fixed issue where http otaf firmware update failed with "BBE1(SL_STATUS_SI91X_HTTP_TIMEOUT) error" for HTTP and BBD6(SL_STATUS_SI91X_SSL_TLS_HANDSHAKE_TIMEOUT_OR_FTP_FILE_NOT_CLOSED) for HTTPS otaf
- Fixed issue where DUT is not initializing TCP connection to update the firmware in HTTP OTAF (NCP)application
- Fixed issue where failure/no response during the 2nd iteration of HTTP Server response
- Fixed DUT hang issue which is caused because of HW calibrations.
- Fixed xo captune calibration issue. Issue was xo captune getting overwritten with default value.
- Fixed the issue of module not entering into deep sleep after AP stop API call.
- Fixed an issue of AP VAP initialization in the scenario of AP-start, AP-stop and AP-start again.
- Fixed issues with static IPV4 assignment to DUT.
- Fixed issues with ECDSA ciphers
- Enhancements
- Added change to obtain 6 bytes Bluetooth device address when the "rsi_bt_get_local_device_address" API is called in all BLE applications.
- Added STM32 support for ble_ae_central, ble_throughput_app, ble_power_save and ble_ae_peripheral application
- Fixed Issues
- Fixed BLE disconnection issue while running wifi_https_ble_dual_role application when powersave is disabled.
- Resolved the issue with BLE PER stats cmd API.
- Fixed reconnection issue in case of pairing failure.
- Fixed invalid connection request(CVE-2019-19193) vulnerability.
- Updated readme files for "ble_accept_list" and "ble_testmodes" applications.
- Updated "tx_power" description for HP mode in "rsi-ble-per-transmit-s" structure.
- Fixed issue where WLAN power save API is failing with error code: SL_STATUS_TIMEOUT while executing the ble_ae_central application
- Enhancements
- Added support for wifi_station_ble_throughput_app_ncp, wifi_https_ble_dual_role_ncp, wifi_throughput_ble_dual_role_ncp example application
- Fixed Issues
- Fixed BLE connection establishment when DUT in the central role while using wifi_throughput_ble_dual_role_ncp example
- Fixed issue where DUT is not receiving the IP address to the host even after the DHCP process over the air with the wifi_station_ble_provisioning_aws_ncp application.
- Fixed issue where throughputs and Remote BLE device address are not displaying in the logs for wifi_station_ble_throughput_app_ncp example
- Fixed issue where data transmission is not working with UART interface while running default wifi_station_ble_provisioning_aws_uart_ncp Application
- Fixed issue where compilation errors are seen in the wifi_throughput_ble_dual_role_soc example when configuring CONNECT_OPTION as CONN_BY_ADDR'
- Fixed issue where compilation errors while Disabling HTTPS_DOWNLOAD macro in wifi_https_ble_dual_role application.
- Set the recommended Power Save Profile (PSP) type to Enhanced Max PSP.
- Memory configuration for NCP mode is 672K_M4SS_0K.
- Set the following recommended FreeRTOS configuration in FreeRTOSConfig.h
- configTIMER_TASK_PRIORITY to 55
- configTOTAL_HEAP_SIZE to 51200
- configUSE_POSIX_ERRNO to 1
- Simplicity Studio. This release is tested with SV5.8.0 version.
- Refer to the latest version of the NCP "Getting-Started-with-SiWx917" guide for more details
- It is recommended to enable bit 16 of the 'Extended TCP IP Feature' bit map in the opermode command for all Wi-Fi Socket operations from the host to ensure graceful handling during asynchronous closures from the peer.
- For high throughput applications, aggregation (bit 2 of feature_bit_map) is recommended to be enabled in opermode.
- Users can enable SL_SI91X_EXT_TCP_IP_SSL_16K_RECORD in 'Extended TCP IP Feature' bit map in opermode for (HTTPS server) supporting 16k record.
- TWT
- Recommendation is to use sl_wifi_target_wake_time_auto_selection() API for all TWT applications.
- It is recommended to issue iTWT setup command once IP assignment, TCP connection, application specific socket connections are done.
- When using sl_wifi_enable_target_wake_time API, increase TCP / ARP Timeouts at the remote side depending upon the configured TWT interval configured. It's highly recommended to use sl_wifi_target_wake_time_auto_selection() as an alternative.
- In case of TWT in coex mode, when using sl_wifi_enable_target_wake_time API, use TWT wake duration <= 16 ms and TWT wake interval >= 1 sec. If wake duration > 16 ms or TWT wake interval < 1sec, there might be performance issues.
- For iTWT GTK interval in AP should be configured to max possible value or zero. If GTK interval is not configurable on AP side, recommended TWT interval (in case of sl_wifi_enable_target_wake_time API) or RX Latency (in case of sl_wifi_target_wake_time_auto_selection API) is less than 4sec.
- When sl_wifi_enable_target_wake_time API is used, configuring TWT Wake interval beyond 1 min might lead to disconnections from the AP. Recommended to use TWT wake interval of less than or equal to 1 min.
- When using sl_wifi_enable_target_wake_time API, it is recommended to set missed_beacon_count of sl_wifi_set_advanced_client_configuration API greater than 2 times of the configured TWT Interval.
- Disable power save for high throughput applications or use FAST PSP power save mode as per application requirement.
- The application needs to ensure that it sets RTC with the correct timestamp before establishing the SSL/EAP connection.
- The minimum timeout value should not be less than 1 second for socket select and socket receive calls.
- Please refer Keep alive intervals supported by MQTT broker and configure keep alive interval values accordingly.
- The minimum keep alive interval value recommended for embedded MQTT is 10 Seconds.
- Disable power save and suspend any active TWT sessions before triggering HTTP OTAF.
- Randomize the client port if using rapid connect/disconnect of the MQTT session on the same client port with the power save.
- In BLE, the recommended range of Connection Interval in
- Power Save (BLE Only) - 100 ms to 1.28 s.
- In BLE, during Connection, the configuration of Scan Interval and Scan Window with the same value is not recommended. The suggested ratio of Scan Window to Scan Interval is 3:4.
- In BLE, if a device is acting as Central, the scan window (in set_scan_params and create_connection commands) must be less than the existing Connection Interval. The suggested ratio of Scan Window to Connection Interval is 2:3.
- In BLE mode, if scanning and advertising are in progress on the SiWx91x module and it subsequently gets connected and moves to the central role, scanning stops else if it moves to the peripheral role, advertising stops. To further establish a connection to another peripheral device or to a central device, the application should give a command for starting advertising and scanning again.
- For concurrent Wi-Fi + BLE, and while a Wi-Fi connection is active, we recommend setting the ratio of the BLE scan window to BLE scan interval to 1:3 or 1:4.
- Wi-Fi + BLE Advertising
- All standard advertising intervals are supported. As Wi-Fi throughput is increased, a slight difference in on-air advertisements compared to configured intervals may be observed.
- BLE advertising is skipped if the advertising interval collides with Wi-Fi activity.
- Wi-Fi + BLE scanning
- All standard scan intervals are supported. For better scan results, we recommend setting the ratio of the BLE scan window to BLE scan interval to 1:3 or 1:4.
- BLE scanning will be stopped for intervals that collide with Wi-Fi activity.
- Wi-Fi + BLE Central/Peripheral Connections
- All standard connection intervals are supported.
- 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 achieve higher throughput for both Wi-Fi and BLE, use medium connection intervals, such as 45 to 80 ms with maximum supervision timeout.
- Ensure Wi-Fi activity consumes lower intervals.
- None
- Enhanced sl_wifi_get_firmware_version() API to provide more details (ROM ID, chip ID, security version, etc) which is not backward compatible with firmware older than 1711.2.10.1.0.0.4. Firmware binary notation does not include security version number.
- Observed not being able to receive UDP Rx TPUT print at Teraterm with IPV6 Throughput example
- Matter extension based applications are experiencing compatibility issues with WiseConnect SDK 3.2.0. It is recommended to use WiseConnect SDK 3.1.1 for matter-related applications. This will be addressed in up coming release(s).
- Asynchronous Azure MQTT is not supported, this will be addressed in up coming release(s).
- mDNS with IPV6 is not supported.
- Power Save with TCP/IP is not supported for UART interface.
- Recommended to configure VAP_ID properly for Si91x STA and AP using sl_si91x_setsockopt_async(), in case of data transfer.
- Recommended to use valid length(<= 202 bytes) for topic to be published in the "Embedded MQTT" demo, else it leads to return wrong error code(0x21).
- Observed AWS_DEVICE SHADOW LOGGING STATS is not working with Power Save enable
- Observing DUT is getting stuck while running MQTT publish with 2 different topics
- Observed MQTT RX is failing when continuous data sent every 1 second in aws_mqtt application
- Observed DUT Failed to connect to AP with timeout error 0x7(SL_STATUS_TIMEOUT) while single MQTT subscribe and publish in loop with embedded MQTT application
- Observed DUT is not initiating the AWS connection post-rejoin failure indication after publishing 10-15 packets, turning OFF AP and trying to rejoin the network with aws_mqtt application
- Observing LAST_WILL_MESSAGE is random at every MQTT connection rather than the configured Message/Length with embedded MQTT application
- Observing MQTT disconnect API is getting failed with 0x7(SL_STATUS_TIMEOUT) error while doing publish & subscribe with embedded MQTT application
- Bus thread stack may need to increase if local variables are used in user callback to avoid stack overflow
Wi-Fi STA
- STA Connection with the WPA3 Hunting and Pecking algorithm takes about 3-4 seconds.
- Observed connection failures with some APs in more channel congestion ~50-60% occupancy open lab environment.
- Region selection based on country IE in the beacon is not supported
- Observed intermittent beacon reception from Access Point ( beacon misses) when channel congestion > 85%.
- UL MU-MIMO is not supported.
Access Point (AP) Mode
- Scan feature in AP mode not fully functional.
- Fixed rate configuration in AP mode using sl_wifi_set_transmit_rate API is not being set as expected.
WPA2 Enterprise security (STA)
- Observed issue with configuring certificate key and programming 4096 bit key and SHA384/SHA512 certificates.
- Observing DUT is throwing 0x1001c when configuring .data.certificate_key as "123456789"
- Issue observed with WPA2 Enterprise Connectivity using Microsoft RADIUS Server.
Wi-Fi Concurrency ( AP + STA in same channel)
- Observed 3rd party STA association fail with 917 AP while 917 STA mode is connecting/reconnecting to configured 3rd party AP. Reconnect 3rd party STA to 917 AP in such scenarios.
OFDMA (UL/DL)
- Less throughput observed in DL-OFDMA with some APs that enabled LDPC.
MUMIMO (DL)
- For Coex Scenario Wi-Fi + BLE, BLE Data transfer, MU retries (~50-60%) observed while running DL MU-MIMO test.
- Observed Performance, Interop issues with MU MIMO with certain APs.
- Less throughput was observed in MU-MIMO with some APs that enabled LDPC.
MU-MIMO (UL)
- UL MU-MIMO is not supported.
TWT
- When sl_wifi_enable_target_wake_time() API is used, occasional MQTT disconnections may be observed if TWT is configured with longer TWT intervals (>30secs) with embedded MQTT + TWT. As an alternative, it's highly recommended to use sl_wifi_target_wake_time_auto_selection() API, where these dependencies are internally handled.
Wi-Fi STA Rejoin
- observed Scanning (probe request) in all channels instead of the channels configured in selective channel(channel_bitmap_2g4) during rejoin process
IPv4/IPv6
- IP change notification is not indicated to the application
BSD Socket API
- Configuration issue to program TCP retry count (default 10) through setsockopt
- Every server socket created consumes a socket (maximum of 10 sockets supported) and every subsequent connection to server socket consumes an additional socket (from the same pool of 10 sockets), which limits the number of server connections supported.
- Observed socket shutdown is not happening and DUT is getting stuck at "prvCheckTasksWaitingTermination" while doing socket connection-> data transfer -> socket shut down for multiple iterations.
- Observed DUT is not sending TCP retry packets on air when configured through setsockopt().
SSL Client/Server
- Sometimes during SSL Handshake, ECC curve parameters generated are wrong, resulting in connection failure with BBD2 error. However, this recovers in the next attempt.
- Secure SSL renegotiation not supported in Embedded Networking Stack
HTTP Client/ HTTPS Client
- Observed occasional HTTPS continuous download failures when power save is enabled. Recommended to disable it before performing HTTPS continuous downloads
- Observed HTTPS post data is failing with error code: BBE2 (HTTP Failed).
SNTP
- Unable to get SNTP async events when coex mode and power save are enabled
Throughputs & Performance
- Observed 20% less Wi-Fi throughput with SDK 3.x compare to target throughput (depends on host and host interface), SDK refinements are in progress
Secure Over the Air (OTA) Upgrade
- Observed firmware upgrade failures after multiple iterations
- Observed OTA failures with power save enabled, So recommended to disable power save during OTA
- Observed "0xffffffff" error at the remote end while doing firmware upgrade via TCP server using (featured) example with ubuntu 21.0x.
Wi-Fi IOT Cloud integration (AWS IOT Core)
- Observed AWS MQTT keepalive transmission is not happening at expected intervals with power save enabled.
- Observing LAST_WILL_MESSAGE is random at every MQTT connection rather than the configured Message/Length
Wi-Fi Interoperability (IOP)
- Observed disconnections with Amplifi (AFI-INS-R) AP with Powersave enable
- TWT session is failing due to disconnections observed in DUT if rx_latency is set to 55 seconds and receive data is also set to 55 seconds on MI Xiaomi RA72 and Tplink AX53 AP's
- Observed less throughput(~1Mb) while running TCP RX with Max_PSP powersave with DLink 810 AP
- Observed interop issue (random disconnections) with few APs (EERO 6+, EERO PRO 6E, Cisco Catalyst 9120AXID)
- Disconnections observed with Netgear RAX120 AP in WPA3 security
GAP
- SPI interrupt miss issue was observed that prevents the host from receiving packets delivered by the TA, when there is continuous BLE TX/RX data transfer using the ble_multiconnection_gatt_test application.
DTM/PER
- Recommend to limit BLE Tx Maximum power to 18 dBm and not to use power_index 127 for BLE HP chain.
IOP
- BLE connection failure has been observed on a few mobile devices (Samsung S23& Oneplus 9pro) when Si917 device is configured as central.
- For Coex Scenario Wi-Fi + BLE, BLE Data transfer, MU retries (~50-60%) observed while running DL MU-MIMO test.
- Observed Wi-Fi + BLE intermittent connection failures, disconnections, and data transfer stalls in the long run when power save is enabled.
- While executing Wi-Fi Commissioning using the wifi_station_ble_provisioning example, BLE is disconnecting is observed with few boards.
- Observed "DUT is not disconnecting to the AP when initiating disconnection from EFR connect app screen using wifi_station_ble_provisioning_aws example
- Observed DUT failed to load certificate with error "0x10026" (SL_STATUS_SI91X_WRONG_PARAMETERS) while running wifi_https_ble_dual_role_v6 application
- All projects in the package are compatible with GNU ARM V12.2.1 toolchain
- Project Configurator is not supported.
- WPS 2.0 PIN/PUSH, Network Manager Enhancements
- Websockets
- Matter integration with Embedded TCP/IP stack
- Enhanced buffer management, Throughput optimization
- TLS over LWIP, Network layer applications (MQTT, HTTP, etc.) over LWIP.
- Debugging utilities
- Secure communication over host interfaces (UART, SPI, SDIO)
- UART 2 Debug prints are supported only on ULP_GPIO_9.
- SiWx91x NCP connectivity FW Update Process using simplicity commander
- Spatial Re-Use, BSS Max Idle
- Provisioning using Wi-Fi AP
- Support for 8 Peripheral + 2 Central connections
- Support for BLE Mesh(4 nodes only) for limited Mesh use case
- BRD8045A and BRD8045C adapter boards does not have software API support for hardware flow control.
- Baremetal mode is not supported.
- WiSeConnect3_SDK_3.1.3 and later versions are not compatible with firmware versions prior to 1711.2.10.1.2.0.4, due to enhancements in max transmit power configuration during Wi-Fi join/connection, need to be cautious while doing OTA firmware upgrade.
- SPI configuration for ACTIVE LOW interrupt, LOAD_DEFAULT_NWP_FW_ACTIVE_LOW is not supported
- TLS 1.3 Server is not supported
- 40 MHz bandwidth for 2.4 GHz and 5 GHz band is not supported.
- A maximum of 3 SSL connections are supported in Wi-Fi alone and CoEx modes.
- In SSL ECC Curve ID supported is 23. SSL handshake with 3rd party clients depends on the SSL ECC Curve ID.
- The number of Non-Transmitting BSSIDs processed is limited by the beacon length that can be processed by the stack (which is 1024 bytes). Beacons greater than 1024 Bytes in length will not be processed.
- UL MUMIMO is not supported.
- WPA3 AP supports only H2E algorithm.
- PMKSA caching is not supported in WPA3 AP mode.
- The maximum embedded MQTT Publish payload is 1 kbyte.
- Timeout value for socket select and socket receive calls of less than 1 second is not currently supported.
- SA query procedure not supported in 11W AP mode.
- WPA3 AP transition mode is not supported.
- In Concurrent mode (AP/STA) aggregation (Tx and Rx) is not supported.
- AP standalone mode does not support Tx aggregation. Rx aggregation is supported with limited number of BA sessions.
- Embedded HTTP Server is not supported.
- mDNS with IPV6 is not supported.
- For BLE, if the connection is established with a small connection interval (less than 15 ms), simultaneous roles (i.e., Central + Scanning and Peripheral + Advertising) are not supported.
- BLE maximum two concurrent connections are supported, which can be either a connection to two peripheral devices, to one central and one peripheral device or two central devices.
- BLE Slave latency value is valid up to 32 only.
- BLE TX/RX throughput is less when tested with EFM as compared to EFR.
- Maximum supported AE data length is 200 bytes.
- Supports only two ADV_EXT sets.
- Supports only two BLE connections (1 Central and 1 Peripheral) with AE.
- Advertising Extension feature is not supported in Coexistence.
- Isochronous channels feature is not supported.
- Connection subrating feature is not supported.
- LE power controller feature is not supported.
- EATT feature is not supported.
- Periodic Advertising with response(PAwR) feature is not supported.
- BLE Audio is not supported.
- The feature of dynamically changing the TX power when extended advertising is active is not supported.
- EFR Connect mobile application doesn't have support to differentiate the BLE configurators based on the Bluetooth Device address.
- Wi-Fi AP + BLE currently not supported
| Item | Details |
|---|---|
| Release date | Mar 14th, 2024 |
| SDK Version | 3.1.4 |
| Firmware Version | 1711.2.10.1.3.0.7 |
| Package Name | WiSeConnect3_SDK_3.1.4 |
| Supported RTOS | FreeRTOS |
| Operating Modes Supported | Wi-Fi STA, Wi-Fi AP, Wi-Fi STA+BLE, Wi-Fi STA+AP |
- SiWx917 release consists of two components
- Wireless Firmware - SiWx917 Firmware Binary available as SiWG917-B.2.10.1.3.0.7.rps
- Wiseconnect3 Library - Wiseconnect3 SDK library runs on the external host in NCP mode.
- Expansion kits: SiWx917-EB4346A (based on Radio board SiWx917-4346A + 8045A Co-Processor Adapter board)
- Expansion Kits: Si917-8036B (Beta version)
- IC OPNs: SiWN917M100LGTBA (Wi-Fi 6 NCP IC, QFN 7x7, 2.4 GHz, 4MB stacked flash, -40 to +85C)
- Operating Modes
- Wi-Fi STA (802.11ax, 802.11n), Wi-Fi 802.11n AP, Wi-Fi STA (802.11ax, 802.11n) + 802.11n AP, Wi-Fi STA (802.11ax, 802.11n) + BLE
- Security
- Secure Boot, Secure Key storage and HW device identity with PUF, Secure Zone, Secure XIP (Execution in place) from flash, Secure Attestation, Anti Rollback, Secure Debug. Flash Protection
- Secure firmware upgrade options:
- Firmware loading through UART, SPI Interface
- Secure Over the Air (OTA) Upgrade
- Crypto Support
- Crypto API's for Hardware Accelerators:
- Advanced Encryption Standard (AES) 128/256/192, Secure Hash Algorithm (SHA) 256/384/512, Hash Message Authentication Code (HMAC), Random Number Generator (RNG), SHA3, AES-Galois Counter Mode (GCM)/ Cipher based Message Authentication Code (CMAC), ChaCha-poly, True Random Number Generator (TRNG)
- Software Accelerators: RSA, ECC
- Wrapping Secret keys (Symmetric crypto).
- Crypto API's for Hardware Accelerators:
- System Power Save
- Deep Sleep with RAM retention and without RAM retention
- Wireless Power Save: Connected Sleep (Wi-Fi Standby Associated), BLE Advertising with powersave, BLE Scan with powersave , BLE connection with powersave. Only Max PSP power save mode is supported in BLE
- Wi-Fi Protocols
- IEEE 802.11 b/g/n/ax (2.4GHz)
- Access Point (AP) Mode
- 4 Client Support, Hidden SSID Mode, Auto Channel Selection, Scan in AP mode (Alpha Version).
- Wi-Fi Security
- WPA2 Personal, WPA3 Personal (H2E method only) (Alpha Version), WPA Mixed mode (WPA/WPA2)
- Wi-Fi Scan
- Selective Scan, Active/Passive Scan
- Wi-Fi STA (Security Modes)
- Open Mode, WPA2 Personal, WPA2 Enhancements, WPA3 Personal, Mixed Mode (WPA/WPA2), WPA3 Personal Transition Mode (WPA2/WPA3)
- WPA2 Enterprise security (STA)
- Method
- PEAP/TTLS/TLS 1.0/TLS 1.2/FAST
- Method
- Wi-Fi STA Rejoin
- Wi-Fi STA Roaming
- BG Scan, OKC (Opportunistic Key caching), PMK (Pairwise Master Key) caching, Pre-Authentication
- Wi-Fi Protocol Power Save
- Deep sleep (unconnected state), Max PSP, Enhanced Max PSP, Fast PSP, TWT
- QoS
- WMM-QoS
- Wi-Fi 6 Feature
- MUMIMO (DL), OFDMA (UL/DL), iTWT, TWT I-Frame & TWT Enhancements, BSS coloring, MBSSID
- Wi-Fi Concurrency
- AP+STA (Same channel)
- Wi-Fi Band/Channels
- 2.4GHz CH1-11, 2.4GHz CH1-13, 2.4GHz CH1-14 (Japan)
- Known Security Vulnerabilities Handled
- WPA2 KRACK Attacks, Fragment and Forge Vulnerability
- Core Networking Features
- TCP/IP Bypass (LWIP as Hosted stack for reference), IPv4/IPv6/UDP/TCP/ARP/ICMP/ICMPv6
- SSL client versions TLSV1.0, TLSV1.2, TLSV1.3
- SSL server versions TLSV1.0 and TLSV1.2
- DHCPv4 (Client/Server)/ DHCPv6 Client
- Advanced Network Features
- HTTP Client/HTTPS Client//DNS Client/SNTP Client, Embedded MQTT/MQTT on host
- Wi-Fi IoT Cloud Integration
- AWS IOT Core
- BSD and IoT sockets application programming interface(API)
- GAP(Advertising, Scanning, initiation, Connection and Bonding)
- Generic Attribute Protocol(GATT)
- Attribute protocol(ATT)
- Security
- LL Privacy 1.2
- Accept list
- Directed Advertising
- Extended Advertising
- Periodic Advertising
- Periodic Advertising scanning
- Extended Advertising scanning
- Periodic Advertising list
- LE periodic advertising synchronization
- LE PHY(1Mbps, 2Mbps) & Coded PHY(125Kbps, 500kbps)
- Simultaneous scanning on 1Mbps and Coded PHY
- LE dual role topology
- LE data packet length extensions(DLE)
- Asymmetric PHYs
- LE channel selection algorithm 2 (CSA#2)
- LE Secure connections
- Bluetooth 5.4 Qualified
- Simplified and Unified DX for Wi-Fi API
- Simplifies application development and presents clean and standardized APIs
- BSD and ARM IoT-compliant socket API
- Available through Simplicity Studio and GitHub
- Wi-Fi STA + BLE
- 3 wire coex acting as Wi-Fi with external Bluetooth
- 3 wire coex acting as Wi-Fi with external Zigbee/OT
- Enhancements
- None.
- Fixed Issues
- None.
- Enhancements
- Added support for HTTP Server and provided demo application.
- Added multithreaded support for the Concurrent mode demo(Alpha).
- Added IPv6 support in AWS IoT MQTT Client application.
- Added API support to get socket information from firmware.
- Added support for featured and few snippet demos on SPI interface over STM32 (Alpha).
- Added support for NCP over UART interface (Alpha).
- Enhancements in throughput over SPI interface.
- Fixed Issues
- Updated the missing error codes in the documentation.
- Fixed SNTP client stop issue.
- Enhancements
- Added support to configure IPv6 link local address from the host while skipping the configuration of IPv6 unique global address for the network interface.
- Added support for configuration of SU Beamforming capability
- Added DNS-SD record in the MDNS query response to allow discovery of DUT's MDNS service with consistency.
- Fixed Issues
- Resolved Server side dependency to repeat the firmware binary header (64 bytes).
- Fixed MBSSID feature Interop issue with WiFi7 AP.
- Enhancements
- Added BLE error code details in 917 documentation
- Added support for NCP over SPI interface using STM32 for BLE_PER demo .
- Added support for NCP over UART interface for few BLE demos (ble_ae_central, ble_power_save, ble_throughput_app, ble_ae_peripheral and ble_per.).
- Fixed Issues
- Resolved the BLE hang issue when DUT was trying to connect to the nRf dongle with I/O capability as 0x00.
- Resolved issue where DUT stopped transmitting scan request and scan response packets over air after 15 seconds while running the ble_multiconnection_gatt_test application.
- Enhancements
- Added support for 3 SSL sockets in CoEx mode.
- Added NCP-UART Support for Wi-Fi Client BLE Provisioning with AWS example.
- Fixed Issues
- None
- Set the recommended Power Save Profile (PSP) type to Enhanced Max PSP.
- Memory configuration for NCP mode is 672K_M4SS_0K.
- Simplicity Studio. This release is tested with SV5.8.0 version.
- Refer to the latest version of the NCP "Getting-Started-with-SiWx917" guide for more details
- It is recommended to enable bit 16 of the 'Extended TCP IP Feature' bit map in the opermode command for all Wi-Fi Socket operations from the host to ensure graceful handling during asynchronous closures from the peer.
- For high throughput applications, aggregation (bit 2 of feature_bit_map) is recommended to be enabled in opermode.
- To reset TA (NWP), the application needs to call sl_wifi_deinit() followed by sl_wifi_init().
- Users can enable SL_SI91X_EXT_TCP_IP_SSL_16K_RECORD in 'Extended TCP IP Feature' bit map in opermode for (HTTPS server) supporting 16k record.
- TWT
- Recommendation is to use sl_wifi_target_wake_time_auto_selection() API for all TWT applications.
- It is recommended to issue iTWT setup command once IP assignment, TCP connection, application specific socket connections are done.
- When using sl_wifi_enable_target_wake_time API, increase TCP / ARP Timeouts at the remote side depending upon the configured TWT interval configured. It's highly recommended to use sl_wifi_target_wake_time_auto_selection() as an alternative.
- In case of TWT in coex mode, when using sl_wifi_enable_target_wake_time API, use TWT wake duration <= 16 ms and TWT wake interval >= 1 sec. If wake duration > 16 ms or TWT wake interval < 1sec, there might be performance issues.
- For iTWT GTK interval in AP should be configured to max possible value or zero. If GTK interval is not configurable on AP side, recommended TWT interval (in case of sl_wifi_enable_target_wake_time API) or RX Latency (in case of sl_wifi_target_wake_time_auto_selection API) is less than 4sec.
- When sl_wifi_enable_target_wake_time API is used, configuring TWT Wake interval beyond 1 min might lead to disconnections from the AP. Recommended to use TWT wake interval of less than or equal to 1 min.
- When using sl_wifi_enable_target_wake_time API, it is recommended to set missed_beacon_count of sl_wifi_set_advanced_client_configuration API greater than 2 times of the configured TWT Interval.
- Disable power save for high throughput applications or use FAST PSP power save mode as per application requirement.
- The application needs to ensure that it sets RTC with the correct timestamp before establishing the SSL/EAP connection.
- The minimum timeout value should not be less than 1 second for socket select and socket receive calls.
- Embedded MQTT keep alive interval should be either 0 or a value greater than 35 seconds.
- Disable power save and suspend any active TWT sessions before triggering HTTP OTAF.
- Randomize the client port if using rapid connect/disconnect of the MQTT session on the same client port with the power save.
- In BLE, the recommended range of Connection Interval in
- Power Save (BLE Only) - 100 ms to 1.28 s.
- In BLE, during Connection, the configuration of Scan Interval and Scan Window with the same value is not recommended. The suggested ratio of Scan Window to Scan Interval is 3:4.
- In BLE, if a device is acting as Central, the scan window (in set_scan_params and create_connection commands) must be less than the existing Connection Interval. The suggested ratio of Scan Window to Connection Interval is 2:3.
- In BLE mode, if scanning and advertising are in progress on the SiWx91x module and it subsequently gets connected and moves to the central role, scanning stops else if it moves to the peripheral role, advertising stops. To further establish a connection to another peripheral device or to a central device, the application should give a command for starting advertising and scanning again.
- For concurrent Wi-Fi + BLE, and while a Wi-Fi connection is active, we recommend setting the ratio of the BLE scan window to BLE scan interval to 1:3 or 1:4.
- Wi-Fi + BLE Advertising
- All standard advertising intervals are supported. As Wi-Fi throughput is increased, a slight difference in on-air advertisements compared to configured intervals may be observed.
- BLE advertising is skipped if the advertising interval collides with Wi-Fi activity.
- Wi-Fi + BLE scanning
- All standard scan intervals are supported. For better scan results, we recommend setting the ratio of the BLE scan window to BLE scan interval to 1:3 or 1:4.
- BLE scanning will be stopped for intervals that collide with Wi-Fi activity.
- Wi-Fi + BLE Central/Peripheral Connections
- All standard connection intervals are supported.
- 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 achieve higher throughput for both Wi-Fi and BLE, use medium connection intervals, such as 45 to 80 ms with maximum supervision timeout.
- Ensure Wi-Fi activity consumes lower intervals.
- None
- Enhanced sl_wifi_get_firmware_version() API to provide more details (ROM ID, chip ID, security version, etc) which is not backward compatible with firmwares older than 1711.2.10.1.0.0.4. Firmware binary notation does not include security version number.
- Observed not being able to receive UDP Rx TPUT print at Teraterm with IPV6 Throughput example
- Matter extension based applications are experiencing compatibility issues with WiseConnect SDK 3.1.4. It is recommended to use WiseConnect SDK 3.1.1 for matter-related applications. This will be addressed in up coming release(s).
- Asynchronous Azure MQTT is not supported, this will be addressed in up coming release(s).
- Power Save with TCP/IP is not supported for UART interface.
- CLI_DEMO and Calibration demo are not supported over UART interface.
- Recommended to configure VAP_ID properly for Si91x STA and AP using sl_si91x_setsockopt_async(), in case of data transfer.
- Recommended to use valid length(<= 202 bytes) for topic to be published in the "Embedded MQTT" demo, else it leads to return wrong error code(0x21).
Wi-Fi STA
- STA Connection with the WPA3 Hunting and Pecking algorithm takes about 3-4 seconds.
- Observed connection failures with some APs in more channel congestion ~50-60% occupancy open lab environment.
- Region selection based on country IE in the beacon is not supported
- Observed intermittent beacon reception from Access Point ( beacon misses) in an extremely congested environment
Access Point (AP) Mode
- Scan feature in AP mode not fully functional.
- Fixed rate configuration in AP mode using sl_wifi_set_transmit_rate API is not being set as expected.
WPA2 Enterprise security (STA)
- Observed issue with configuring certificate key and programming 4096 bit key and SHA384/SHA512 certificates.
- Observing DUT is throwing 0x1001c when configuring .data.certificate_key as "123456789"
- Configuration issue to program PAC file for EAP FAST Manual mode
- Issue observed with WPA2 Enterprise Connectivity using Microsoft RADIUS Server.
Wi-Fi Concurrency ( AP + STA in same channel)
- Observed 3rd party STA association fail with 917 AP while 917 STA mode is connecting/reconnecting to configured 3rd party AP. Reconnect 3rd party STA to 917 AP in such scenarios.
OFDMA (UL/DL)
- Less throughput observed in DL-OFDMA with some APs that enabled LDPC.
MUMIMO (DL)
- For Coex Scenario Wi-Fi + BLE, BLE Data transfer, MU retries (~50-60%) observed while running DL MU-MIMO test.
- Observed Performance, Interop issues with MU MIMO with certain APs.
- Less throughput was observed in MU-MIMO with some APs that enabled LDPC.
MU-MIMO (UL)
- UL MU-MIMO is not supported.
TWT
- Variability with MQTT keep alive interval based on TWT wake up interval.
- When sl_wifi_enable_target_wake_time() API is used, occasional MQTT disconnections may be observed if TWT is configured with longer TWT intervals (>30secs) with embedded MQTT + TWT. As an alternative, it's highly recommended to use sl_wifi_target_wake_time_auto_selection() API, where these dependencies are internally handled.
Wi-Fi STA Rejoin
- observed Scanning (probe request) in all channels instead of the channels configured in selective channel(channel_bitmap_2g4) during rejoin process
IPv4/IPv6
- Observed issue with assigning static IP to DUT
- IP change notification is not indicated to the application
BSD Socket API
- Configuration issue to program TCP retry count (default 10) through setsockopt
- Every server socket created consumes a socket (maximum of 10 sockets supported) and every subsequent connection to server socket consumes an additional socket (from the same pool of 10 sockets), which limits the number of server connections supported.
SSL Client/Server
- Sometimes during SSL Handshake, ECC curve parameters generated are wrong, resulting in connection failure with BBD2 error. However, this recovers in the next attempt.
- Secure SSL renegotiation not supported in Embedded Networking Stack
- observed connection failures with ECDSA ciphers
HTTP Client/ HTTPS Client
- Observed occasional HTTPS continuous download failures when power save is enabled. Recommended to disable it before performing HTTPS continuous downloads
- Observed HTTPS post data is failing with error code: BBE2 (HTTP Failed).Unable to get HTTP GET response when http length is exceeding 1024 bytes when SL_SI91X_FEAT_LONG_HTTP_URL bit is disabled.
SNTP
- Unable to get SNTP async events when coex mode and power save are enabled
Throughputs & Performance
- Observed 20% less Wi-Fi throughput with SDK 3.x compare to target throughput (depends on host and host interface), SDK refinements are in progress
Secure Over the Air (OTA) Upgrade
- Observed firmware upgrade failures after multiple iterations
- Observed OTA failures with power save enabled, So recommended to disable power save during OTA
- Observed "0xffffffff" error at the remote end while doing firmware upgrade via TCP server using (featured) example with ubuntu 21.0x.
Wi-Fi IOT Cloud integration (AWS IOT Core)
- Observed AWS MQTT keepalive transmission is not happening at expected intervals with power save enabled.
Wi-Fi Interoperability (IOP)
- Observed disconnections with Amplifi (AFI-INS-R) AP with Powersave enable
- TWT session is failing due to disconnections observed in DUT if rx_latency is set to 55 seconds and receive data is also set to 55 seconds on MI Xiaomi RA72 and Tplink AX53 AP's
- Observed less throughput(~1Mb) while running TCP RX with Max_PSP powersave with DLink 810 AP
- Observed interop issue (random disconnections) with few APs (EERO 6+, EERO PRO 6E, Cisco Catalyst 9120AXID)
- Disconnections observed with Netgear RAX120 AP in WPA3 security
GAP
- BLE start advertising API failed with an error code 0xffffffe2(RSI_ERROR_RESPONSE_TIMEOUT) within 5minutes while executing ble start ,stop and clear the address resolution API's are called in a loop continuously.
- DUT stop transmitting scan request and scan response packets over air after 15 seconds while running the ble_multiconnection_gatt_test application.
- SPI interrupt miss issue was observed that prevents the host from receiving packets delivered by the TA, when there is continuous BLE TX/RX data transfer using the ble_multiconnection_gatt_test application.
DTM/PER
- Recommend to limit BLE Tx Maximum power to 18 dBm and not to use power_index 127 for BLE HP chain.
- BLE PER stats API returns error code: 0xFFFFFFE2 (RSI_ERROR_RESPONSE_TIMEOUT) in transmit mode after sometime.
IOP
- BLE connection failure has been observed on a few mobile devices (Samsung S23& Oneplus 9pro) when Si917 device is configured as central.
- For Coex Scenario Wi-Fi + BLE, BLE Data transfer, MU retries (~50-60%) observed while running DL MU-MIMO test.
- Observed Wi-Fi + BLE intermittent connection failures, disconnections, and data transfer stalls in the long run when power save is enabled.
- While executing Wi-Fi Commissioning using the wifi_station_ble_provisioning example, BLE is disconnecting is observed with few boards.
- Observed "DUT is not disconnecting to the AP when initiating disconnection from EFR connect app screen using wifi_station_ble_provisioning_aws example
- All projects in the package are compatible with GNU ARM V12.2.1 toolchain
- Project Configurator is not supported.
- WPS 2.0 PIN/PUSH, Network Manager Enhancements
- MDNS, HTTP Server, Azure MQTT Client, Websockets
- Matter integration with Embedded TCP/IP stack
- Enhanced buffer management, Throughput optimization
- TLS over LWIP, Network layer applications (MQTT, HTTP, etc.) over LWIP.
- Debugging utilities
- Secure communication over host interfaces (UART. SPI, SDIO)
- UART 2 Debug prints are supported only on ULP_GPIO_9.
- Spatial Re-Use, BSS Max Idle
- Provisioning using Wi-Fi AP
- Support for 8 Peripheral + 2 Central connections
- Support for BLE Mesh(4 nodes only) for limited Mesh use case
- None
- Baremetal mode is not supported.
- WiSeConnect3_SDK_3.1.3 and later versions are not compatible with firmware versions prior to 1711.2.10.1.2.0.4, due to enhancements in max transmit power configuration during Wi-Fi join/connection, need to be cautious while doing OTA firmware upgrade.
- TLS 1.3 Server is not supported
- 40 MHz bandwidth for 2.4 GHz band is not supported.
- A maximum of 3 SSL connections are supported in Wi-Fi alone and CoEx modes.
- In SSL ECC Curve ID supported is 23. SSL handshake with 3rd party clients depends on the SSL ECC Curve ID.
- The number of Non-Transmitting BSSIDs processed is limited by the beacon length that can be processed by the stack (which is 1024 bytes). Beacons greater than 1024 Bytes in length will not be processed.
- UL MUMIMO is not supported.
- WPA3 AP supports only H2E algorithm.
- PMKSA caching is not supported in WPA3 AP mode.
- The maximum embedded MQTT Publish payload is 1 kbyte.
- Timeout value for socket select and socket receive calls of less than 1 second is not currently supported.
- SA query procedure not supported in 11W AP mode.
- WPA3 AP transition mode is not supported.
- For BLE, if the connection is established with a small connection interval (less than 15 ms), simultaneous roles (i.e., Central + Scanning and Peripheral + Advertising) are not supported.
- BLE maximum two concurrent connections are supported, which can be either a connection to two peripheral devices, to one central and one peripheral device or two central devices.
- BLE Slave latency value is valid up to 32 only.
- BLE TX/RX throughput is less when tested with EFM as compared to EFR.
- Maximum supported AE data length is 200 bytes.
- Supports only two ADV_EXT sets.
- Supports only two BLE connections (1 Central and 1 Peripheral) with AE.
- Advertising Extension feature is not supported in Coexistence.
- Isochronous channels feature is not supported.
- Connection subrating feature is not supported.
- LE power controller feature is not supported.
- EATT feature is not supported.
- Periodic Advertising with response(PAwR) feature is not supported.
- BLE Audio is not supported.
- The feature of dynamically changing the TX power when extended advertising is active is not supported.
- Wi-Fi AP + BLE currently not supported
| Item | Details |
|---|---|
| Release date | Feb 14th, 2024 |
| SDK Version | 3.1.3 |
| Firmware Version | 1711.2.10.1.2.0.4 |
| Package Name | WiSeConnect3_SDK_3.1.3 |
| Supported RTOS | FreeRTOS |
| Operating Modes Supported | Wi-Fi STA, Wi-Fi AP, Wi-Fi STA+BLE, Wi-Fi STA+AP |
- SiWx917 release consists of two components
- Wireless Firmware - SiWx917 Firmware Binary available as SiWG917-B.2.10.1.2.0.4.rps
- Wiseconnect3 Library - Wiseconnect3 SDK library runs on the external host in NCP mode.
- Expansion kits: SiWx917-EB4346A (based on Radio board SiWx917-4346A + 8045A Co-Processor Adapter board)
- Expansion Kits: Si917-8036B (Beta version)
- IC OPNs: SiWN917M100LGTBA (Wi-Fi 6 NCP IC, QFN 7x7, 2.4 GHz, 4MB stacked flash, -40 to +85C)
- Operating Modes
- Wi-Fi STA (802.11ax, 802.11n), Wi-Fi 802.11n AP, Wi-Fi STA (802.11ax, 802.11n) + 802.11n AP, Wi-Fi STA (802.11ax, 802.11n) + BLE
- Security
- Secure Boot, Secure Key storage and HW device identity with PUF, Secure Zone, Secure XIP (Execution in place) from flash, Secure Attestation, Anti Rollback, Secure Debug. Flash Protection
- Secure firmware upgrade options:
- Firmware loading through UART, SPI Interface
- Secure Over the Air (OTA) Upgrade
- Crypto Support
- Advanced Encryption Standard (AES) 128/256/192, Secure Hash Algorithm (SHA) 256/384/512, Hash Message Authentication Code (HMAC), Random Number Generator (RNG), SHA3, AES-Galois Counter Mode (GCM)/ Cipher based Message Authentication Code (CMAC), ChaCha-poly, True Random Number Generator (TRNG)
- Software Accelerators: RSA, ECC
- Integrated with mbed TLS
- System Power Save
- Deep Sleep with RAM retention and without RAM retention
- Wireless Power Save: Connected Sleep (Wi-Fi Standby Associated), BLE Advertising with powersave, BLE Scan with powersave , BLE connection with powersave. Only Max PSP power save mode is supported in BLE
- Wi-Fi Protocols
- IEEE 802.11 b/g/n/ax (2.4GHz)
- Access Point (AP) Mode
- 4 Client Support, Hidden SSID Mode, Auto Channel Selection, Scan in AP mode (Alpha Version).
- Wi-Fi Security
- WPA2 Personal, WPA3 Personal (H2E method only) (Alpha Version), WPA Mixed mode (WPA/WPA2)
- Wi-Fi Scan
- Selective Scan, Active/Passive Scan
- Wi-Fi STA (Security Modes)
- Open Mode, WPA2 Personal, WPA2 Enhancements, WPA3 Personal, Mixed Mode (WPA/WPA2), WPA3 Personal Transition Mode (WPA2/WPA3)
- WPA2 Enterprise security (STA)
- Method
- PEAP/TTLS/TLS 1.0/TLS 1.2/FAST
- Method
- Wi-Fi STA Rejoin
- Wi-Fi STA Roaming
- BG Scan, OKC (Opportunistic Key caching), PMK (Pairwise Master Key) caching, Pre-Authentication
- Wi-Fi Protocol Power Save
- Deep sleep (unconnected state), Max PSP, Enhanced Max PSP, Fast PSP,** TWT
- QoS
- WMM-QoS
- Wi-Fi 6 Feature
- MUMIMO (DL), OFDMA (UL/DL), iTWT, TWT I-Frame & TWT Enhancements, BSS coloring, MBSSID
- Wi-Fi Concurrency
- AP+STA (Same channel)
- Wi-Fi Band/Channels
- 2.4GHz CH1-11, 2.4GHz CH1-13, 2.4GHz CH1-14 (Japan)
- Known Security Vulnerabilities Handled
- WPA2 KRACK Attacks, Fragment and Forge Vulnerability
- Core Networking Features
- TCP/IP Bypass (LWIP as Hosted stack for reference), IPv4/IPv6/UDP/TCP/ARP/ICMP/ICMPv6
- SSL client versions TLSV1.0, TLSV1.2, TLSV1.3
- SSL server versions TLSV1.0 and TLSV1.2
- DHCPv4 (Client/Server)/ DHCPv6 Client
- Advanced Network Features
- HTTP Client/HTTPS Client//DNS Client/SNTP Client, Embedded MQTT/MQTT on host
- Wi-Fi IoT Cloud Integration
- AWS IOT Core
- BSD and IoT sockets application programming interface(API)
- GAP(Advertising, Scanning, initiation, Connection and Bonding)
- Generic Attribute Protocol(GATT)
- Attribute protocol(ATT)
- Security
- LL Privacy 1.2
- Accept list
- Directed Advertising
- Extended Advertising
- Periodic Advertising
- Periodic Advertising scanning
- Extended Advertising scanning
- Periodic Advertising list
- LE periodic advertising synchronization
- LE PHY(1Mbps, 2Mbps) & Coded PHY(125Kbps, 500kbps)
- Simultaneous scanning on 1Mbps and Coded PHY
- LE dual role topology
- LE data packet length extensions(DLE)
- Asymmetric PHYs
- LE channel selection algorithm 2 (CSA#2)
- LE Secure connections
- Bluetooth 5.4 Qualified
- Simplified and Unified DX for Wi-Fi API
- Simplifies application development and presents clean and standardized APIs
- BSD and ARM IoT-compliant socket API
- Available through Simplicity Studio and GitHub
- Wi-Fi STA + BLE
- 3 wire coex acting as Wi-Fi with external Bluetooth
- 3 wire coex acting as Wi-Fi with external Zigbee/OT
- Enhancements
- Enhancements done in power save module to address few stability issues
- Fixed Issues
- Fixed De-init issue for the system which do not support XTAL.
- Enhancements
- Added mDNS feature support (Alpha Version).
- Added Azure Freertos middleware SDK Support (Alpha Version).
- Added "wifi_http_otaf_twt" demo.
- Added "Wi-Fi - Azure IoT MQTT Client" demo.
- Added support for NCP over the UART interface (Alpha version).
- Added sl_si91x_set_fast_fw_up() and sl_si91x_upgrade_firmware() APIs for firmware upgrade.
- Added callback support for handling TCP remote terminate event.
- Added support for wild cards in MQTT subscription.
- Added sl_sntp_client_get_time() API to get epoch time for SNTP.
- Replaced licensed third party certificates with prototype certs for AWS and Azure.
- It is recommended to enable bit 12 of the 'Feature bit map' in the opermode command for enabling long sized ICMP packet support.
- Added support in SDK to set absolute power value in scan and join commands.
- Added wifi6 support in PER mode for CLI demo.
- Added "ble_multiconnection_gatt_test" demo.
- Added "ble_unified_ae_coex_app" demo.
- Fixed Issues
- In the STM32 demo applications, fixed the yield functionality issues with the priorities assigned to the other tasks vs timer task in STM32 demo applications.
- Fixed MQTT returning an error when the incoming publish packet length is greater than 64 bytes.
- Fixed Http client de-init hang issue when wlan disconnect occurs.
- Fixed issues with Asynchronous socket select.
- Updated Korea region configuration.
- Fixed issues in OOB demo.
- Fixed issues in standard curve parameters for SECP192R1 curve.
- Modified RSI_HT_CAPS_BIT_MAP to support 20MHz channel width only.
- Enhancements
- Added Long URL support of 2048 bytes for HTTP Get Command.
- Added support for Transition Disable Indication (TDI) in AP mode. It is an indication from an Si91x AP to WPA2/3 STA, that the STA is to disable certain transition modes for subsequent connections to the AP's network.
- Implemented beacon stop feature in AP mode.
- Enabled HT Caps in AP mode for high throughputs.
- Increased the topic length and username length size for Embedded MQTT Publish and Subscribe.
- Fixed Issues
- Added support for wrapping functionality for unaligned key length.
- Enhancements
- None
- Fixed Issues
- Fixed the issue where connectable directed advertising exited without establishing a connection with the central device.
- Fixed issue where device is throwing an error when it tried to re-enabling AE ADV after establishing an AE connection with two adverting sets.
- Fixed AE connection fail issue when remote device transmitting AUX ADV packets with Coded PHY rates.
- Enhancements
- None
- Fixed Issues
- Fixed issue where device sometimes failed to respond to connection update request in CoEx which is causing BLE disconnection.
- Set the recommended Power Save Profile (PSP) type to Enhanced Max PSP.
- Memory configuration for NCP mode is 672K_M4SS_0K.
- Simplicity Studio. This release is tested with SV5.8.0 version.
- Refer to the latest version of the NCP "Getting-Started-with-SiWx917" guide for more details
- It is recommended to enable bit 16 of the 'Extended TCP IP Feature' bit map in the opermode command for all Wi-Fi Socket operations from the host to ensure graceful handling during asynchronous closures from the peer.
- For high throughput applications, aggregation (bit 2 of feature_bit_map) is recommended to be enabled in opermode.
- To reset TA (NWP), the application needs to call sl_wifi_deinit() followed by sl_wifi_init().
- Users can enable SL_SI91X_EXT_TCP_IP_SSL_16K_RECORD in 'Extended TCP IP Feature' bit map in opermode for (HTTPS server) supporting 16k record.
- TWT
- Recommendation is to use sl_wifi_target_wake_time_auto_selection() API for all TWT applications.
- It is recommended to issue iTWT setup command once IP assignment, TCP connection, application specific socket connections are done.
- When using sl_wifi_enable_target_wake_time API, increase TCP / ARP Timeouts at the remote side depending upon the configured TWT interval configured. It's highly recommended to use sl_wifi_target_wake_time_auto_selection() as an alternative.
- In case of TWT in coex mode, when using sl_wifi_enable_target_wake_time API, use TWT wake duration <= 16 ms and TWT wake interval >= 1 sec. If wake duration > 16 ms or TWT wake interval < 1sec, there might be performance issues.
- For iTWT GTK interval in AP should be configured to max possible value or zero. If GTK interval is not configurable on AP side, recommended TWT interval (in case of sl_wifi_enable_target_wake_time API) or RX Latency (in case of sl_wifi_target_wake_time_auto_selection API) is less than 4sec.
- When sl_wifi_enable_target_wake_time API is used, configuring TWT Wake interval beyond 1 min might lead to disconnections from the AP. Recommended to use TWT wake interval of less than or equal to 1 min.
- When using sl_wifi_enable_target_wake_time API, it is recommended to set missed_beacon_count of sl_wifi_set_advanced_client_configuration API greater than 2 times of the configured TWT Interval.
- Disable power save for high throughput applications or use FAST PSP power save mode as per application requirement.
- The application needs to ensure that it sets RTC with the correct timestamp before establishing the SSL/EAP connection.
- The minimum timeout value should not be less than 1 second for socket select and socket receive calls.
- Embedded MQTT keep alive interval should be either 0 or a value greater than 35 seconds.
- Disable power save and suspend any active TWT sessions before triggering HTTP OTAF.
- Randomize the client port if using rapid connect/disconnect of the MQTT session on the same client port with the power save.
- In BLE, the recommended range of Connection Interval in
- Power Save (BLE Only) - 100 ms to 1.28 s.
- In BLE, during Connection, the configuration of Scan Interval and Scan Window with the same value is not recommended. The suggested ratio of Scan Window to Scan Interval is 3:4.
- In BLE, if a device is acting as Central, the scan window (in set_scan_params and create_connection commands) must be less than the existing Connection Interval. The suggested ratio of Scan Window to Connection Interval is 2:3.
- In BLE mode, if scanning and advertising are in progress on the SiWx91x module and it subsequently gets connected and moves to the central role, scanning stops else if it moves to the peripheral role, advertising stops. To further establish a connection to another peripheral device or to a central device, the application should give a command for starting advertising and scanning again.
- For concurrent Wi-Fi + BLE, and while a Wi-Fi connection is active, we recommend setting the ratio of the BLE scan window to BLE scan interval to 1:3 or 1:4.
- Wi-Fi + BLE Advertising
- All standard advertising intervals are supported. As Wi-Fi throughput is increased, a slight difference in on-air advertisements compared to configured intervals may be observed.
- BLE advertising is skipped if the advertising interval collides with Wi-Fi activity.
- Wi-Fi + BLE scanning
- All standard scan intervals are supported. For better scan results, we recommend setting the ratio of the BLE scan window to BLE scan interval to 1:3 or 1:4.
- BLE scanning will be stopped for intervals that collide with Wi-Fi activity.
- Wi-Fi + BLE Central/Peripheral Connections
- All standard connection intervals are supported.
- 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 achieve higher throughput for both Wi-Fi and BLE, use medium connection intervals, such as 45 to 80 ms with maximum supervision timeout.
- Ensure Wi-Fi activity consumes lower intervals.
- None
- Enhanced sl_wifi_get_firmware_version() API to provide more details (ROM ID, chip ID, security version, etc) which is not backward compatible with firmwares older than 1711.2.10.1.0.0.4. Firmware binary notation does not include security version number.
- Observed not being able to receive UDP Rx TPUT print at Teraterm with IPV6 Throughput example
- Matter applications are experiencing compatibility issues with WiseConnect SDK 3.1.2. It is recommended to use WiseConnect SDK 3.1.1 for matter-related applications. This will be addressed in up coming release(s).
- Asynchronous Azure MQTT is not supported, this will be addressed in up coming release(s).
- Disable power save before making TCP connection for UART interface.
Wi-Fi STA
- STA Connection with the WPA3 Hunting and Pecking algorithm takes about 3-4 seconds.
- Observed connection failures with some APs in more channel congestion ~50-60% occupancy open lab environment.
- Region selection based on country IE in the beacon is not supported
- Observed intermittent beacon reception from Access Point ( beacon misses) in an extremely congested environment
Access Point (AP) Mode
- Scan feature in AP mode not fully functional.
- Fixed rate configuration in AP mode using sl_wifi_set_transmit_rate API is not being set as expected.
WPA2 Enterprise security (STA)
- Observed issue with configuring certificate key and programming 4096 bit key and SHA384/SHA512 certificates.
- Observing DUT is throwing 0x1001c when configuring .data.certificate_key as "123456789"
- Configuration issue to program PAC file for EAP FAST Manual mode
- Issue observed with WPA2 Enterprise Connectivity using Microsoft RADIUS Server.
Wi-Fi Concurrency ( AP + STA in same channel)
- Observed 3rd party STA association fail with 917 AP while 917 STA mode is connecting/reconnecting to configured 3rd party AP. Reconnect 3rd party STA to 917 AP in such scenarios.
OFDMA (UL/DL)
- Less throughput observed in DL-OFDMA with some APs that enabled LDPC.
MUMIMO (DL)
- For Coex Scenario Wi-Fi + BLE, BLE Data transfer, MU retries (~50-60%) observed while running DL MU-MIMO test.
- Observed Performance, Interop issues with MU MIMO with certain APs.
- Less throughput was observed in MU-MIMO with some APs that enabled LDPC.
MU-MIMO (UL)
- UL MU-MIMO is not supported.
TWT
- Variability with MQTT keep alive interval based on TWT wake up interval.
- When sl_wifi_enable_target_wake_time() API is used, occasional MQTT disconnections may be observed if TWT is configured with longer TWT intervals (>30secs) with embedded MQTT + TWT. As an alternative, it's highly recommended to use sl_wifi_target_wake_time_auto_selection() API, where these dependencies are internally handled.
Wi-Fi STA Rejoin
- observed Scanning (probe request) in all channels instead of the channels configured in selective channel(channel_bitmap_2g4) during rejoin process
IPv4/IPv6
- Observed issue with assigning static IP to DUT
- IP change notification is not indicated to the application
BSD Socket API
- Configuration issue to program TCP retry count (default 10) through setsockopt
- Every server socket created consumes a socket (maximum of 10 sockets supported) and every subsequent connection to server socket consumes an additional socket (from the same pool of 10 sockets), which limits the number of server connections supported.
SSL Client/Server
- Sometimes during SSL Handshake, ECC curve parameters generated are wrong, resulting in connection failure with BBD2 error. However, this recovers in the next attempt.
- Secure SSL renegotiation not supported in Embedded Networking Stack
- observed connection failures with ECDSA ciphers
HTTP Client/ HTTPS Client
- Observed occasional HTTPS continuous download failures when power save is enabled. Recommended to disable it before performing HTTPS continuous downloads
- Observed HTTPS post data is failing with error code: BBE2 (HTTP Failed).Unable to get HTTP GET response when http length is exceeding 1024 bytes when SL_SI91X_FEAT_LONG_HTTP_URL bit is disabled.
SNTP
- Unable to get SNTP async events when coex mode and power save are enabled
Throughputs & Performance
- Observed 20% less Wi-Fi throughput with SDK 3.x compare to target throughput (depends on host and host interface), SDK refinements are in progress
Secure Over the Air (OTA) Upgrade
- Observed firmware upgrade failures after multiple iterations
- Observed OTA failures with power save enabled, So recommended to disable power save during OTA
- Observed "0xffffffff" error at the remote end while doing firmware upgrade via TCP server using (featured) example with ubuntu 21.0x.
Wi-Fi IOT Cloud integration (AWS IOT Core)
- Observed AWS MQTT keepalive transmission is not happening at expected intervals with power save enabled.
Wi-Fi Interoperability (IOP)
- Observed disconnections with Amplifi (AFI-INS-R) AP with Powersave enable
- TWT session is failing due to disconnections observed in DUT if rx_latency is set to 55 seconds and receive data is also set to 55 seconds on MI Xiaomi RA72 and Tplink AX53 AP's
- Observed less throughput(~1Mb) while running TCP RX with Max_PSP powersave with DLink 810 AP
- Observed interop issue (random disconnections) with few APs (EERO 6+, EERO PRO 6E, Cisco Catalyst 9120AXID)
- Disconnections observed with Netgear RAX120 AP in WPA3 security
GAP
- BLE start advertising API failed with an error code 0xffffffe2(RSI_ERROR_RESPONSE_TIMEOUT) within 5minutes while executing ble start ,stop and clear the address resolution API's are called in a loop continuously.
- DUT stop transmitting scan request and scan response packets over air after 15 seconds while running the ble_multiconnection_gatt_test application.
- SPI interrupt miss issue was observed that prevents the host from receiving packets delivered by the TA, when there is continuous BLE TX/RX data transfer using the ble_multiconnection_gatt_test application.
DTM/PER
- Recommend to limit BLE Tx Maximum power to 18 dBm and not to use power_index 127 for BLE HP chain.
IOP
- BLE connection failure has been observed on a few mobile devices (Samsung S23& Oneplus 9pro) when Si917 device is configured as central.
- For Coex Scenario Wi-Fi + BLE, BLE Data transfer, MU retries (~50-60%) observed while running DL MU-MIMO test.
- Observed Wi-Fi + BLE intermittent connection failures, disconnections, and data transfer stalls in the long run when power save is enabled.
- While executing Wi-Fi Commissioning using the wifi_station_ble_provisioning example, BLE is disconnecting is observed with few boards.
- Observed "DUT is not disconnecting to the AP when initiating disconnection from EFR connect app screen using wifi_station_ble_provisioning_aws example
- All projects in the package are compatible with GNU ARM V12.2.1 toolchain
- Project Configurator is not supported.
- WPS 2.0 PIN/PUSH, Network Manager Enhancements
- MDNS, HTTP Server, Azure MQTT Client, Websockets
- Matter integration with Embedded TCP/IP stack
- Enhanced buffer management, Throughput optimization
- TLS over LWIP, Network layer applications (MQTT, HTTP, etc.) over LWIP.
- Debugging utilities
- Secure communication over host interfaces (UART. SPI, SDIO)
- UART 2 Debug prints are supported only on ULP_GPIO_9.
- Spatial Re-Use, BSS Max Idle
- Provisioning using Wi-Fi AP
- Support for 8 Peripheral + 2 Central connections
- Support for BLE Mesh(4 nodes only) for limited Mesh use case
- None
- Baremetal mode is not supported.
- WiSeConnect3_SDK_3.1.3 and later versions are not compatible with firmware versions prior to 1711.2.10.1.2.0.4, due to enhancements in max transmit power configuration during Wi-Fi join/connection, need to be cautious while doing OTA firmware upgrade.
- TLS 1.3 Server is not supported
- 40 MHz bandwidth for 2.4 GHz band is not supported.
- A maximum of 3 SSL connections are supported in Wi-Fi alone mode.
- In SSL ECC Curve ID supported is 23. SSL handshake with 3rd party clients depends on the SSL ECC Curve ID.
- The number of Non-Transmitting BSSIDs processed is limited by the beacon length that can be processed by the stack (which is 1024 bytes). Beacons greater than 1024 Bytes in length will not be processed.
- UL MUMIMO is not supported.
- WPA3 AP supports only H2E algorithm.
- PMKSA caching is not supported in WPA3 AP mode.
- The maximum embedded MQTT Publish payload is 1 kbyte.
- Timeout value for socket select and socket receive calls of less than 1 second is not currently supported.
- SA query procedure not supported in 11W AP mode.
- WPA3 AP transition mode is not supported.
- For BLE, if the connection is established with a small connection interval (less than 15 ms), simultaneous roles (i.e., Central + Scanning and Peripheral + Advertising) are not supported.
- BLE maximum two concurrent connections are supported, which can be either a connection to two peripheral devices, to one central and one peripheral device or two central devices.
- BLE Slave latency value is valid up to 32 only.
- BLE TX/RX throughput is less when tested with EFM as compared to EFR.
- Maximum supported AE data length is 200 bytes.
- Supports only two ADV_EXT sets.
- Supports only two BLE connections (1 Central and 1 Peripheral) with AE.
- Advertising Extension feature is not supported in Coexistence.
- Isochronous channels feature is not supported.
- Connection subrating feature is not supported.
- LE power controller feature is not supported.
- EATT feature is not supported.
- Periodic Advertising with response(PAwR) feature is not supported.
- BLE Audio is not supported.
- The feature of dynamically changing the TX power when extended advertising is active is not supported.
- Wi-Fi AP + BLE currently not supported
| Item | Details |
|---|---|
| Release date | Jan 17th, 2024 |
| SDK Version | 3.1.2 |
| Firmware Version | 1711.2.10.1.1.0.2 |
| Package Name | WiSeConnect3_SDK_3.1.2 |
| Supported RTOS | FreeRTOS |
| Operating Modes Supported | Wi-Fi STA, Wi-Fi AP, Wi-Fi STA+BLE, Wi-Fi STA+AP |
- SiWx917 release consists of two components
- Wireless Firmware - SiWx917 Firmware Binary available as SiWG917-B.2.10.1.1.0.2.rps
- Wiseconnect3 Library - Wiseconnect3 SDK library runs on the external host in NCP mode.
- Expansion kits: SiWx917-EB4346A (based on Radio board SiWx917-4346A + 8045A Co-Processor Adapter board)
- Expansion Kits: Si917-8036B (Beta version)
- IC OPNs: SiWN917M100LGTBA (Wi-Fi 6 NCP IC, QFN 7x7, 2.4 GHz, 4MB stacked flash, -40 to +85C)
- Operating Modes
- Wi-Fi STA (802.11ax, 802.11n), Wi-Fi 802.11n AP, Wi-Fi STA (802.11ax, 802.11n) + 802.11n AP, Wi-Fi STA (802.11ax, 802.11n) + BLE
- Security
- Secure Boot, Secure Key storage and HW device identity with PUF, Secure Zone, Secure XIP (Execution in place) from flash, Secure Attestation, Anti Rollback, Secure Debug. Flash Protection
- Secure firmware upgrade options:
- Firmware loading through UART, SPI Interface
- Secure Over the Air (OTA) Upgrade
- Crypto Support
- Advanced Encryption Standard (AES) 128/256/192, Secure Hash Algorithm (SHA) 256/384/512, Hash Message Authentication Code (HMAC), Random Number Generator (RNG), SHA3, AES-Galois Counter Mode (GCM)/ Cipher based Message Authentication Code (CMAC), ChaCha-poly, True Random Number Generator (TRNG)
- Software Accelerators: RSA, ECC
- Integrated with mbed TLS
- System Power Save
- Deep Sleep with RAM retention and without RAM retention
- Wireless Power Save: Connected Sleep (Wi-Fi Standby Associated), BLE Advertising with powersave, BLE Scan with powersave , BLE connection with powersave. Only Max PSP power save mode is supported in BLE
- Wi-Fi Protocols
- IEEE 802.11 b/g/n/ax (2.4GHz)
- Access Point (AP) Mode
- 4 Client Support, Hidden SSID Mode, Auto Channel Selection, Scan in AP mode
- Wi-Fi Security
- WPA2 Personal, WPA3 Personal (H2E method only), WPA Mixed mode (WPA/WPA2)
- Wi-Fi Scan
- Selective Scan, Active/Passive Scan
- Wi-Fi STA (Security Modes)
- Open Mode, WPA2 Personal, WPA2 Enhancements, WPA3 Personal, Mixed Mode (WPA/WPA2), WPA3 Personal Transition Mode (WPA2/WPA3)
- WPA2 Enterprise security (STA)
- Method
- PEAP/TTLS/TLS 1.0/TLS 1.2/FAST
- Method
- Wi-Fi STA Rejoin
- Wi-Fi STA Roaming
- BG Scan, OKC (Opportunistic Key caching), PMK (Pairwise Master Key) caching, Pre-Authentication
- Wi-Fi Protocol Power Save
- Deep sleep (unconnected state), Max PSP, Enhanced Max PSP, Fast PSP,** TWT
- QoS
- WMM-QoS
- Wi-Fi 6 Feature
- MUMIMO (DL), OFDMA (UL/DL), iTWT, TWT I-Frame & TWT Enhancements, BSS coloring, MBSSID
- Wi-Fi Concurrency
- AP+STA (Same channel)
- Wi-Fi Band/Channels
- 2.4GHz CH1-11, 2.4GHz CH1-13, 2.4GHz CH1-14 (Japan)
- Known Security Vulnerabilities Handled
- WPA2 KRACK Attacks, Fragment and Forge Vulnerability
- Core Networking Features
- TCP/IP Bypass (LWIP as Hosted stack for reference), IPv4/IPv6/UDP/TCP/ARP/ICMP/ICMPv6
- SSL client versions TLSV1.0, TLSV1.2, TLSV1.3
- SSL server versions TLSV1.0 and TLSV1.2
- DHCP (Client/Server)/ DHCPv6 Client
- Advanced Network Features
- HTTP Client/HTTPS Client//DNS Client/SNTP Client, Embedded MQTT/MQTT on host
- Wi-Fi IoT Cloud Integration
- AWS IOT Core
- BSD and IoT sockets application programming interface(API)
- GAP(Advertising, Scanning, initiation, Connection and Bonding)
- Generic Attribute Protocol(GATT)
- Attribute protocol(ATT)
- Security
- LL Privacy 1.2
- Accept list
- Directed Advertising
- Extended Advertising
- Periodic Advertising
- Periodic Advertising scanning
- Extended Advertising scanning
- Periodic Advertising list
- LE periodic advertising synchronization
- LE PHY(1Mbps, 2Mbps) & Coded PHY(125Kbps, 500kbps)
- Simultaneous scanning on 1Mbps and Coded PHY
- LE dual role topology
- LE data packet length extensions(DLE)
- Asymmetric PHYs
- LE channel selection algorithm 2 (CSA#2)
- LE Secure connections
- Bluetooth 5.4 Qualified
- Simplified and Unified DX for Wi-Fi API
- Simplifies application development and presents clean and standardized APIs
- BSD and ARM IoT-compliant socket API
- Available through Simplicity Studio and GitHub
- Wi-Fi STA + BLE
- 3 wire coex acting as Wi-Fi with external Bluetooth
- 3 wire coex acting as Wi-Fi with external Zigbee/OT
- WOW LAN is not supported.
- Enhancements
- Resolved warnings in the featured and snippet demos.
- sl_wifi_get_sta_tsf() API added to get the station TSF time which is synchronized with connected AP beacon TSF.
- Added "update gain” demo for BLE.
- Added an option to test user gain table feature in "ble_per" demo by enabling the “GAIN_TABLE_AND_MAX_POWER_UPDATE_ENABLE” macro.
- Removed unused input parameters in rsi_ble_set_ble_tx_power() API.
- Fixed Issues
- Fixed issue with BSSID based connection.
- Fixed issue with the file descriptors set handling for socket select.
- Fixed issue with authentication and association timeout is not reflecting as per timeout configuration using sl_si91x_configure_timeout() API
- Fixed profile id corruption issue for IPV6 demos.
- Fixed application hang issue at the AE Clear Periodic Adv list API when used "ble_ae_central" example.
- Fixed issue where BLE connect API is failing because of 0xFFFFFFE2(RSI_ERROR_RESPONSE_TIMEOUT) error with ble_central application.
- Enhancements
- Added support for TSF time which is synchronized with connected AP beacon TSF.
- Improve PER performance at max input power levels for 11b.
- Improved ppm error across channels at room temperature.
- Updated regulatory tables of WLAN
- Fixed Issues
- Increased supported length for Embedded MQTT username up to 120 bytes and topic length up to 200 bytes.
- Added support to process long ICMP ping response up to packet size of 1472 Bytes for IPv4 and 1452 Bytes for IPv6.
- Issue with configuration of TCP MSS through setsockopt() has been fixed.
- Fixed Listen interval based power save issue when IPV6 mode is enabled
- Added fix for missing RSN IE in first few AP beacons
- Enhancements
- Added Region based maximum power index support for both 0dBm & 10dDm LP chains.
- Fixed Issues
- Fixed regulatory output power violations with default region based settings in HP chain.
- Fixed an issue that caused the Set local name API to fail with the error code 0x4e66[Invalid Name length] when a local name given with 16 bytes of length.
- Enhancements
- None
- Fixed Issues
- None
- Set the recommended Power Save Profile (PSP) type to Enhanced Max PSP.
- Memory configuration for NCP mode is 672K_M4SS_0K.
- Simplicity Studio. This release is tested with SV5.8.0 version.
- Refer to the latest version of the NCP "Getting-Started-with-SiWx917" guide for more details
- It is recommended to enable bit 16 of the 'Extended TCP IP Feature' bit map in the opermode command for all Wi-Fi Socket operations from the host to ensure graceful handling during asynchronous closures from the peer.
- For high throughput applications, aggregation (bit 2 of feature_bit_map) is recommended to be enabled in opermode.
- To reset TA (NWP), the application needs to call sl_wifi_deinit() followed by sl_wifi_init().
- Users can enable SL_SI91X_EXT_TCP_IP_SSL_16K_RECORD in 'Extended TCP IP Feature' bit map in opermode for (HTTPS server) supporting 16k record.
- TWT
- Recommendation is to use sl_wifi_target_wake_time_auto_selection() API for all TWT applications.
- It is recommended to issue iTWT setup command once IP assignment, TCP connection, application specific socket connections are done.
- When using sl_wifi_enable_target_wake_time API, increase TCP / ARP Timeouts at the remote side depending upon the configured TWT interval configured. It's highly recommended to use sl_wifi_target_wake_time_auto_selection() as an alternative.
- In case of TWT in coex mode, when using sl_wifi_enable_target_wake_time API, use TWT wake duration <= 16 ms and TWT wake interval >= 1 sec. If wake duration > 16 ms or TWT wake interval < 1sec, there might be performance issues.
- For iTWT GTK interval in AP should be configured to max possible value or zero. If GTK interval is not configurable on AP side, recommended TWT interval (in case of sl_wifi_enable_target_wake_time API) or RX Latency (in case of sl_wifi_target_wake_time_auto_selection API) is less than 4sec.
- When sl_wifi_enable_target_wake_time API is used, configuring TWT Wake interval beyond 1 min might lead to disconnections from the AP. Recommended to use TWT wake interval of less than or equal to 1 min.
- When using sl_wifi_enable_target_wake_time API, it is recommended to set missed_beacon_count of sl_wifi_set_advanced_client_configuration API greater than 2 times of the configured TWT Interval.
- Disable power save for high throughput applications or use FAST PSP power save mode as per application requirement.
- The application needs to ensure that it sets RTC with the correct timestamp before establishing the SSL/EAP connection.
- The minimum timeout value should not be less than 1 second for socket select and socket receive calls.
- Embedded MQTT keep alive interval should be either 0 or a value greater than 35 seconds.
- Disable power save and suspend any active TWT sessions before triggering HTTP OTAF.
- Randomize the client port if using rapid connect/disconnect of the MQTT session on the same client port with the power save.
- In BLE, the recommended range of Connection Interval in
- Power Save (BLE Only) - 100 ms to 1.28 s.
- In BLE, during Connection, the configuration of Scan Interval and Scan Window with the same value is not recommended. The suggested ratio of Scan Window to Scan Interval is 3:4.
- In BLE, if a device is acting as Central, the scan window (in set_scan_params and create_connection commands) must be less than the existing Connection Interval. The suggested ratio of Scan Window to Connection Interval is 2:3.
- In BLE mode, if scanning and advertising are in progress on the SiWx91x module and it subsequently gets connected and moves to the central role, scanning stops else if it moves to the peripheral role, advertising stops. To further establish a connection to another peripheral device or to a central device, the application should give a command for starting advertising and scanning again.
- For concurrent Wi-Fi + BLE, and while a Wi-Fi connection is active, we recommend setting the ratio of the BLE scan window to BLE scan interval to 1:3 or 1:4.
- Wi-Fi + BLE Advertising
- All standard advertising intervals are supported. As Wi-Fi throughput is increased, a slight difference in on-air advertisements compared to configured intervals may be observed.
- BLE advertising is skipped if the advertising interval collides with Wi-Fi activity.
- Wi-Fi + BLE scanning
- All standard scan intervals are supported. For better scan results, we recommend setting the ratio of the BLE scan window to BLE scan interval to 1:3 or 1:4.
- BLE scanning will be stopped for intervals that collide with Wi-Fi activity.
- Wi-Fi + BLE Central/Peripheral Connections
- All standard connection intervals are supported.
- 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 achieve higher throughput for both Wi-Fi and BLE, use medium connection intervals, such as 45 to 80 ms with maximum supervision timeout.
- Ensure Wi-Fi activity consumes lower intervals.
- None
- Enhanced sl_wifi_get_firmware_version() API to provide more details (ROM ID, chip ID, security version, etc) which is not backward compatible with firmwares older than 1711.2.10.1.0.0.4. Firmware binary notation does not include security version number.
- Observed not being able to receive UDP Rx TPUT print at Teraterm with IPV6 Throughput example
- Matter applications are experiencing compatibility issues with WiseConnect SDK 3.1.2. It is recommended to use WiseConnect SDK 3.1.1 for matter-related applications. This will be addressed in up coming release(s).
Wi-Fi STA
- STA Connection with the WPA3 Hunting and Pecking algorithm takes about 3-4 seconds.
- Observed connection failures with some APs in more channel congestion ~50-60% occupancy open lab environment.
- Region selection based on country IE in the beacon is not supported
- Observed intermittent beacon reception from Access Point ( beacon misses) in an extremely congested environment
- Note section in API documentation for sl_wifi_get_sta_tsf needs to be corrected to "Returns error if station is not connected or at least one beacon is not received."
Access Point (AP) Mode
- Scan feature in AP mode not fully functional.
- Fixed rate configuration in AP mode using sl_wifi_set_transmit_rate API is not being set as expected.
WPA2 Enterprise security (STA)
- Observed issue with configuring certificate key and programming 4096 bit key and SHA384/SHA512 certificates.
- Observing DUT is throwing 0x1001c when configuring .data.certificate_key as "123456789"
- Configuration issue to program PAC file for EAP FAST Manual mode
- Issue observed with WPA2 Enterprise Connectivity using Microsoft RADIUS Server.
Wi-Fi Concurrency ( AP + STA in same channel)
- Observed 3rd party STA association fail with 917 AP while 917 STA mode is connecting/reconnecting to configured 3rd party AP. Reconnect 3rd party STA to 917 AP in such scenarios.
OFDMA (UL/DL)
- Less throughput observed in DL-OFDMA with some APs that enabled LDPC.
MUMIMO (DL)
- For Coex Scenario Wi-Fi + BLE, BLE Data transfer, MU retries (~50-60%) observed while running DL MU-MIMO test.
- Observed Performance, Interop issues with MU MIMO with certain APs.
- Less throughput was observed in MU-MIMO with some APs that enabled LDPC.
TWT
- Variability with MQTT keep alive interval based on TWT wake up interval.
- When sl_wifi_enable_target_wake_time() API is used, occasional MQTT disconnections may be observed if TWT is configured with longer TWT intervals (>30secs) with embedded MQTT + TWT. As an alternative, it's highly recommended to use sl_wifi_target_wake_time_auto_selection() API, where these dependencies are internally handled.
Wi-Fi STA Rejoin
- observed Scanning (probe request) in all channels instead of the channels configured in selective channel(channel_bitmap_2g4) during rejoin process
IPv4/IPv6
- Observed issue with assigning static IP to DUT
- IP change notification is not indicated to the application
BSD Socket API
- Configuration issue to program TCP retry count (default 10) through setsockopt
- Every server socket created consumes a socket (maximum of 10 sockets supported) and every subsequent connection to server socket consumes an additional socket (from the same pool of 10 sockets), which limits the number of server connections supported.
SSL Client/Server
- Sometimes during SSL Handshake, ECC curve parameters generated are wrong, resulting in connection failure with BBD2 error. However, this recovers in the next attempt.
- Secure SSL renegotiation not supported in Embedded Networking Stack
- observed connection failures with ECDSA ciphers
HTTP Client/ HTTPS Client
- Observed occasional HTTPS continuous download failures when power save is enabled. Recommended to disable it before performing HTTPS continuous downloads
- Observed HTTPS post data is failing with error code: BBE2 (HTTP Failed).
SNTP
- Unable to get SNTP async events when coex mode and power save are enabled
Throughputs & Performance
- Observed 20% less Wi-Fi throughput with SDK 3.x compare to target throughput (depends on host and host interface), SDK refinements are in progress
Secure Over the Air (OTA) Upgrade
- Observed firmware upgrade failures after multiple iterations
- Observed OTA failures with power save enabled, So recommended to disable power save during OTA
- Observed "0xffffffff" error at the remote end while doing firmware upgrade via TCP server using (featured) example with ubuntu 21.0x.
Wi-Fi IOT Cloud integration (AWS IOT Core)
- Observed AWS MQTT keepalive transmission is not happening at expected intervals with power save enabled.
Wi-Fi Interoperability (IOP)
- Observed disconnections with Amplifi (AFI-INS-R) AP with Powersave enable
- TWT session is failing due to disconnections observed in DUT if rx_latency is set to 55 seconds and receive data is also set to 55 seconds on MI Xiaomi RA72 and Tplink AX53 AP's
- Observed less throughput(~1Mb) while running TCP RX with Max_PSP powersave with DLink 810 AP
- Observed interop issue (random disconnections) with few APs (EERO 6+, EERO PRO 6E, Cisco Catalyst 9120AXID)
- Disconnections observed with Netgear RAX120 AP in WPA3 security
IOP
- BLE connection failure has been observed on a few mobile devices (Samsung S23& Oneplus 9pro) when Si917 device is configured as central.
- For Coex Scenario Wi-Fi + BLE, BLE Data transfer, MU retries (~50-60%) observed while running DL MU-MIMO test.
- Observed Wi-Fi + BLE intermittent connection failures, disconnections, and data transfer stalls in the long run when power save is enabled.
- While executing Wi-Fi Commissioning using the wifi_station_ble_provisioning example, BLE is disconnecting is observed with few boards.
- Observed "DUT is not disconnecting to the AP when initiating disconnection from EFR connect app screen using wifi_station_ble_provisioning_aws example
- All projects in the package are compatible with GNU ARM V12.2.1 toolchain
- Project Configurator is not supported.
- WPS 2.0 PIN/PUSH, Network Manager Enhancements
- MDNS, HTTP Server, Azure MQTT Client, Websockets
- Matter integration with Embedded TCP/IP stack
- Enhanced buffer management, Throughput optimization
- TLS over LWIP, Network layer applications (MQTT, HTTP, etc.) over LWIP.
- Debugging utilities
- Secure communication over host interfaces (UART, SPI, SDIO)
- UART 2 Debug prints are supported only on ULP_GPIO_9.
- Spatial Re-Use, BSS Max Idle
- Provisioning using Wi-Fi AP
- Support for 8 Peripheral + 2 Central connections
- Support for BLE Mesh(4 nodes only) for limited Mesh use case
- None
- Baremetal mode is not supported.
- TLS 1.3 Server is not supported
- 40 MHz bandwidth for 2.4 GHz band is not supported.
- A maximum of 3 SSL connections are supported in Wi-Fi alone mode.
- In SSL ECC Curve ID supported is 23. SSL handshake with 3rd party clients depends on the SSL ECC Curve ID.
- The number of Non-Transmitting BSSIDs processed is limited by the beacon length that can be processed by the stack (which is 1024 bytes). Beacons greater than 1024 Bytes in length will not be processed.
- UL MUMIMO is not supported.
- WPA3 AP supports only H2E algorithm.
- PMKSA caching is not supported in WPA3 AP mode.
- The maximum embedded MQTT Publish payload is 1 kbyte.
- Timeout value for socket select and socket receive calls of less than 1 second is not currently supported.
- For BLE, if the connection is established with a small connection interval (less than 15 ms), simultaneous roles (i.e., Central + Scanning and Peripheral + Advertising) are not supported.
- BLE maximum two concurrent connections are supported, which can be either a connection to two peripheral devices, to one central and one peripheral device or two central devices.
- BLE Slave latency value is valid up to 32 only.
- BLE TX/RX throughput is less when tested with EFM as compared to EFR.
- Maximum supported AE data length is 200 bytes.
- Supports only two ADV_EXT sets.
- Supports only two BLE connections (1 Central and 1 Peripheral) with AE.
- Advertising Extension feature is not supported in Coexistence.
- Isochronous channels feature is not supported.
- Connection subrating feature is not supported.
- LE power controller feature is not supported.
- EATT feature is not supported.
- Periodic Advertising with response(PAwR) feature is not supported.
- BLE Audio is not supported.
- The feature of dynamically changing the TX power when extended advertising is active is not supported.
- Wi-Fi AP + BLE currently not supported
| Item | Details |
|---|---|
| Release date | Jan 2nd, 2024 |
| SDK Version | 3.1.1-Hotfix |
| Firmware Version | 1711.2.10.1.0.0.7 |
| Package Name | WiSeConnect3_SDK_3.1.1-Hotfix |
| Supported RTOS | FreeRTOS |
| Operating Modes Supported | Wi-Fi STA, Wi-Fi AP, Wi-Fi STA+BLE, Wi-Fi STA+AP |
- SiWx917 release consists of two components
- Wireless Firmware - SiWx917 Firmware Binary available as SiWG917-B.2.10.1.0.0.x.rps
- Wiseconnect3 Library - Wiseconnect3 SDK library runs on the external host in NCP mode.
- Expansion kits: SiWx917-EB4346A (based on Radio board SiWx917-4346A + 8045A Co-Processor Adapter board)
- Expansion Kits: Si917-8036B (Beta version)
- IC OPNs: SiWN917M100LGTBA (Wi-Fi 6 NCP IC, QFN 7x7, 2.4 GHz, 4MB stacked flash, -40 to +85C)
- Operating Modes
- Wi-Fi STA (802.11ax, 802.11n), Wi-Fi 802.11n AP, Wi-Fi STA (802.11ax, 802.11n) + 802.11n AP, Wi-Fi STA (802.11ax, 802.11n) + BLE
- Security
- Secure Boot, Secure Key storage and HW device identity with PUF, Secure Zone, Secure XIP (Execution in place) from flash, Secure Attestation, Anti Rollback, Secure Debug. Flash Protection
- Secure firmware upgrade options:
- Firmware loading through UART, SPI Interface
- Secure Over the Air (OTA) Upgrade
- Crypto Support
- Crypto API's for Hardware Accelerators:
- Advanced Encryption Standard (AES) 128/256/192, Secure Hash Algorithm (SHA) 256/384/512, Hash Message Authentication Code (HMAC), Random Number Generator (RNG), SHA3, AES-Galois Counter Mode (GCM)/ Cipher based Message Authentication Code (CMAC), ChaCha-poly, True Random Number Generator (TRNG)
- Software Accelerators: RSA, ECC
- Integrated with mbed TLS
- Crypto API's for Hardware Accelerators:
- System Power Save
- Deep Sleep with RAM retention and without RAM retention
- Wireless Power Save: Connected Sleep (Wi-Fi Standby Associated), BLE Advertising with powersave, BLE Scan with powersave , BLE connection with powersave. Only Max PSP power save mode is supported in BLE
- Wi-Fi Protocols
- IEEE 802.11 b/g/n/ax (2.4GHz)
- Access Point (AP) Mode
- 4 Client Support, Hidden SSID Mode, Auto Channel Selection, Scan in AP mode
- Wi-Fi Security
- WPA2 Personal, WPA3 Personal (H2E method only), WPA Mixed mode (WPA/WPA2)
- Wi-Fi Scan
- Selective Scan, Active/Passive Scan
- Wi-Fi STA (Security Modes)
- Open Mode, WPA2 Personal, WPA2 Enhancements, WPA3 Personal, Mixed Mode (WPA/WPA2), WPA3 Personal Transition Mode (WPA2/WPA3)
- WPA2 Enterprise security (STA)
- Method
- PEAP/TTLS/TLS 1.0/TLS 1.2/FAST
- Method
- Wi-Fi STA Rejoin
- Wi-Fi STA Roaming
- BG Scan, OKC (Opportunistic Key caching), PMK (Pairwise Master Key) caching, Pre-Authentication
- Wi-Fi Protocol Power Save
- Deep sleep (unconnected state), Max PSP, Enhanced Max PSP, Fast PSP,** TWT
- QoS
- WMM-QoS
- Wi-Fi 6 Feature
- MUMIMO (DL), OFDMA (UL/DL), iTWT, TWT I-Frame & TWT Enhancements, BSS coloring, MBSSID
- Wi-Fi Concurrency
- AP+STA (Same channel)
- Wi-Fi Band/Channels
- 2.4GHz CH1-11, 2.4GHz CH1-13, 2.4GHz CH1-14 (Japan)
- Known Security Vulnerabilities Handled
- WPA2 KRACK Attacks, Fragment and Forge Vulnerability
- Core Networking Features
- TCP/IP Bypass (LWIP as Hosted stack for reference), IPv4/IPv6/UDP/TCP/ARP/ICMP/ICMPv6
- SSL client versions TLSV1.0, TLSV1.2, TLSV1.3
- SSL server versions TLSV1.0 and TLSV1.2
- DHCP (Client/Server)/ DHCPv6 Client
- Advanced Network Features
- HTTP Client/HTTPS Client//DNS Client/SNTP Client, Embedded MQTT/MQTT on host
- Wi-Fi IoT Cloud Integration
- AWS IOT Core
- BSD and IoT sockets application programming interface(API)
- GAP(Advertising, Scanning, initiation, Connection and Bonding)
- Generic Attribute Protocol(GATT)
- Attribute protocol(ATT)
- Security
- LL Privacy 1.2
- Accept list
- Directed Advertising
- Extended Advertising
- Periodic Advertising
- Periodic Advertising scanning
- Extended Advertising scanning
- Periodic Advertising list
- LE periodic advertising synchronization
- LE PHY(1Mbps, 2Mbps) & Coded PHY(125Kbps, 500kbps)
- Simultaneous scanning on 1Mbps and Coded PHY
- LE dual role topology
- LE data packet length extensions(DLE)
- Asymmetric PHYs
- LE channel selection algorithm 2 (CSA#2)
- LE Secure connections
- Bluetooth 5.4 Qualified
- Simplified and Unified DX for Wi-Fi API
- Simplifies application development and presents clean and standardized APIs
- BSD and ARM IoT-compliant socket API
- Available through Simplicity Studio and GitHub
- Wi-Fi STA + BLE
- 3 wire coex acting as Wi-Fi with external Bluetooth
- 3 wire coex acting as Wi-Fi with external Zigbee/OT
- None
- None
- Fixed Issues
- Updated WLAN regulatory power tables.
- Fixed Issues
- Updated BLE regulatory power tables.
- None
- Set the recommended Power Save Profile (PSP) type to Enhanced Max PSP.
- Memory configuration for NCP mode is 672K_M4SS_0K.
- Simplicity Studio. This release is tested with SV5.8.0 version.
- Refer to the latest version of the NCP "Getting-Started-with-SiWx917" guide for more details
- It is recommended to enable bit 16 of the 'Extended TCP IP Feature' bit map in the opermode command for all Wi-Fi Socket operations from the host to ensure graceful handling during asynchronous closures from the peer.
- For high throughput applications, aggregation (bit 2 of feature_bit_map) is recommended to be enabled in opermode.
- To reset TA (NWP), the application needs to call sl_wifi_deinit() followed by sl_wifi_init().
- Users can enable SL_SI91X_EXT_TCP_IP_SSL_16K_RECORD in 'Extended TCP IP Feature' bit map in opermode for (HTTPS server) supporting 16k record.
- TWT
- Recommendation is to use sl_wifi_target_wake_time_auto_selection() API for all TWT applications.
- It is recommended to issue iTWT setup command once IP assignment, TCP connection, application specific socket connections are done.
- When using sl_wifi_enable_target_wake_time API, increase TCP / ARP Timeouts at the remote side depending upon the configured TWT interval configured. It's highly recommended to use sl_wifi_target_wake_time_auto_selection() as an alternative.
- In case of TWT in coex mode, when using sl_wifi_enable_target_wake_time API, use TWT wake duration <= 16 ms and TWT wake interval >= 1 sec. If wake duration > 16 ms or TWT wake interval < 1sec, there might be performance issues.
- For iTWT GTK interval in AP should be configured to max possible value or zero. If GTK interval is not configurable on AP side, recommended TWT interval (in case of sl_wifi_enable_target_wake_time API) or RX Latency (in case of sl_wifi_target_wake_time_auto_selection API) is less than 4sec.
- When sl_wifi_enable_target_wake_time API is used, configuring TWT Wake interval beyond 1 min might lead to disconnections from the AP. Recommended to use TWT wake interval of less than or equal to 1 min.
- When using sl_wifi_enable_target_wake_time API, it is recommended to set missed_beacon_count of sl_wifi_set_advanced_client_configuration API greater than 2 times of the configured TWT Interval.
- Disable power save for high throughput applications or use FAST PSP power save mode as per application requirement.
- The application needs to ensure that it sets RTC with the correct timestamp before establishing the SSL/EAP connection.
- The minimum timeout value should not be less than 1 second for socket select and socket receive calls.
- Embedded MQTT keep alive interval should be either 0 or a value greater than 35 seconds.
- Disable power save and suspend any active TWT sessions before triggering HTTP OTAF.
- Randomize the client port if using rapid connect/disconnect of the MQTT session on the same client port with the power save.
- In BLE, the recommended range of Connection Interval in
- Power Save (BLE Only) - 100 ms to 1.28 s.
- In BLE, during Connection, the configuration of Scan Interval and Scan Window with the same value is not recommended. The suggested ratio of Scan Window to Scan Interval is 3:4.
- In BLE, if a device is acting as Central, the scan window (in set_scan_params and create_connection commands) must be less than the existing Connection Interval. The suggested ratio of Scan Window to Connection Interval is 2:3.
- In BLE mode, if scanning and advertising are in progress on the SiWx91x module and it subsequently gets connected and moves to the central role, scanning stops else if it moves to the peripheral role, advertising stops. To further establish a connection to another peripheral device or to a central device, the application should give a command for starting advertising and scanning again.
- For concurrent Wi-Fi + BLE, and while a Wi-Fi connection is active, we recommend setting the ratio of the BLE scan window to BLE scan interval to 1:3 or 1:4.
- Wi-Fi + BLE Advertising
- All standard advertising intervals are supported. As Wi-Fi throughput is increased, a slight difference in on-air advertisements compared to configured intervals may be observed.
- BLE advertising is skipped if the advertising interval collides with Wi-Fi activity.
- Wi-Fi + BLE scanning
- All standard scan intervals are supported. For better scan results, we recommend setting the ratio of the BLE scan window to BLE scan interval to 1:3 or 1:4.
- BLE scanning will be stopped for intervals that collide with Wi-Fi activity.
- Wi-Fi + BLE Central/Peripheral Connections
- All standard connection intervals are supported.
- 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 achieve higher throughput for both Wi-Fi and BLE, use medium connection intervals, such as 45 to 80 ms with maximum supervision timeout.
- Ensure Wi-Fi activity consumes lower intervals.
- None
- Observed issue, when NULL is passed for readfds, writefds, excepfds to socket, select.
- Enhanced sl_wifi_get_firmware_version() API to provide more details (ROM ID, chip ID, security version, etc) which is not backward compatible with firmwares older than 1711.2.10.1.0.0.4. Firmware binary notation does not include security version number.
- Observed not being able to receive UDP Rx TPUT print at Teraterm with IPV6 Throughput example
Wi-Fi STA
- STA Connection with the WPA3 Hunting and Pecking algorithm takes about 3-4 seconds.
- Observed BSSID-based connection configuration is not reflecting to make a connection with the specified access point.
- Observed connection failures with some APs in more channel congestion ~50-60% occupancy open lab environment.
- Observed auth/assoc timeout is not reflecting as per timeout configuration using sl_si91x_configure_timeout() API .
- Region selection based on country IE in the beacon is not supported
- Observed intermittent beacon reception from Access Point ( beacon misses) in an extremely congested environment
Access Point (AP) Mode
- Scan feature in AP mode not fully functional.
- Fixed rate configuration in AP mode using sl_wifi_set_transmit_rate API is not being set as expected.
- First few beacons (~ 10) don't include RSN IE
WPA2 Enterprise security (STA)
- Observed issue with configuring certificate key and programming 4096 bit key and SHA384/SHA512 certificates.
- Observing DUT is throwing 0x1001c when configuring .data.certificate_key as "123456789"
- Configuration issue to program PAC file for EAP FAST Manual mode
- Issue observed with WPA2 Enterprise Connectivity using Microsoft RADIUS Server.
Wi-Fi Concurrency ( AP + STA in same channel)
- Observed 3rd party STA association fail with 917 AP while 917 STA mode is connecting/reconnecting to configured 3rd party AP. Reconnect 3rd party STA to 917 AP in such scenarios.
OFDMA (UL/DL)
- Less throughput observed in DL-OFDMA with some APs that enabled LDPC.
MUMIMO (DL)
- For Coex Scenario Wi-Fi + BLE, BLE Data transfer, MU retries (~50-60%) observed while running DL MU-MIMO test.
- Observed Performance, Interop issues with MU MIMO with certain APs.
- Less throughput was observed in MU-MIMO with some APs that enabled LDPC.
TWT
- Variability with MQTT keep alive interval based on TWT wake up interval.
- When sl_wifi_enable_target_wake_time() API is used, occasional MQTT disconnections may be observed if TWT is configured with longer TWT intervals (>30secs) with embedded MQTT + TWT. As an alternative, it's highly recommended to use sl_wifi_target_wake_time_auto_selection() API, where these dependencies are internally handled.
Wi-Fi STA Rejoin
- observed Scanning (probe request) in all channels instead of the channels configured in selective channel(channel_bitmap_2g4) during rejoin process
IPv4/IPv6
- Observed issue with assigning static IP to DUT
- IP change notification is not indicated to the application
- Observed sl_net_up returning 0x27 error code due to an issue in the handling of IPv6 address.
BSD Socket API
- Configuration issue to program MSS (default 1460), TCP retry count (default 10) through setsockopt
- Every server socket created consumes a socket (maximum of 10 sockets supported) and every subsequent connection to server socket consumes an additional socket (from the same pool of 10 sockets), which limits the number of server connections supported.
SSL Client/Server
- Sometimes during SSL Handshake, ECC curve parameters generated are wrong, resulting in connection failure with BBD2 error. However, this recovers in the next attempt.
- Secure SSL renegotiation not supported in Embedded Networking Stack
- observed connection failures with ECDSA ciphers
HTTP Client/ HTTPS Client
- Observed occasional HTTPS continuous download failures when power save is enabled. Recommended to disable it before performing HTTPS continuous downloads
- Observed HTTPS post data is failing with error code: BBE2 (HTTP Failed).
SNTP
- Unable to get SNTP async events when coex mode and power save are enabled
Throughputs & Performance
- Observed 20% less Wi-Fi throughput with SDK 3.x compare to target throughput (depends on host and host interface), SDK refinements are in progress
Secure Over the Air (OTA) Upgrade
- Observed firmware upgrade failures after multiple iterations
- Observed OTA failures with power save enabled, So recommended to disable power save during OTA
- Observed "0xffffffff" error at the remote end while doing firmware upgrade via TCP server using (featured) example with ubuntu 21.0x.
Wi-Fi IOT Cloud integration (AWS IOT Core)
- Observed AWS MQTT keepalive transmission is not happening at expected intervals with power save enabled.
Wi-Fi Interoperability (IOP)
- Observed disconnections with Amplifi (AFI-INS-R) AP with Powersave enable
- TWT session is failing due to disconnections observed in DUT if rx_latency is set to 55 seconds and receive data is also set to 55 seconds on MI Xiaomi RA72 and Tplink AX53 AP's
- Observed less throughput(~1Mb) while running TCP RX with Max_PSP powersave with DLink 810 AP
- Observed interop issue (random disconnections) with few APs (EERO 6+, EERO PRO 6E, Cisco Catalyst 9120AXID)
- Disconnections observed with Netgear RAX120 AP in WPA3 security
GAP
- When running the ble_central application with power save enabled, it was observed that the BLE connect API is failing because of 0xFFFFFFE2(RSI_ERROR_RESPONSE_TIMEOUT) error.
- When BLE local name is provided with a 16-byte length, the Set local name API fails with error code: 0x4e66[Invalid Name length].
Advertising Extension
- When running the ble_ae_central example, observed an application hang issue at the AE Clear Periodic Adv list API.
DTM/PER
- Recommend to limit BLE Tx Maximum power to 16 dBm. Please don't use for 127 power_index for BLE HP release with this release.
IOP
- BLE connection failure has been observed on a few mobile devices (Samsung S23& Oneplus 9pro) when Si917 device is configured as central.
- For Coex Scenario Wi-Fi + BLE, BLE Data transfer, MU retries (~50-60%) observed while running DL MU-MIMO test.
- Observed Wi-Fi + BLE intermittent connection failures, disconnections, and data transfer stalls in the long run when power save is enabled.
- While executing Wi-Fi Commissioning using the wifi_station_ble_provisioning example, BLE is disconnecting is observed with few boards.
- Observed "DUT is not disconnecting to the AP when initiating disconnection from EFR connect app screen using wifi_station_ble_provisioning_aws example
- All projects in the package are compatible with GNU ARM V12.2.1 toolchain
- Project Configurator is not supported.
- WPS 2.0 PIN/PUSH, Network Manager Enhancements
- MDNS, HTTP Server, Azure MQTT Client, Websockets
- Matter integration with Embedded TCP/IP stack
- Enhanced buffer management, Throughput optimization
- TLS over LWIP, Network layer applications (MQTT, HTTP, etc.) over LWIP.
- Debugging utilities
- Secure communication over host interfaces (UART. SPI, SDIO)
- UART 2 Debug prints are supported only on ULP_GPIO_9.
- Spatial Re-Use, BSS Max Idle
- Provisioning using Wi-Fi AP
- Support for 8 Peripheral + 2 Central connections
- Support for BLE Mesh(4 nodes only) for limited Mesh use case
- None
- Baremetal mode is not supported.
- TLS 1.3 Server is not supported
- 40 MHz bandwidth for 2.4 GHz band is not supported.
- A maximum of 3 SSL connections are supported in Wi-Fi alone mode.
- In SSL ECC Curve ID supported is 23. SSL handshake with 3rd party clients depends on the SSL ECC Curve ID.
- The number of Non-Transmitting BSSIDs processed is limited by the beacon length that can be processed by the stack (which is 1024 bytes). Beacons greater than 1024 Bytes in length will not be processed.
- UL MUMIMO is not supported.
- WPA3 AP supports only H2E algorithm.
- PMKSA caching is not supported in WPA3 AP mode.
- The maximum embedded MQTT Publish payload is 1 kbyte.
- Timeout value for socket select and socket receive calls of less than 1 second is not currently supported.
- For BLE, if the connection is established with a small connection interval (less than 15 ms), simultaneous roles (i.e., Central + Scanning and Peripheral + Advertising) are not supported.
- BLE maximum two concurrent connections are supported, which can be either a connection to two peripheral devices, to one central and one peripheral device or two central devices.
- BLE Slave latency value is valid up to 32 only.
- BLE TX/RX throughput is less when tested with EFM as compared to EFR.
- Maximum supported AE data length is 200 bytes.
- Supports only two ADV_EXT sets.
- Supports only two BLE connections (1 Central and 1 Peripheral) with AE.
- Advertising Extension feature is not supported in Coexistence.
- Isochronous channels feature is not supported.
- Connection subrating feature is not supported.
- LE power controller feature is not supported.
- EATT feature is not supported.
- Periodic Advertising with response(PAwR) feature is not supported.
- BLE Audio is not supported.
- The feature of dynamically changing the TX power when extended advertising is active is not supported.
- Wi-Fi AP + BLE currently not supported
| Item | Details |
|---|---|
| Release date | Dec 20th, 2023 |
| SDK Version | 3.1.1-Doc |
| Firmware Version | 1711.2.10.1.0.0.4 |
| Package Name | WiSeConnect3_SDK_3.1.1-Doc |
| Supported RTOS | FreeRTOS |
| Operating Modes Supported | Wi-Fi STA, Wi-Fi AP, Wi-Fi STA+BLE, Wi-Fi STA+AP |
- SiWx917 release consists of two components
- Wireless Firmware - SiWx917 Firmware Binary available as SiWG917-B.2.10.0.0.4.x.rps
- Wiseconnect3 Library - Wiseconnect3 SDK library runs on the external host in NCP mode.
- Expansion kits: SiWx917-EB4346A (based on Radio board SiWx917-4346A + 8045A Co-Processor Adapter board)
- Expansion Kits: Si917-8036B (Beta version)
- IC OPNs: SiWN917M100LGTBA (Wi-Fi 6 NCP IC, QFN 7x7, 2.4 GHz, 4MB stacked flash, -40 to +85C)
- Operating Modes
- Wi-Fi STA (802.11ax, 802.11n), Wi-Fi 802.11n AP, Wi-Fi STA (802.11ax, 802.11n) + 802.11n AP, Wi-Fi STA (802.11ax, 802.11n) + BLE
- Security
- Secure Boot, Secure Key storage and HW device identity with PUF, Secure Zone, Secure XIP (Execution in place) from flash, Secure Attestation, Anti Rollback, Secure Debug. Flash Protection
- Secure firmware upgrade options:
- Firmware loading through UART, SPI Interface
- Secure Over the Air (OTA) Upgrade
- Crypto Support
- Crypto API's for Hardware Accelerators:
- Advanced Encryption Standard (AES) 128/256/192, Secure Hash Algorithm (SHA) 256/384/512, Hash Message Authentication Code (HMAC), Random Number Generator (RNG), SHA3, AES-Galois Counter Mode (GCM)/ Cipher based Message Authentication Code (CMAC), ChaCha-poly, True Random Number Generator (TRNG)
- Software Accelerators: RSA, ECC
- Integrated with mbed TLS
- Crypto API's for Hardware Accelerators:
- System Power Save
- Deep Sleep with RAM retention and without RAM retention
- Wireless Power Save: Connected Sleep (Wi-Fi Standby Associated), BLE Advertising with powersave, BLE Scan with powersave , BLE connection with powersave. Only Max PSP power save mode is supported in BLE
- Wi-Fi Protocols
- IEEE 802.11 b/g/n/ax (2.4GHz)
- Access Point (AP) Mode
- 4 Client Support, Hidden SSID Mode, Auto Channel Selection, Scan in AP mode
- Wi-Fi Security
- WPA2 Personal, WPA3 Personal (H2E method only), WPA Mixed mode (WPA/WPA2)
- Wi-Fi Scan
- Selective Scan, Active/Passive Scan
- Wi-Fi STA (Security Modes)
- Open Mode, WPA2 Personal, WPA2 Enhancements, WPA3 Personal, Mixed Mode (WPA/WPA2), WPA3 Personal Transition Mode (WPA2/WPA3)
- WPA2 Enterprise security (STA)
- Method
- PEAP/TTLS/TLS 1.0/TLS 1.2/FAST
- Method
- Wi-Fi STA Rejoin
- Wi-Fi STA Roaming
- BG Scan, OKC (Opportunistic Key caching), PMK (Pairwise Master Key) caching, Pre-Authentication
- Wi-Fi Protocol Power Save
- Deep sleep (unconnected state), Max PSP, Enhanced Max PSP, Fast PSP,** TWT
- QoS
- WMM-QoS
- Wi-Fi 6 Feature
- MUMIMO (DL), OFDMA (UL/DL), iTWT, TWT I-Frame & TWT Enhancements, BSS coloring, MBSSID
- Wi-Fi Concurrency
- AP+STA (Same channel)
- Wi-Fi Band/Channels
- 2.4GHz CH1-11, 2.4GHz CH1-13, 2.4GHz CH1-14 (Japan)
- Known Security Vulnerabilities Handled
- WPA2 KRACK Attacks, Fragment and Forge Vulnerability
- Core Networking Features
- TCP/IP Bypass (LWIP as Hosted stack for reference), IPv4/IPv6/UDP/TCP/ARP/ICMP/ICMPv6
- SSL client versions TLSV1.0, TLSV1.2, TLSV1.3
- SSL server versions TLSV1.0 and TLSV1.2
- DHCP (Client/Server)/ DHCPv6 Client
- Advanced Network Features
- HTTP Client/HTTPS Client//DNS Client/SNTP Client, Embedded MQTT/MQTT on host
- Wi-Fi IoT Cloud Integration
- AWS IOT Core
- BSD and IoT sockets application programming interface(API)
- GAP(Advertising, Scanning, initiation, Connection and Bonding)
- Generic Attribute Protocol(GATT)
- Attribute protocol(ATT)
- Security
- LL Privacy 1.2
- Accept list
- Directed Advertising
- Extended Advertising
- Periodic Advertising
- Periodic Advertising scanning
- Extended Advertising scanning
- Periodic Advertising list
- LE periodic advertising synchronization
- LE PHY(1Mbps, 2Mbps) & Coded PHY(125Kbps, 500kbps)
- Simultaneous scanning on 1Mbps and Coded PHY
- LE dual role topology
- LE data packet length extensions(DLE)
- Asymmetric PHYs
- LE channel selection algorithm 2 (CSA#2)
- LE Secure connections
- Bluetooth 5.4 Qualified
- Simplified and Unified DX for Wi-Fi API
- Simplifies application development and presents clean and standardized APIs
- BSD and ARM IoT-compliant socket API
- Available through Simplicity Studio and GitHub
- Wi-Fi STA + BLE
- 3 wire coex acting as Wi-Fi with external Bluetooth
- 3 wire coex acting as Wi-Fi with external Zigbee/OT
- None
- Enhancements
- Folder restructuring, renamed SLC features and components as part of componentization. (Refer Migration Guide)
- Standardized build parameters, enum, structures, typedef, and API signatures. (Refer Migration Guide)
- Added support for TA(NWP) buffer configuration in sl_wifi_init.
- Added support for sl_wifi_device_context_t in sl_wifi_init.
- Replaced sl_tls with sl_net credential API.
- Updated certificate handling APIs.
- Updated and standardized README files for featured examples, MQTT, TWT, and more.
- Generic API reference documentation updation.
- Added support for customization support of ncp_host and spi_driver implementations using efx_ncp_custom_host_mcu and siwx917_ncp_custom_spi_driver respectively.
- Updated readme files for AES, calibration app, HTTP client, WLAN throughput v6, and embedded MQTT client.
- Updated documentation for the CLI demo in NCP mode.
- added readme files for ble_per and ble_accept_list.
- Updated BLE API reference documentation with descriptions and navigation links.
- Replaced printf statements with LOG_PRINT in all Coex example applications.
- Enhancements
- Added support for WPA3 personal security (with H2E method only) in AP mode
- Added support for timeout configuration API
- Added support for Server Name Indication (SNI).
- Added support for Extensible Authentication Protocol (EAP) encrypted certificates.
- Added support for CLI demo, HTTP client, WLAN throughput v6, and embedded MQTT client example applications for NCP mode
- Fixed Issues
- Resolved issues with CW modes in RF test example.
- Fixed the issue where application hangs during SHA operation on larger data exceeding 1400 bytes in TA(NWP).
- Fixed the issue where the IOT socket connect/bind failed with -3 error in the CLI demo app.
- Fixed the issue where DUT BLE stopped advertising after a few seconds while running wifi_ble_power_save_ncp application.
- Fixed the issue where sl_net_init returned 0xff82 as an error code in the case of WLAN throughput NCP.
- Added NCP Support For
- ble_power_save, gatt_long_read, ble_hid_on_gatt, ble_unified_ae_coex_app, ble_datalength, ble_accept_list, ble_central, ble_longrange_2mpbps, ble_heart_rate_profile, ble_ibeacon, ble_privacy, ble_secureconnection, ble_throughput_app, ble_ae_central and ble_ae_peripheral applications.
- Enhancements
- Added support for standby sleep with RAM retention in WLAN+BLE coex mode.
- Removed support for unused rsi_ble_set_prop_protocol_ble_bandedge_tx_power(), rsi_bt_ber_enable_or_disable(), and rsi_bt_per_cw_mode() APIs.
- Added support for rsi_ble_prepare_write_async, rsi_ble_execute_write_async and rsi_ble_get_inc_services SAPI's in gatt_test application.
- Fixed Issues
- DUT transmitting 240 bytes MTU request packet regardless of programmed MTU length.
- DUT is unable to transmit complete periodic advertising data.
- Hang issue when transmitting BLE notification with coded PHY rates of 125kbps and 500kbps.
- DUT not transmitting BLE scan requests after 20sec when power save is enabled.
- DUT not transmitting packets continuously over the air in BLE test modes.
- BLE Set BD address API failing with error code 0xfffffffd (Command given in the wrong state).
- rsi_ble_set_local_att_value() API fails with error code 0xFFFFFFE2 (RSI_ERROR_RESPONSE_TIMEOUT) during BLE notification.
- "Failed to keep module in active mode: FFFFFFFF" issue when disabling power save after enabling enhanced max psp power save.
- BLE per stats cmd API fails with error code 0xFFFFFFE2 (RSI_ERROR_RESPONSE_TIMEOUT).
- BLE scanning stops within ~4-5 minutes when powersave is enabled.
- Enhancements
- Added support for wifi_station_ble_provisioning with AWS cloud.
- Increased priority of Wi-Fi handling of data transmission in coex mode.
- Fixed Issues
- Abrupt termination of HTTP download in the application when Powersave is enabled.
- Firmware update fails with 0x7 error code when power save is enabled in wifi_throughput_ble_dual_role application.
- Handling of PLL value in coex mode.
- BLE disconnection issue after ~25-30 min while running WLAN HTTP/HTTPs download along with BLE data transfer with Power save enabled.
- Set the recommended Power Save Profile (PSP) type to Enhanced Max PSP.
- Memory configuration for NCP mode is 672K_M4SS_0K.
- Simplicity Studio. This release is tested with SV5.8.0 version.
- Refer to the latest version of the NCP "Getting-Started-with-SiWx917" guide for more details
- It is recommended to enable bit 16 of the 'Extended TCP IP Feature' bit map in the opermode command for all Wi-Fi Socket operations from the host to ensure graceful handling during asynchronous closures from the peer.
- For high throughput applications, aggregation (bit 2 of feature_bit_map) is recommended to be enabled in opermode.
- To reset TA (NWP), the application needs to call sl_wifi_deinit() followed by sl_wifi_init().
- Users can enable SL_SI91X_EXT_TCP_IP_SSL_16K_RECORD in 'Extended TCP IP Feature' bit map in opermode for (HTTPS server) supporting 16k record.
- TWT
- Recommendation is to use sl_wifi_target_wake_time_auto_selection() API for all TWT applications.
- It is recommended to issue iTWT setup command once IP assignment, TCP connection, application specific socket connections are done.
- When using sl_wifi_enable_target_wake_time API, increase TCP / ARP Timeouts at the remote side depending upon the configured TWT interval configured. It's highly recommended to use sl_wifi_target_wake_time_auto_selection() as an alternative.
- In case of TWT in coex mode, when using sl_wifi_enable_target_wake_time API, use TWT wake duration <= 16 ms and TWT wake interval >= 1 sec. If wake duration > 16 ms or TWT wake interval < 1sec, there might be performance issues.
- For iTWT GTK interval in AP should be configured to max possible value or zero. If GTK interval is not configurable on AP side, recommended TWT interval (in case of sl_wifi_enable_target_wake_time API) or RX Latency (in case of sl_wifi_target_wake_time_auto_selection API) is less than 4sec.
- When sl_wifi_enable_target_wake_time API is used, configuring TWT Wake interval beyond 1 min might lead to disconnections from the AP. Recommended to use TWT wake interval of less than or equal to 1 min.
- When using sl_wifi_enable_target_wake_time API, it is recommended to set missed_beacon_count of sl_wifi_set_advanced_client_configuration API greater than 2 times of the configured TWT Interval.
- Disable power save for high throughput applications or use FAST PSP power save mode as per application requirement.
- The application needs to ensure that it sets RTC with the correct timestamp before establishing the SSL/EAP connection.
- The minimum timeout value should not be less than 1 second for socket select and socket receive calls.
- Embedded MQTT keep alive interval should be either 0 or a value greater than 35 seconds.
- Disable power save and suspend any active TWT sessions before triggering HTTP OTAF.
- Randomize the client port if using rapid connect/disconnect of the MQTT session on the same client port with the power save.
- In BLE, the recommended range of Connection Interval in
- Power Save (BLE Only) - 100 ms to 1.28 s.
- In BLE, during Connection, the configuration of Scan Interval and Scan Window with the same value is not recommended. The suggested ratio of Scan Window to Scan Interval is 3:4.
- In BLE, if a device is acting as Central, the scan window (in set_scan_params and create_connection commands) must be less than the existing Connection Interval. The suggested ratio of Scan Window to Connection Interval is 2:3.
- In BLE mode, if scanning and advertising are in progress on the SiWx91x module and it subsequently gets connected and moves to the central role, scanning stops else if it moves to the peripheral role, advertising stops. To further establish a connection to another peripheral device or to a central device, the application should give a command for starting advertising and scanning again.
- For concurrent Wi-Fi + BLE, and while a Wi-Fi connection is active, we recommend setting the ratio of the BLE scan window to BLE scan interval to 1:3 or 1:4.
- Wi-Fi + BLE Advertising
- All standard advertising intervals are supported. As Wi-Fi throughput is increased, a slight difference in on-air advertisements compared to configured intervals may be observed.
- BLE advertising is skipped if the advertising interval collides with Wi-Fi activity.
- Wi-Fi + BLE scanning
- All standard scan intervals are supported. For better scan results, we recommend setting the ratio of the BLE scan window to BLE scan interval to 1:3 or 1:4.
- BLE scanning will be stopped for intervals that collide with Wi-Fi activity.
- Wi-Fi + BLE Central/Peripheral Connections
- All standard connection intervals are supported.
- 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 achieve higher throughput for both Wi-Fi and BLE, use medium connection intervals, such as 45 to 80 ms with maximum supervision timeout.
- Ensure Wi-Fi activity consumes lower intervals.
- None
- Observed issue, when NULL is passed for readfds, writefds, excepfds to socket, select.
- Enhanced sl_wifi_get_firmware_version() API to provide more details (ROM ID, chip ID, security version, etc) which is not backward compatible with firmwares older than 1711.2.10.1.0.0.4. Firmware binary notation does not include security version number.
- Observed not being able to receive UDP Rx TPUT print at Teraterm with IPV6 Throughput example
Wi-Fi STA
- STA Connection with the WPA3 Hunting and Pecking algorithm takes about 3-4 seconds.
- Observed BSSID-based connection configuration is not reflecting to make a connection with the specified access point.
- Observed connection failures with some APs in more channel congestion ~50-60% occupancy open lab environment.
- Observed auth/assoc timeout is not reflecting as per timeout configuration using sl_si91x_configure_timeout() API .
- Region selection based on country IE in the beacon is not supported
- Observed intermittent beacon reception from Access Point ( beacon misses) in an extremely congested environment
Access Point (AP) Mode
- Scan feature in AP mode not fully functional.
- Fixed rate configuration in AP mode using sl_wifi_set_transmit_rate API is not being set as expected.
- First few beacons (~ 10) don't include RSN IE
WPA2 Enterprise security (STA)
- Observed issue with configuring certificate key and programming 4096 bit key and SHA384/SHA512 certificates.
- Observing DUT is throwing 0x1001c when configuring .data.certificate_key as "123456789"
- Configuration issue to program PAC file for EAP FAST Manual mode
- Issue observed with WPA2 Enterprise Connectivity using Microsoft RADIUS Server.
Wi-Fi Concurrency ( AP + STA in same channel)
- Observed 3rd party STA association fail with 917 AP while 917 STA mode is connecting/reconnecting to configured 3rd party AP. Reconnect 3rd party STA to 917 AP in such scenarios.
OFDMA (UL/DL)
- Less throughput observed in DL-OFDMA with some APs that enabled LDPC.
MUMIMO (DL)
- For Coex Scenario Wi-Fi + BLE, BLE Data transfer, MU retries (~50-60%) observed while running DL MU-MIMO test.
- Observed Performance, Interop issues with MU MIMO with certain APs.
- Less throughput was observed in MU-MIMO with some APs that enabled LDPC.
TWT
- Variability with MQTT keep alive interval based on TWT wake up interval.
- When sl_wifi_enable_target_wake_time() API is used, occasional MQTT disconnections may be observed if TWT is configured with longer TWT intervals (>30secs) with embedded MQTT + TWT. As an alternative, it's highly recommended to use sl_wifi_target_wake_time_auto_selection() API, where these dependencies are internally handled.
Wi-Fi STA Rejoin
- observed Scanning (probe request) in all channels instead of the channels configured in selective channel(channel_bitmap_2g4) during rejoin process
IPv4/IPv6
- Observed issue with assigning static IP to DUT
- IP change notification is not indicated to the application
- Observed sl_net_up returning 0x27 error code due to an issue in the handling of IPv6 address.
BSD Socket API
- Configuration issue to program MSS (default 1460), TCP retry count (default 10) through setsockopt
- Every server socket created consumes a socket (maximum of 10 sockets supported) and every subsequent connection to server socket consumes an additional socket (from the same pool of 10 sockets), which limits the number of server connections supported.
SSL Client/Server
- Sometimes during SSL Handshake, ECC curve parameters generated are wrong, resulting in connection failure with BBD2 error. However, this recovers in the next attempt.
- Secure SSL renegotiation not supported in Embedded Networking Stack
- observed connection failures with ECDSA ciphers
HTTP Client/ HTTPS Client
- Observed occasional HTTPS continuous download failures when power save is enabled. Recommended to disable it before performing HTTPS continuous downloads
- Observed HTTPS post data is failing with error code: BBE2 (HTTP Failed).
SNTP
- Unable to get SNTP async events when coex mode and power save are enabled
Throughputs & Performance
- Observed 20% less Wi-Fi throughput with SDK 3.x compare to target throughput (depends on host and host interface), SDK refinements are in progress
Secure Over the Air (OTA) Upgrade
- Observed firmware upgrade failures after multiple iterations
- Observed OTA failures with power save enabled, So recommended to disable power save during OTA
- Observed "0xffffffff" error at the remote end while doing firmware upgrade via TCP server using (featured) example with ubuntu 21.0x.
Wi-Fi IOT Cloud integration (AWS IOT Core)
- Observed AWS MQTT keepalive transmission is not happening at expected intervals with power save enabled.
Wi-Fi Interoperability (IOP)
- Observed disconnections with Amplifi (AFI-INS-R) AP with Powersave enable
- TWT session is failing due to disconnections observed in DUT if rx_latency is set to 55 seconds and receive data is also set to 55 seconds on MI Xiaomi RA72 and Tplink AX53 AP's
- Observed less throughput(~1Mb) while running TCP RX with Max_PSP powersave with DLink 810 AP
- Observed interop issue (random disconnections) with few APs (EERO 6+, EERO PRO 6E, Cisco Catalyst 9120AXID)
- Disconnections observed with Netgear RAX120 AP in WPA3 security
GAP
- When running the ble_central application with power save enabled, it was observed that the BLE connect API is failing because of 0xFFFFFFE2(RSI_ERROR_RESPONSE_TIMEOUT) error.
- When BLE local name is provided with a 16-byte length, the Set local name API fails with error code: 0x4e66[Invalid Name length].
Advertising Extension
- When running the ble_ae_central example, observed an application hang issue at the AE Clear Periodic Adv list API.
DTM/PER
- Recommend to limit BLE Tx Maximum power to 16 dBm. Please don't use for 127 power_index for BLE HP release with this release.
IOP
- BLE connection failure has been observed on a few mobile devices (Samsung S23& Oneplus 9pro) when Si917 device is configured as central.
- For Coex Scenario Wi-Fi + BLE, BLE Data transfer, MU retries (~50-60%) observed while running DL MU-MIMO test.
- Observed Wi-Fi + BLE intermittent connection failures, disconnections, and data transfer stalls in the long run when power save is enabled.
- While executing Wi-Fi Commissioning using the wifi_station_ble_provisioning example, BLE is disconnecting is observed with few boards.
- Observed "DUT is not disconnecting to the AP when initiating disconnection from EFR connect app screen using wifi_station_ble_provisioning_aws example
- All projects in the package are compatible with GNU ARM V12.2.1 toolchain
- Project Configurator is not supported.
- WPS 2.0 PIN/PUSH, Network Manager Enhancements
- MDNS, HTTP Server, Azure MQTT Client, Websockets
- Matter integration with Embedded TCP/IP stack
- Enhanced buffer management, Throughput optimization
- TLS over LWIP, Network layer applications (MQTT, HTTP, etc.) over LWIP.
- Debugging utilities
- Secure communication over host interfaces (UART. SPI, SDIO)
- UART 2 Debug prints are supported only on ULP_GPIO_9.
- Spatial Re-Use, BSS Max Idle
- Provisioning using Wi-Fi AP
- Support for 8 Peripheral + 2 Central connections
- Support for BLE Mesh(4 nodes only) for limited Mesh use case
- None
- Baremetal mode is not supported.
- TLS 1.3 Server is not supported
- 40 MHz bandwidth for 2.4 GHz band is not supported.
- A maximum of 3 SSL connections are supported in Wi-Fi alone mode.
- In SSL ECC Curve ID supported is 23. SSL handshake with 3rd party clients depends on the SSL ECC Curve ID.
- The number of Non-Transmitting BSSIDs processed is limited by the beacon length that can be processed by the stack (which is 1024 bytes). Beacons greater than 1024 Bytes in length will not be processed.
- UL MUMIMO is not supported.
- WPA3 AP supports only H2E algorithm.
- PMKSA caching is not supported in WPA3 AP mode.
- The maximum embedded MQTT Publish payload is 1 kbyte.
- Timeout value for socket select and socket receive calls of less than 1 second is not currently supported.
- For BLE, if the connection is established with a small connection interval (less than 15 ms), simultaneous roles (i.e., Central + Scanning and Peripheral + Advertising) are not supported.
- BLE maximum two concurrent connections are supported, which can be either a connection to two peripheral devices, to one central and one peripheral device or two central devices.
- BLE Slave latency value is valid up to 32 only.
- BLE TX/RX throughput is less when tested with EFM as compared to EFR.
- Maximum supported AE data length is 200 bytes.
- Supports only two ADV_EXT sets.
- Supports only two BLE connections (1 Central and 1 Peripheral) with AE.
- Advertising Extension feature is not supported in Coexistence.
- Isochronous channels feature is not supported.
- Connection subrating feature is not supported.
- LE power controller feature is not supported.
- EATT feature is not supported.
- Periodic Advertising with response(PAwR) feature is not supported.
- BLE Audio is not supported.
- The feature of dynamically changing the TX power when extended advertising is active is not supported.
- Wi-Fi AP + BLE currently not supported
| Release date | Dec 13th, 2023 |
| SDK Version | 3.1.1 |
| Firmware Version | 1711.2.10.0.0.4 |
| Package Name | WiSeConnect3_SDK_3.1.1 |
| Supported RTOS | FreeRTOS |
| Operating Modes Supported | Wi-Fi STA, Wi-Fi AP, Wi-Fi STA+BLE, Wi-Fi STA+AP |
| Build Quality | GA |
- SiWx917 release consists of two components
- Wireless Firmware - SiWx917 Firmware Binaries
- Wiseconnect3 Library - Wiseconnect3 SDK library runs on the external host in NCP mode
- This release is meant only for use with designs based on SiWx917 Silicon
- The firmware to load in your design are available in the following format:
- SiWG917-B.2.10.0.0.4.x.rps - Sutlej B0 Full-featured firmware binary
- NCP EFR Expansion Kit with NCP Radio board SiWx917-EB4346A (BRD4346A + BRD8045A)
- BRD4002A Wireless pro kit mainboard SI-MB4002A
- EFR32xG24 Wireless 2.4 GHz +10 dBm Radio Board xG24-RB4186C
-
- Wi-Fi STA (802.11ax, 802.11n),
- Wi-Fi 802.11n AP,
- Wi-Fi STA (802.11ax, 802.11n) + 802.11n AP,
- Wi-Fi STA (802.11ax, 802.11n) + BLE:
-
- SPI
-
- Secure Boot
- Secure firmware upgrade over
- ISP
- Secure OTA
- Secure Key storage and HW device identity with PUF
- Secure Zone
- Secure XIP (Execution in place) from flash
- Secure Attestation
- Anti Rollback
- Secure Debug
- Flash Protection
-
- Crypto API's for Hardware Accelerators:
- Advanced Encryption Standard (AES) 128/256/192
- Secure Hash Algorithm (SHA) 256/384/512
- Hash Message Authentication Code (HMAC)
- Random Number Generator (RNG)
- SHA3
- AES-Galois Counter Mode (GCM)/ Cipher based Message Authentication Code (CMAC)
- ChaCha-poly
- True Random Number Generator (TRNG)
- Software Accelerators: RSA, ECC
- Integrated with mbed TLS
- Crypto API's for Hardware Accelerators:
-
- Deep Sleep
- With RAM retention
- Without RAM retention
- Connected Sleep
- Host based wake-up
- Deep Sleep
-
- IEEE 802.11 b/g/n/ax (2.4GHz)
-
- 4 Client Support
- WiFi Security
- WPA2 Personal
- WPA3 Personal (H2E method only)
- WPA Mixed mode (WPA/WPA2)
- Hidden SSID Mode
- Auto Channel Selection
- Scan in AP mode
-
- Selective Scan
- Active/Passive Scanning
-
- Open Mode
- WPA2 Personal, WPA2 Enhancements
- WPA3 Personal
- Mixed mode (WPA/WPA2)
- WPA3 Personal Transition Mode (WPA2/WPA3)
-
- Method
- PEAP/TTLS/TLS 1.0/TLS 1.2/FAST
- Method
-
- BG Scan
- OKC (Opportunistic Key caching)
- PMK (Pairwise Master Key) caching
- Pre-Authentication
-
- Deep sleep (unconnected state)
- Max PSP
- Enhanced Max PSP
- Fast PSP
- TWT
-
- WMM-QoS
-
- MUMIMO (DL)
- OFDMA (UL/DL)
- iTWT,** TWT I-Frame & TWT Enhancements
- BSS coloring
- MBSSID
-
- AP+STA (Same channel)
-
- 2.4GHz CH1-11
- 2.4GHz CH1-13
- 2.4GHz CH1-14 (Japan)
-
- WPA2 KRACK Attacks
- Fragment and Forge Vulnerability
-
- TCP/IP Bypass (LWIP as Hosted stack for reference)
- IPv4/IPv6/UDP/TCP/ARP/ICMP/ICMPv6
- SSL client versions TLSV1.0, TLSV1.2, TLSV1.3
- SSL server versions TLSV1.0 and TLSV1.2
- DHCP (Client/Server)/ DHCPv6 Client
-
- HTTP Client/HTTPS Client//DNS Client/SNTP Client
- Embedded MQTT/MQTT on host
-
- AWS IOT Core
- BSD and IoT sockets application programming interface(API)
- GAP ( Advertising, Scanning, initiation, Connection and Bonding)
- Generic Attribute Protocol (GATT)
- Attribute protocol (ATT)
- Security
- LL Privacy 1.2
- Accept list
- Directed Advertising
- Extended Advertising
- Periodic Advertising
- Periodic Advertising scanning
- Extended Advertising scanning
- Periodic Advertising list
- LE periodic advertising synchronization
- LE PHY(1Mbps, 2Mbps) & Coded PHY(125Kbps, 500kbps)
- Simultaneous scanning on 1M and Coded PHY
- LE dual role topology
- LE data packet length extensions( DLE)
- Asymmetric PHYs
- LE channel selection algorithm 2 (CSA#2)
- LE secure connections
- Bluetooth 5.4 Qualified( Clerical work pending)
- Wi-Fi STA + BLE
- 3 wire coex acting as Wi-Fi with external Bluetooth
- 3 wire coex acting as Wi-Fi with external Zigbee/OT
-
- Folder restructuring, renamed SLC features and components as part of componentization. (Refer Migration Guide)
- Standardized build parameters, enum, structures, typedef, and API signatures. (Refer Migration Guide)
- Added support for TA(NWP) buffer configuration in sl_wifi_init.
- Added support for sl_wifi_device_context_t in sl_wifi_init.
- Added support for WPA3 personal security (with H2E method only) in AP mode
- Added support for timeout configuration API
- Added support for Server Name Indication (SNI).
- Added support for Extensible Authentication Protocol (EAP) encrypted certificates.
- Replaced sl_tls with sl_net credential API.
- Updated certificate handling APIs.
- Updated and standardized README files for featured examples, MQTT, TWT, and more.
- Generic API reference documentation updation.
- Added support for CLI demo, HTTP client, WLAN throughput v6, and embedded MQTT client example applications for NCP mode
- Added support for customization support of ncp_host and spi_driver implementations using efx_ncp_custom_host_mcu and siwx917_ncp_custom_spi_driver respectively.
- Updated readme files for AES, calibration app, HTTP client, WLAN throughput v6, and embedded MQTT client.
- Updated documentation for the CLI demo in NCP mode.
-
- Resolved issues with CW modes in RF test example.
- Fixed the issue where application hangs issue during SHA operation on larger data exceeding 1400 bytes in TA(NWP).
- Fixed the issue where DUT sent non-aggregated packets with protected ADDBA response for improving throughput.
- Fixed the issue where the IOT socket connect/bind failed with -3 error in the CLI demo app.
- Fixed the issue where DUT_BLE stopped advertising after a few seconds while running wifi_ble_power_save_ncp application.
- Fixed the issue where sl_net_init returned 0xff82 as an error code in the case of WLAN throughput NCP.
-
- ble_power_save
- gatt_long_read
- ble_hid_on_gatt
- ble_unified_ae_coex_app
- ble_datalength
- ble_accept_list
- ble_central
- ble_longrange_2mpbps
- ble_heart_rate_profile
- ble_ibeacon
- ble_privacy
- ble_secureconnection
- ble_throughput_app
- ble_ae_central and ble_ae_peripheral applications.
-
- Readme files for ble_per and ble_accept_list.
- BLE API reference documentation with descriptions and navigation links.
- Added support for standby sleep with RAM retention in WLAN+BLE coex mode.
- Removed support for unused rsi_ble_set_prop_protocol_ble_bandedge_tx_power(), rsi_bt_ber_enable_or_disable(), and rsi_bt_per_cw_mode() APIs.
- Added support for rsi_ble_prepare_write_async, rsi_ble_execute_write_async and rsi_ble_get_inc_services SAPI's in gatt_test application.
-
- DUT transmitting 240 bytes MTU request packet regardless of programmed MTU length.
- DUT is unable to transmit complete periodic advertising data.
- Hang issue when transmitting BLE notification with coded PHY rates of 125kbps and 500kbps.
- DUT not transmitting BLE scan requests after 20sec when power save is enabled.
- DUT not transmitting packets continuously over the air in BLE test modes.
- BLE Set BD address API failing with error code 0xfffffffd (Command given in the wrong state).
- rsi_ble_set_local_att_value() API fails with error code 0xFFFFFFE2 (RSI_ERROR_RESPONSE_TIMEOUT) during BLE notification.
- "Failed to keep module in active mode: FFFFFFFF" issue when disabling power save after enabling enhanced max psp power save.
- BLE per stats cmd API fails with error code 0xFFFFFFE2 (RSI_ERROR_RESPONSE_TIMEOUT).
- BLE scanning stops within ~4-5 minutes when powersave is enabled.
-
- Added support for wifi_station_ble_provisioning with AWS cloud.
- Added support for the timer (with the power save disabled) in wifi_station_ble_provisioning_aws example.
- Added support for alarm-based power save mode in wlan_station_ble_provisioning_with_aws cloud example application.
- Increased priority of Wi-Fi handling of data transmission in coex mode.
- Replaced Printf statements with LOG_PRINT in all Coex example applications.
-
- Abrupt termination of HTTP download in the application when Powersave is enabled.
- Firmware update fails with 0x7 error code when power save is enabled in wifi_throughput_ble_dual_role application.
- Handling of PLL value in coex mode.
- BLE disconnection issue after ~25-30 min while running WLAN HTTP/HTTPs download along with BLE data transfer with Power save enabled.
- Set the recommended Power Save Profile (PSP) type to Enhanced Max PSP.
- Memory configuration for NCP mode is 672K_M4SS_0K.
- Simplicity Studio. This release is tested with SV5.8.0 version.
- Refer to the latest version of the NCP "Getting-Started-with-SiWx917" guide for more details
- It is recommended to enable bit 16 of the 'Extended TCP IP Feature' bit map in the opermode command for all Wi-Fi Socket operations from the host to ensure graceful handling during asynchronous closures from the peer.
- Aggregation (bit 2 of feature_bit_map) is recommended to be enabled in opermode. This enables software to aggregate multiple packets to achieve better throughput
- TCP retransmission count value is recommended to be 30 or higher so that the TCP does not disconnect while the rejoin happens.
- To reset TA (NWP), the application needs to call sl_wifi_deinit() followed by sl_wifi_init(). Users must ensure that no execution happens from flash at this point of time. (Refer to example applications)
- Users can enable SL_SI91X_EXT_TCP_IP_SSL_16K_RECORD in 'Extended TCP IP Feature' bit map in opermode for (HTTPS server) supporting 16k record.
-
- It is recommended to issue iTWT setup command once IP assignment, TCP connection, application specific socket connections are done.
- When using sl_wifi_enable_target_wake_time API, increase TCP / ARP Timeouts at the remote side depending upon the configured TWT interval configured. It's highly recommended to use sl_wifi_target_wake_time_auto_selection() as an alternative.
- In case of TWT in coex mode, when using sl_wifi_enable_target_wake_time API, use TWT wake duration <= 16 ms and TWT wake interval >= 1 sec. If wake duration > 16 ms or TWT wake interval < 1sec, there might be performance issues.
- For iTWT GTK interval in AP should be configured to max possible value or zero. If GTK interval is not configurable on AP side, recommended TWT interval (in case of sl_wifi_enable_target_wake_time API) or RX Latency (in case of sl_wifi_target_wake_time_auto_selection API) is less than 4sec.
- When sl_wifi_enable_target_wake_time API is used, configuring TWT Wake interval beyond 1 min might lead to disconnections from the AP. Recommended to use TWT wake interval of less than or equal to 1 min.
- When using sl_wifi_enable_target_wake_time API, it is recommended to set missed_beacon_count of sl_wifi_set_advanced_client_configuration API greater than 2 times of the configured TWT Interval.
- Disable power save for high throughput applications or use FAST PSP powersave mode as per application requirement.
- The application needs to ensure that it sets RTC with the correct timestamp when the feature is enabled before establishing the SSL/EAP connection.
- The minimum timeout value should not be less than 1 second for socket select and socket receive calls.
- Embedded MQTT keep alive interval should be either 0 or a value greater than 35 seconds.
- Disable power save and suspend any active TWT sessions before triggering HTTP OTAF.
- Randomize the client port if using rapid connect/disconnect of the MQTT session on the same client port with the power save.
- In BLE, the recommended range of Connection Interval in
- Power Save (BLE Only) - 100 ms to 1.28 s.
- In BLE, during Connection, the configuration of Scan Interval and Scan Window with the same value is not recommended. The suggested ratio of Scan Window to Scan Interval is 3:4.
- In BLE, if a device is acting as Central, the scan window (in set_scan_params and create_connection commands) must be less than the existing Connection Interval. The suggested ratio of Scan Window to Connection Interval is 2:3.
- In BLE mode, if scanning and advertising are in progress on the SiWx91x module and it subsequently gets connected and moves to the central role, scanning stops else if it moves to the peripheral role, advertising stops. To further establish a connection to another peripheral device or to a central device, the application should give a command for starting advertising and scanning again.
- For concurrent Wi-Fi + BLE, and while a Wi-Fi connection is active, we recommend setting the ratio of the BLE scan window to BLE scan interval to 1:3 or 1:4.
- Wi-Fi + BLE Advertising
- All standard advertising intervals are supported. As Wi-Fi throughput is increased, a slight difference in on-air advertisements compared to configured intervals may be observed.
- BLE advertising is skipped if the advertising interval collides with Wi-Fi activity.
- Wi-Fi + BLE scanning
- All standard scan intervals are supported. For better scan results, we recommend setting the ratio of the BLE scan window to BLE scan interval to 1:3 or 1:4.
- BLE scanning will be stopped for intervals that collide with Wi-Fi activity.
- Wi-Fi + BLE Central/Peripheral Connections
- All standard connection intervals are supported.
- 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 achieve higher throughput for both Wi-Fi and BLE, use medium connection intervals, such as 45 to 80 ms with maximum supervision timeout.
- Ensure Wi-Fi activity consumes lower intervals.
- Sometimes during SSL Handshake, ECC curve parameters generated are wrong, resulting in connection failure with BBD2 error. However, this recovers in the next attempt.
- Secure SSL renegotiation not supported in Embedded Networking Stack
- Every server socket created consumes a socket and every subsequent connection consumes an additional socket.
- Observed failure with BIT_TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384, BIT_TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 ciphers
- Configuration issue to program MSS, TCP retry count
- Observed inconsistency with MQTT keep alive when TWT is enabled
- TWT device (STA) may not go to sleep in between TWT intervals in case of burst data traffic where data transfer happens over multiple TWT service periods.
- When sl_wifi_enable_target_wake_time() API is used, observed occasional MQTT disconnections with longer TWT intervals (>30secs) with embedded MQTT + TWT.
- There are performance and IOP issues with MU MIMO.
- STA Connection with the WPA3 Hunting and Pecking algorithm takes about 3-4 seconds.
- Issue observed with WPA2 Enterprise Connectivity using Microsoft RADIUS Server.
- Observed HTTPS Continuous download fails with TA Power save
- Planned performance improvements are in progress to get optimal performance in Wi-Fi/WiFi+BLE
- Observed interop issue (connectivity failure) with few AP's(EERO 6+, EERO PRO 6E, Cisco Catalyst 9120AXID) when device reset/reboot happens on active connection.
- Unable to get SNTP async events when coex mode and power save are enabled and not getting any response for sl_net_up API for 2nd Iteration
- Disconnections observed with Netgear RAX120 AP in WPA3 security
- Observed connection failures with some AP's in more channel congestion ~50-60% occupancy open lab environment.
- In AP mode, first few beacons don't include RSN IE.
- Issue with fixed rate configuration in AP mode.
- Configuration issue to program PAC file for EAP FAST Manual mode.
- Optional LDPC feature is not enabled, So observed less throughput in DL-OFDMA with some APs.
- Observed issue with configuring Certificate key and programming 4096 bit key and SHA384/SHA512 certificates.
- Observed auth/assoc timeout is not affecting/working as per timeout configuration.
- Observed sl_net_deinit is not returning any response for both "SL_NET_WIFI_AP_INTERFACE" and "SL_NET_WIFI_CLIENT_INTERFACE" interfaces.
- Observed AWS MQTT keepalive transmission is not happening at expected intervals with power save enabled.
- WoWLAN feature not supported.
- Observed QOS1 publish is not happening in 3rd iteration while aws_mqtt application running in loop
- Observed DUT is going back to power save before the monitor interval when there is no RX data from AP in ENH MAX PSP
- Observed DUT is giving Incorrect error code(0x5) for SNTP create when ludp socket is opened at 123 port.
- When running the ble_central application with power save enabled, it was observed that the BLE connect API is failing because of 0xFFFFFFE2(RSI_ERROR_RESPONSE_TIMEOUT) error.
- When running the ble_ae_central example, observed an application hang issue at the AE Clear Periodic Adv list API.
- BLE connection failure has been observed on a few mobile devices (Samsung S23& Oneplus 9pro) when device is configured as central.
- The maximum power that BLE can support is 16 dBm. It is not permitted for users to program more than 16dBm. 127 power_index is not supported in this release.
- Observed inconsistency issues with Wi-Fi + BLE in powersave mode
- MU retries in DL MUMIMO are more in CoEx
- While executing WIFI Commissioning using the wifi_station_ble_provisioning example, BLE is disconnecting is observed with few boards.
- Observed "DUT is not disconnecting to the AP when initiating disconnection from EFR connect app screen using wifi_station_ble_provisioning_aws example
- None
- None
- TLS 1.3 Server is not supported
- Broadcast TWT is not supported.
- AMSDU TX is not supported.
- Fragmentation is not supported.
- AMSDUs within AMPDU is not supported.
- Currently, the module does not support Radio Measurement Requests feature of CCX V2
- 802.11k is not supported
- 40 MHz bandwidth for 2.4 GHz band is not supported.
- Maximum of 3 SSL connections are supported in Wi-Fi alone mode.
- In SSL ECC Curve ID supported is 23. SSL handshake with 3rd party clients depends on the SSL ECC Curve ID.
- Legacy TA(NWP) LP mode is not supported.
- In iTWT mode, downlink data traffic should be limited. Disconnections may be observed if AP fails to send all the buffered data in the next TWT Service Period.
- The number of Non-Transmitting BSSIDs processed is limited by the beacon length that can be processed by the stack (which is 1024 bytes). Beacons greater than 1024 Bytes in length will not be processed.
- UL MUMIMO is not supported.
- The embedded HTTP server is not supported.
- Baremetal is not supported
- Compared to SoC mode, NCP mode has fewer examples, but more will be enabled in upcoming releases.
- WPA3 AP supports only H2E algorithm.
- PMKSA caching is not supported in WPA3 AP mode.
- UART 2 Debug prints are supported only on ULP_GPIO_9.
- WiFi Mesh not supported
- Apple HomeKit not supported
- Cellular coexistence not supported
- The maximum embedded MQTT Publish payload is 1 kbyte.
- Timeout value for socket select and socket receive calls of less than 1 second is not currently supported.
- For BLE, if the connection is established with a small connection interval (less than 15 ms), simultaneous roles (i.e., Central + Scanning and Peripheral + Advertising) are not supported.
- BLE maximum two concurrent connections are supported(1 Central connection and 1 Peripheral connection) or (2 Central connections) or (2 Peripheral connections)).
- BLE Slave latency value is valid up to 32 only.
- BLE TX/RX throughput is less when tested with EFM as compared to EFR.
- Maximum supported AE data length is 200 bytes.
- Supports only two ADV_EXT sets.
- Supports only two BLE connections (1 Central and 1 Peripheral) with AE.
- Advertising Extension feature is not supported in Coexistence.
- Isochronous channels feature is not supported.
- Connection subrating feature is not supported.
- LE power controller feature is not supported.
- EATT feature is not supported.
- Periodic Advertising with response(PAwR) feature is not supported.
- BLE Audio is not supported.
- The feature of dynamically changing the TX power when extended advertising is active is not supported.
- All projects in the package are compatible with GCC 12.2.2 version.
This SDK package supports SoC Mode and NCP Mode for A0 and B0:
- In SoC Mode: Customer applications can run on Cortex M4. Wireless, network, and security stacks run on the wireless subsystem.
- In NCP mode: Wireless, network, and security stacks run on the Wireless subsystem. Customer applications run on the external host MCU.
- Silicon Labs' SiWx917 includes an ultra-low power Wi-Fi 6 plus Bluetooth Low Energy (BLE) 5.1 wireless subsystem and an integrated micro-controller application subsystem.
Note: Use Simplicity Studio version SV5.7.0.1 onwards
- Operating Modes : Wi-Fi STA (802.11ax, 802.11n), Wi-Fi 802.11n AP, Wi-Fi STA (802.11ax, 802.11n) + 802.11n AP, Wi-Fi STA (802.11ax, 802.11n) + BLE
- Wireless Protocols : IEEE 802.11b, 802.11g, 802.11n, 802.11ax, BLE 5.1
- Multiple Ultra Low Power Modes : Support ultra low power Wi-Fi standby associated current in Wi-Fi 4 mode, Ultra low power Wi-Fi Standby associated current in Wi-Fi 6 mode leveraging TWT, Always on Cloud connected power, BLE connected power, and, deep sleep ULP mode
- MCU examples : GPIO, I2C, Calendar, SPI, SSI, SIO, Micro DMA, UART/USART, Watchdog Timer, Timers, Config Timers, ULP (Ultra Low Power) Timers, Sleeptimer, IOSTREAM, NVM3, MEMLCD, SDIO Secondary, PWM, ADC, EFUSE, I2S, PSRAM, ML Blinky, Sensorhub
- Wi-Fi : 2.4GHz Wi-Fi Support - WPA2/WPA3 Personal, Wi-Fi 6 OFDMA/MU-MIMO Support that enhances network capacity and reduces latency
- Cloud : Amazon Cloud Connectivity Support, Amazon FreeRTOS
- BLE : BLE 5.1, BLE dual role (Central and Peripheral Support), Advertising extensions, Data length extensions, LL privacy, BLE whitelisting, and BLE long Range.
- Integrated Stacks and Profiles : Wi-Fi Stack, BLE Stack, All GAP and GATT based Profiles & Services are Supported, TCP/IP stack with TLS 1.3, HTTP/HTTPS, DHCP, MQTT Client, DNS client
- IDE : Simplicity Studio with Windows 10(64-bit), Linux, Mac OS
- TA/M4 Firmware Update Tool : Simplicity Commander
- Hardware kits to evaluate SoC Mode :
- Si-MB4002A Main board
- SiWx917 Radio boards
| RadioBoard Type | SiWx917A0 with Board Version | SiWx917B0 with Board Version |
|---|---|---|
| Common flash | Si917-BRD4325A(1.0 /1.1 /1.2) | - |
| Common flash | - | Si917-BRD4338A(2.0) |
| Dual flash | Si917-BRD4325B(1.0 /1.1 /1.2) | - |
| External PSRAM | - | Si917-BRD4340A(2.0) |
- Host Interface : SPI
- Operating Modes : Wi-Fi STA (802.11ax, 802.11n), Wi-Fi 802.11n AP, Wi-Fi STA (802.11ax, 802.11n) + 802.11n AP, Wi-Fi STA (802.11ax, 802.11n) + BLE
- Wireless Protocols : IEEE 802.11b, 802.11g, 802.11n, 802.11ax, BLE 5.1
- Multiple Ultra Low Power Modes : Support Ultra low power Wi-Fi Standby associated current in Wi-Fi 4 mode, Ultra low power Wi-Fi Standby associated current in Wi-Fi 6 mode leveraging TWT, Always on Cloud connected power, BLE connected power, and, deep sleep ULP mode.
- Wi-Fi : 2.4GHz Wi-Fi Support, WPA2/WPA3 Personal, Wi-Fi 6 OFDMA/MU-MIMO Support that enhances network capacity and reduces latency
- BLE : BLE 5.1, BLE dual role (Central and Peripheral Support), Advertising extensions, Data length extensions, LL privacy, BLE Whitelisting and BLE long Range.
- Integrated Stacks and Profiles : Wi-Fi Stack , BLE Stack , All GAP and GATT based Profiles & Services are Supported, TCP/IP stack with TLS 1.3, HTTP/HTTPS, DHCP, MQTT Client, DNS Client.
- IDE : Simplicity Studio with Windows 10(64-bit)
- Hardware kits to evaluate NCP Mode
- Si917 B0 1.2 expansion board BRD8036B
- Wireless Pro kit Mainboard BRD4002A Rev A06
- EFR32xG21 2.4 GHz 20 dBm Radio Board (BRD4180B Rev A02)
| Item | Details |
|---|---|
| Release date | Oct 9th, 2023 |
| SDK Version | 3.1.0 |
| Firmware Version | 1711.2.9.0.0.21 |
| Package Name | WiSeConnect3_SDK_3.1.0 |
| Supported RTOS | FreeRTOS |
| Operating Modes Supported | Wi-Fi STA, Wi-Fi AP, Wi-Fi STA+BLE, Wi-Fi STA+AP |
| Build Quality | Beta |
- SiWx917 release consists of two components
- Wireless Firmware - SiWx917 Firmware Binaries
- Wiseconnect3 Library - Wiseconnect3 SDK library runs on the external host in NCP mode and internal Cortex M4 in SoC Mode.
- This release is meant only for use with designs based on SiWx917 Silicon
- The firmware to load in your design are available in the following format:
- SiWG917-A.2.9.0.0.x.rps - A0 Full-featured firmware binary
- SiWG917-B.2.9.0.0.x.rps - B0 Full-featured firmware binary
MCU
- ADC Single Channel, ADC Static Mode, Analog Comparator, Blinky, Bod, CTS, DAC FIFO, DAC Static, GPIO, I2C, I2S, NVM3, OPAMP, PSRAM, PWM, QEI, RTC, SDIO Secondary, SPI Master and Slave, UART, Micro DMA, USART, Watchdog Timer, USART Master and Slave
- UC Supported Peripherals - GPIO, I2C, Calendar, SPI, SSI, SIO, Micro DMA, UART/USART, Watchdog Timer, Timers , Config Timers, ULP (Ultra Low Power) Timers, SDIO Secondary, PWM, ADC, EFUSE, I2S, PSRAM, Sleeptimer, IOSTREAM, MEMLCD.
- ULP (Ultra Low Power) Peripherals - ulp_gpio, ulp_adc ulp_i2c, ulp_i2s, ulp_ir_decoder, ulp_spi, ulp_timer, ulp_uart, ulp_udma
Wi-Fi
- WPA2/WPA3 Personal, WPS and WPA2-EAP Support for Station Mode
- TCP/IP stack with IPv4, IPv6, TCP, UDP, TLS, HTTP/HTTPS, DHCPv4, DHCPv6, MQTT Client, DNS Client, SNTP client.
- Support for SSL client versions TLSV1.0, TLSV1.2, TLSV1.3 and SSL server versions TLSV1.0 and TLSV1.2
- Wi-Fi STA (802.11n/802.11ax) + 802.11n AP Support
- HE (802.11ax) and Individual TWT Feature Support
- Multiple BSSID feature support as an STA
- Secure OTA support on B0 radio boards.
- Support for LWIP network stack
- Support for AWS MQTT library
- Support for BSD and IoT sockets application programming interface(API)
Bluetooth Low Energy
- BLE central & peripheral connections are supported.
- Ultra-low power save is supported.
Power Save
- The power save profiles supported are Max PSP, enhanced MAX PSP, Fast PSP, and 802.11ax TWT.
Crypto Support
- AES, SHA, AES-CCM, HMAC, and TRNG FW Crypto API support added.
- PSA enabled Mbed TLS support added
- NVM support is added for key storage
- Symmetric key storage support added for Volatile and transparent key.
- TRNG, AES, SHA, and AES-CCM hardware crypto engine is integrated with PSA crypto.
MCU
- Added Ultra Low Power(ULP) examples support for SSI Master, USART, Micro DMA, Calendar, GPIO, I2C Leader, Timer.
Wi-Fi
- Added support for Efuse read, User Gain tables, Calibration Software APIs
- Added support for M4 soft reset
- Added example support tcp_tx_on_periodic_wakeup_soc, wlan_throughput_psram, twt_use_case_remote_app
- Enhancement of SNTP example to support async notification
- Updation of Readme files to have a unified "Project Environment" section
- Added support for sl_wifi_enable_target_wake_time() API
- Added M4 power save support for embedded_mqtt_client_twt and twt_tcp_client, twt_use_case_demo, aws_device_shadow_logging_stats examples
- Fixed security setting failure to apply properly while enabling the APUT in DUT
- Removal of file duplicates sl_net_default_values.h
- Readme enhancement to fix setup diagram images
- Removal of all UAPSD references
- RTC timer get and set APIs
- Added PSRAM board support for applications
- Added TA and M4 power save for lwip_tcp_client example
- Updation of wlan_throughput example SI91x asynchronous sockets for high throughputs
- Added support to handle transmit test opermode
- Updated print_sl_ipv6_address() utility to print IP address in new format.
- Added M4 power save support for tcp_tx_on_periodic_wakeup example
- Added thread-safe support for malloc and free functions
- Added SNI option for sockets
- Added support for AP stop feature
- Fixed issue stability issues in firmware update
- Added support for WPA3
- Added API support for configuration of listen interval
- Added NCP support for AWS MQTT, twt_tcp_client, power_save_deep_sleep, enterprise_client examples
- Added crypto examples - HMAC, PSA SHA, si91x_psa_asymmetric_key_storage, si91x_psa_symmetric_key_storage, si91x_psa_aes, ECDH, PSA GCM, PSA HMAC.
- Fixed async event handling in the aws_device_shadow application
- Updated readme of cli_demo with steps to add new command handlers
BLE
- Fixed high power numbers issue in BLE PER application with Tx and Rx in SoC mode
- Added ble_testmodes demo in SoC & NCP
- Added gatt_long_read, ble_ae_central and ble_ae_peripheral applications in SoC
- Renaming of all references of whitelist to acceptlist in all BLE examples
- Added support for test agent application for BLE commands
- Added support for rsi_ble_req_hci_raw command
- Added support for 352K_320K memory configuration in immediate_alert_client example application
CoEx
- Added wifi_station_ble_throughput_app coex application
- Added studio support and logging stats feature for wifi_station_ble_provisioning_aws_logging_stats application
- Fixed BLE notifications issue in wifi_throughput_ble_dual_role application
- Fixed 0 Mbps data samples in WLAN throughput test in wifi_throughput_ble_dual_role application
System
- None
System
- The current revision of SiWx917 B0 has:
- RAM memory of 672k bytes which can be shared between TA and M4 processors in NCP/SoC mode. The following memory configuration modes are supported.
- EXT_FEAT_672K_M4SS_0K- This mode configures TA with 672k and M4 with 0K bytes of memory which is applicable only in the case of NCP mode
- The below configurations are applicable in SoC mode and can be configured based on the application requirement By default EXT_FEAT_352K_M4SS_320K configuration will be selected in SoC mode
- EXT_FEAT_480K_M4SS_192K - This mode configures TA with 480k and M4 with 192K bytes of memory
- EXT_FEAT_416K_M4SS_256K - This mode configures TA with 416k and M4 with 256K bytes of memory
- EXT_FEAT_352K_M4SS_320K - This mode configures TA with 352k and M4 with 320K bytes of memory
- The currently supported memory configuration for NCP mode is 672K_M4SS_0K.
- SoC mode should not use 672k_M4SS_0k memory configuration.
- RAM memory of 672k bytes which can be shared between TA and M4 processors in NCP/SoC mode. The following memory configuration modes are supported.
- Set the recommended Power Save Profile (PSP) type to Enhanced Max PSP.
IDE
- Download the latest Simplicity Studio (SV5.7.0.1)
- Refer to the latest version of the SoC/NCP "Getting-Started-with-SiWx917" guide for more details
Network Stack
- The recommended embedded MQTT Publish payload is 1 kBytes.
Wi-Fi
- It is recommended to enable bit 16 of the 'Extended TCP IP Feature' bit map in the opermode command for all Wi-Fi Socket operations from the host to ensure graceful handling during asynchronous closures from the peer.
- Aggregation (bit 2 of feature_bit_map) is recommended to be enabled in opermode. This enables software to aggregate multiple packets to achieve better throughput
- TCP retransmission count value is recommended to be 30 or higher so that the TCP does not disconnect while the rejoin happens.
- To restart the module, the application needs to call sl_wifi_deinit() followed by sl_wifi_init().
- 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.
- User can enable SL_SI91X_EXT_TCP_IP_SSL_16K_RECORD in 'Extended TCP IP Feature'bit map in opermode, if HTTPS download is failing after receiving HTTP headers..
- iTWT setup is recommended after IP assignment/TCP connection/application specific socket connections.
- When using sl_wifi_enable_target_wakeup_time API, increase TCP / ARP Timeouts at the remote side depending upon the configured TWT interval configured.
- In case of TWT+coex, when using sl_wifi_enable_target_wakeup_time API, use TWT wake duration <= 16 ms and TWT wake interval >= 1 sec. If wake duration > 16 ms or TWT wake interval < 1sec, there might be performance issues.
- For iTWT GTK Interval Should be kept max possible value or zero. If GTK interval is not configurable, recommended TWT interval (in case of sl_wifi_enable_target_wakeup_time API) or RX Latency (in case of sl_wifi_target_wake_time_auto_selection API) is less than 4sec.
- Disable Power Save for High Throughput Applications.
- The application needs to ensure that it sets RTC with the correct timestamp when the feature is enabled before establishing the SSL connection.
- The timeout value should not be less than 1 second for socket select and socket receive calls. Timeout value of less than 1 second is not currently supported.
- When sl_wifi_enable_target_wakeup_time API is used, configuring TWT Wake interval beyond 1 min might lead to disconnections from the AP. Recommended to use TWT wakeup interval of less than or equal to 1 min.
- Embedded MQTT keep alive interval should be either 0 or a value greater than 35 seconds.
- When using sl_wifi_enable_target_wakeup_time API, it is recommended to set missed_beacon_count of sl_wifi_set_advanced_client_configuration API greater than 2 times of the configured TWT Interval.
BLE
- In BLE, the recommended range of Connection Interval in
- Power Save (BLE Only) - 100 ms to 1.28 s.
- In BLE, during Connection, the configuration of Scan Interval and Scan Window with the same value is not recommended. The suggested ratio of Scan Window to Scan Interval is 3:4.
- In BLE, if a device is acting as Central, the scan window (in set_scan_params and create_connection commands) must be less than the existing Connection Interval. The suggested ratio of Scan Window to Connection Interval is 2:3.
- In BLE mode, if scanning and advertising are in progress on the SiWx91x module and it subsequently gets connected and moves to the central role, scanning stops else if it moves to the peripheral role, advertising stops. To further establish a connection to another peripheral device or to a central device, the application should give a command for starting advertising and scanning again.
Co-Existence
- For concurrent Wi-Fi + BLE, and while a Wi-Fi connection is active, we recommend setting the ratio of the BLE scan window to BLE scan interval to 1:3 or 1:4.
- Wi-Fi + BLE Advertising
- All standard advertising intervals are supported. As Wi-Fi throughput is increased, a slight difference in on-air advertisements compared to configured intervals may be observed.
- BLE advertising is skipped if the advertising interval collides with Wi-Fi activity.
- Wi-Fi + BLE scanning
- All standard scan intervals are supported. For better scan results, we recommend setting the ratio of the BLE scan window to BLE scan interval to 1:3 or 1:4.
- BLE scanning will be stopped for intervals that collide with Wi-Fi activity.
- Wi-Fi + BLE Central/Peripheral Connections
- All standard connection intervals are supported.
- 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 achieve higher throughput for both Wi-Fi and BLE, use medium connection intervals, such as 45 to 80 ms with maximum supervision timeout.
- Ensure Wi-Fi activity consumes lower intervals.
Network Stack
- Sometimes during SSL Handshake, ECC curve parameters generated are wrong, resulting in connection failure with BBD2 error. However, this recovers in the next attempt.
- 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.
Wi-Fi
- TWT device (STA) may not go to sleep in between TWT intervals in case of burst data traffics with data size more than the configured 'average tx throughput', until completion of data transfer.
- There are performance and IOP issues with MU MIMO.
- WPA3 Connection with the Hunting and Pecking algorithm takes about 3-4 seconds.
- Issue observed with WPA2 Enterprise Connectivity using Microsoft RADIUS Server.
- Low Wi-Fi+BLE throughput
- TCP/UDP TX/RX Data stall observed in CoEx scenarios
- Observed HTTPS Continuous download fails with TA Power save
- Performance improvements are in progress for lower performance metrics.
- Observed interop issue (connectivity failure) with few AP's when device reset/reboot happens on active connection.
- In concurrent mode, AP restart fails after stopping it with ap_stop command.
- DUT deep sleep will not work after stopping AP with ap_stop command.
- Unable to get SNTP async events when coex mode and Power save is enabled
- Fine Tuning 802.11ax Spectral mask in Progress
- Fine Tuning 11b mask in Ch11 in progress
- DUT is unable to connect to the AP with WPA3 security when we enable coex mode (WLAN+BLE) in opermode
- Socket listen API is failing from the second iteration
- Disconnections observed with Netgear RAX120 AP in WPA3 security
- Observed connection failures with some AP's in more channel congestion open lab environment
BLE
- M4 Power save with RTOS is not supported for BLE scan and data transfer in SoC Mode.
- BLE anchor points will experience a miss rate of approximately 10%, when the slave latency is enabled.
- When power save is enabled, the device stops sending BLE scan requests after 20 seconds.
- DUT hangs when transmitting BLE notification with codded PHY rates of 125kbps and 500kbps, when DLE is enabled.
- DUT is not transmitting packets continuously over the air in BLE test modes.
- After connecting to the remote device using gatt_test applications, GATT APIs could not be triggered.
- DUT hangs during multiple iterations of BLE connect and disconnect tests with TA and M4 power enabled.
Co-Existence
- Observed HTTP continuous download is not happening in Powersave mode after BLE connection established using wifi_https_ble_dual_role application
- Observed DUT hang while Wi-Fi UDP Tx and BLE continuous scan run for long time.
- sl_wifi_init throws insufficient memory(0x2C) error, when low_power_mode feature is enabled in CoEx application with "TA_352K_M4SS_320K" Memory configuration.
System
- None
- Refer to the respective Radio board user guides for specific pinout details. Examples are targeted to a specific version mentioned in the respective readme.
- Few peripherals like WDT when configured with RO clock is not working as expected. No impact on the feature but the clocks are not accurate.
Wi-Fi/Network Stack
- TLS 1.3 Server is not supported
- In AP mode, IPv6 Router Advertisements are not supported. Although STA connected to the APUT can transfer IPv6 data to the peers by using SLAAC for address configuration.
- When sl_wifi_enable_target_wake_time() API is used, observed occasional MQTT disconnections with longer TWT intervals (>30secs) with embedded MQTT + TWT.
- AMSDU TX is not supported.
- Fragmentation is not supported.
- AMSDUs within AMPDU is not supported.
- Currently, the module does not support Radio Measurement Requests feature of CCX V2
- 802.11k is not supported
- 40 MHz bandwidth for 2.4 GHz band is not supported.
- 802.11J channel 14 is not supported.
- MQTT versions 3 and 4 are supported.
- Maximum of 3 SSL connections are supported in Wi-Fi alone mode.
- In SSL ECC Curve ID supported is 23. SSL handshake with 3rd party clients depends on the SSL ECC Curve ID.
- LP mode is not supported.
- In iTWT mode, downlink data traffic should be limited. Disconnections may be observed if AP fails to send all the buffered data in the next TWT Service Period.
- Number of MBSSIDs processed is limited by the beacon length that can be processed by the stack (which is limited to 1024 bytes). Beacons greater than 1024 Bytes in length will not be processed.
- In A0 SoC mode, M4 power save will work with 384k TA and 320 M4 memory configuration only. It is not supported for "448K TA and 256k M4" and "512k TA and 192k M4" memory configurations
- CoEx + EAP Security in 352K/320k is not feasible. This issue is observed due to a lack of memory in the 352k/320k Memory Configuration. It is supported with other EXT_FEAT_416K_M4SS_256K and EXT_FEAT_480K_M4SS_192K memory configurations.
- UL MUMIMO is not supported.
- The embedded HTTP server is not supported.
- Baremetal is not supported
- Compared to SoC mode, NCP mode has fewer examples, but more will be enabled in upcoming releases.
BLE
- For BLE, if the connection is established with a small connection interval (less than 15 ms), simultaneous roles (i.e., Central + Scanning and Peripheral + Advertising) are not supported.
- BLE maximum two concurrent connections are supported, which can be either a connection to two peripheral devices, to one central and one peripheral device or two central devices.
- BLE Slave latency value is valid up to 32 only.
- BLE TX/RX throughput is less when tested with EFM as compared to EFR
- Maximum supported AE data length is 200 bytes.
- Supports only two ADV_EXT sets.
- Supports only two BLE connections (1 Central and 1 Peripheral) with AE.
- Advertising Extension feature is not supported in Coexistence.
- The demo's ae_central & ae_peripheral are not supported with TA_352K_M4_320K RAM configuration.
MCU
- ULP Peripherals examples configurations are for RAM-based execution, as flash is powered off in ULP Mode.
- On 4338a board, two I2C instances(I2C1 and I2C2) are using same GPIOs, so support is not there for using two I2C instances simultaneously.
- I2C High speed mode not supported.
- Manual chip select option is not supported when using GSPI and SSI.
Simplicity Studio and Commander
- Default GDB debug configuration is not supported for SoC projects, work around details provided in "Getting-Started-with-SiWx917"
- Observing flash download failures(ERROR 108) for a few image sizes
- While creating project through Simplicity Studio, "copy contents" option not supported.
- Simplicity commander does not support options under "Debug Lock tools" .
| Term | Description |
|---|---|
| New Features | These items are new to this release |
| Changes/Issues Fixed | Changes made to existing features found in previous software releases. |
| Enhancements to existing product flow and feature set. | |
| Bug fixes done in the release | |
| Deprecated Items | Features or functions or APIs that are removed from the distributed release to align with the software roadmap |
| Known Issues | Features or functions that do not work as planned at the time of release. Workarounds may be offered to meet short-term development goals, but longer-term solutions will be added in future software releases |
| Limitations/Recommendations | Describes the limitations on product usage and recommendations for optimal use cases |
- Change SPI frequency to 12.5Mhz while measuring BLE throughput with EFR32
WiSeConnect3_SDK_3.0.13 Release Notes
This SDK package supports SoC Mode and NCP Mode for A0 and B0:
- In SoC Mode: Customer Applications can run on Cortex M4. Wireless, network, and security stacks run on the Wireless subsystem.
- In NCP mode: Wireless, network, and security stacks run on the Wireless subsystem. Customer applications run on the external host MCU.
- Silicon Labs' SiWx917 includes an ultra-low power Wi-Fi 6 plus Bluetooth Low Energy (BLE) 5.1 wireless subsystem and an integrated micro-controller application subsystem.
Note: Use Simplicity Studio version SV5.7.0.1 onwards
SoC Highlights
- Operating Modes : Wi-Fi STA (802.11ax, 802.11n), Wi-Fi 802.11n AP, Wi-Fi STA (802.11ax, 802.11n) + 802.11n AP, Wi-Fi STA (802.11ax, 802.11n) + BLE
- Wireless Protocols : IEEE 802.11b, 802.11g, 802.11n, 802.11ax, BLE 5.1
- Multiple Ultra Low Power Modes : Support Ultra low power Wi-Fi Standby associated current in Wi-Fi 4 mode, Ultra low power Wi-Fi Standby associated current in Wi-Fi 6 mode leveraging TWT, Always on Cloud connected power, BLE connected power, and, deep sleep ULP mode
- MCU examples : GPIO, I2C, Calendar, SPI, SSI, SIO, UDMA, UART/USART, WDT, Timers, Config Timers, ULP (Ultra Low Power) Timers, Sleeptimer, IOSTREAM, NVM3, MEMLCD.
- Wi-Fi : 2.4GHz Wi-Fi Support - WPA2/WPA3 Personal, Wi-Fi 6 OFDMA/MU-MIMO Support that enhances network capacity and reduces latency
- Cloud : Amazon Cloud Connectivity Support, Amazon FreeRTOS
- BLE : BLE 5.1, BLE dual role (Central and Peripheral Support)
- Integrated Stacks and Profiles : Wi-Fi Stack, BLE Stack, and Profiles, TCP/IP stack with TLS 1.3, HTTP/HTTPS, DHCP, MQTT Client, DNS client
- IDE : Simplicity Studio with Windows 10(64-bit), Linux, Mac OS
- TA/M4 Firmware Update Tool : Simplicity Commander
- Hardware kits to evaluate SoC Mode :
- Si-MB4002A Main board
- SiWx917 Radio boards
| RadioBoard Type | SiWx917A0 with Board Version | SiWx917B0 with Board Version |
|---|---|---|
| Common flash | Si917-BRD4325A(1.0 /1.1 /1.2) | - |
| Common flash | - | Si917-BRD4338A(2.0) |
| Dual flash | Si917-BRD4325B(1.0 /1.1 /1.2) | - |
NCP Highlights
- Host Interface : SPI
- Operating Modes : Wi-Fi STA (802.11ax, 802.11n), Wi-Fi 802.11n AP, Wi-Fi STA (802.11ax, 802.11n) + 802.11n AP, Wi-Fi STA (802.11ax, 802.11n) + BLE
- Wireless Protocols : IEEE 802.11b, 802.11g, 802.11n, 802.11ax, BLE 5.1
- Multiple Ultra Low Power Modes : Support Ultra low power Wi-Fi Standby associated current in Wi-Fi 4 mode, Ultra low power Wi-Fi Standby associated current in Wi-Fi 6 mode leveraging TWT, Always on Cloud connected power, BLE connected power, and, deep sleep ULP mode.
- Wi-Fi : 2.4GHz Wi-Fi Support, WPA2/WPA3 Personal, Wi-Fi 6 OFDMA/MU-MIMO Support that enhances network capacity and reduces latency
- BLE : BLE 5.1, BLE dual role (Central and Peripheral Support)
- Integrated Stacks and Profiles : Wi-Fi Stack , BLE Stack and Profiles, TCP/IP stack with TLS 1.3, HTTP/HTTPS, DHCP, MQTT Client, DNS Client.
- IDE : Simplicity Studio with Windows 10(64-bit)
- Hardware kits to evaluate NCP Mode
- Si917 B0 Single Band Radio Board (BRD4338A)
- Wireless Pro kit Mainboard BRD4002A Rev A06
- EFR32xG21 2.4 GHz 20 dBm Radio Board (BRD4180B Rev A02)
Release Details
| Item | Details |
|---|---|
| Release date | Aug 18th, 2023 |
| SDK Version | 3.0.13 |
| Firmware Version | 1711.2.9.0.0.19 |
| Package Name | WiSeConnect3_SDK_3.0.13 |
| Supported RTOS | FreeRTOS |
| Operating Modes Supported | Wi-Fi STA, Wi-Fi AP, Wi-Fi STA+BLE, Wi-Fi STA+AP |
| Build Quality | Beta(NCP) |
Updating to this Release
- SiWx917 release consists of two components
- Wireless Firmware - SiWx917 Firmware Binaries
- Wiseconnect3 Library - Wiseconnect3 SDK Library runs on the external host in NCP mode and internal Cortex M4 in SoC Mode.
- This release is meant only for use with designs based on SiWx917 Silicon
- The firmware to load in your design are available in the following format:
- SiWG917-A.2.9.0.0.x.rps - A0 Full-featured firmware binary
- SiWG917-B.2.9.0.0.x.rps - B0 Full-featured firmware binary
Features Supported
MCU
- ADC Single Channel, ADC Static Mode, Analog Comparator, Blinky, Bod, CTS, DAC FIFO, DAC Static, GPIO, I2C, I2S, NVM3, OPAMP, PSRAM, PWM, QEI, RTC, SDIO Slave, SPI Master and Slave, UART, UDMA, USART, WDT, USART Master and Slave
- UC Supported Peripherals - GPIO, I2C, Calendar, SPI, SSI, SIO, UDMA, UART/USART, WDT, Timers , Config Timers, ULP (Ultra Low Power) Timers, Sleeptimer, IOSTREAM, MEMLCD
- ULP (Ultra Low Power) Peripherals - ulp_gpio, ulp_adc ulp_i2c, ulp_i2s, ulp_ir_decoder, ulp_spi, ulp_timer, ulp_uart, ulp_udma
Wi-Fi
- WPA2/WPA3 Personal, WPS and WPA2-EAP Support for Station Mode
- TCP/IP stack with IPv4, IPv6, TCP, UDP, TLS, HTTP/HTTPS, DHCPv4, DHCPv6, MQTT Client, DNS Client, SNTP client.
- Support for SSL client versions TLSV1.0, TLSV1.2, TLSV1.3 and SSL server versions TLSV1.0 and TLSV1.2
- Wi-Fi STA (802.11n/802.11ax) + 802.11n AP Support
- HE (802.11ax) and Individual TWT Feature Support
- Multiple BSSID feature support as an STA
- Secure OTA support on B0 radio boards.
- Support for LWIP network stack
- Support for AWS MQTT library
- Support for BSD and IoT sockets application programming interface(API)
Bluetooth Low Energy
- BLE central & peripheral connections are supported.
- Ultra-low power save is supported in Test Mode to support Tx/Rx performance testing
Power Save
- The power save profiles supported are Max PSP, enhanced MAX PSP, and 802.11ax TWT.
Changes and Fixes
Wi-Fi
- NCP support for brd4180b EFR
- Addition of featured examples wifi_aws_device_shadow_ncp, wifi_ble_per_ncp, wifi_firmware_update_ncp, wifi_powersave_standby_associated_ncp, wifi_wlan_throughput_ncp
- Addition of snippet examples wifi_access_point_ncp, wifi_concurrent_mode_ncp, wifi_select_app_ncp, wifi_station_ping_ncp, wifi_lwip_tcp_client_ncp, wifi_sntp_client_ncp
- Adds M4 power save support for wifi_station_ble_provisioning_aws
- Asynchronous select support using Si91x sockets APIs
- Added fixes for WLAN data transfer(TCP Tx/UDP Tx) failures while starting BLE Notification in wifi_throughput_ble_dual_role example
- Added fixes for socket bind failures in cli_demo while running in multiple iterations
- Added fixes for HTTP GET and HTTP POST when the application is run for multiple iterations
BLE
- Fixes compilation errors of ble_hid_on_gatt application when configured GATT_ROLE as CLIENT
- Added support for 352K_320K memory configuration in ble_central example application
System
- None
Recommendations
System
- The current revision of SiWx917 A0 has:
- RAM memory of 704k bytes which can be shared between TA and M4 processors in NCP/SoC mode. The following memory configuration modes are supported.
- EXT_FEAT_704K_M4SS_0K- This mode configures TA with 704k and M4 with 0K bytes of memory which is applicable only in the case of NCP mode
- The below configurations are applicable in SoC mode and can be configured based on the application requirement By Default EXT_FEAT_384K_M4SS_320K configuration will be selected in SoC mode
- EXT_FEAT_512K_M4SS_192K - This mode configures TA with 512k and M4 with 192K bytes of memory
- EXT_FEAT_448K_M4SS_256K - This mode configures TA with 448k and M4 with 256K bytes of memory
- EXT_FEAT_384K_M4SS_320K - This mode configures TA with 384k and M4 with 320K bytes of memory
- The currently supported memory configuration for NCP mode is 704K_M4SS_0K.
- SoC mode should not use 704k_M4SS_0k Memory configuration.
- In SoC mode, M4 power save will work with 384k TA and 320 M4 memory configuration only. It is not supported for "448K TA and 256k M4" and "512k TA and 192k M4" memory configurations.
- RAM memory of 704k bytes which can be shared between TA and M4 processors in NCP/SoC mode. The following memory configuration modes are supported.
- The current revision of SiWx917 B0 has:
- RAM memory of 672k bytes which can be shared between TA and M4 processors in NCP/SoC mode. The following memory configuration modes are supported.
- EXT_FEAT_672K_M4SS_0K- This mode configures TA with 672k and M4 with 0K bytes of memory which is applicable only in the case of NCP mode
- The below configurations are applicable in SoC mode and can be configured based on the application requirement By Default EXT_FEAT_352K_M4SS_320K configuration will be selected in SoC mode
- EXT_FEAT_480K_M4SS_192K - This mode configures TA with 480k and M4 with 192K bytes of memory
- EXT_FEAT_416K_M4SS_256K - This mode configures TA with 416k and M4 with 256K bytes of memory
- EXT_FEAT_352K_M4SS_320K - This mode configures TA with 352k and M4 with 320K bytes of memory
- The currently supported memory configuration for NCP mode is 672K_M4SS_0K.
- SoC mode should not use 672k_M4SS_0k Memory configuration.
- In SoC mode, M4 power save will work with any memory configuration.
- RAM memory of 672k bytes which can be shared between TA and M4 processors in NCP/SoC mode. The following memory configuration modes are supported.
- Set the recommended Power Save Profile (PSP) type to Enhanced Max PSP.
IDE
- Download the latest Simplicity Studio (SV5.7.0.1)
- Refer to the latest version of the SoC/NCP "Getting-Started-with-SiWx917" guide for more details
Wi-Fi
- It is recommended to enable bit 16 of the 'Extended TCP IP Feature' bit map in the opermode command for all Wi-Fi Socket Operations from the host to ensure graceful handling during asynchronous closures from the peer.
- Aggregation (bit 2 of feature_bit_map) is recommended to be enabled in opermode. This enables sw to aggregate multiple packets to achieve better throughput
- TCP retransmission count value is recommended to be 30 or higher so that the TCP does not disconnect while the rejoin happens.
- To restart the module, the application needs to call sl_wifi_deinit() followed by sl_wifi_init().
- 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.
- User can enable SL_SI91X_EXT_TCP_IP_SSL_16K_RECORD in 'Extended TCP IP Feature'bit map in opermode, if HTTPS download is failing after receiving HTTP headers..
- iTWT setup is recommended after IP assignment/TCP connection/application connection.
- When using sl_wifi_enable_target_wakeup_time API, increase TCP / ARP Timeouts at the remote side depending upon the configured TWT interval configured.
- In case of TWT+coex, when using sl_wifi_enable_target_wakeup_time API, use TWT wake duration <= 16 ms and TWT wake interval >= 1 sec. If wake duration > 16 ms or TWT wake interval < 1sec, there might be performance issues.
- For iTWT GTK Interval Should be kept max possible value or zero. If GTK interval is not configurable, recommended TWT interval (in case of sl_wifi_enable_target_wakeup_time API)
- Disable Power Save for High Throughput Applications.
- The application needs to ensure that it sets RTC with the 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 of less than 1 second is not currently supported.
- When sl_wifi_enable_target_wakeup_time API is used, configuring TWT Wake interval beyond 1 min might lead to disconnections from the AP. Recommended to use TWT wakeup interval of less than or equal to 1 min.
- MQTT keep alive interval should be either 0 or a value greater than 35 seconds.
- When using sl_wifi_enable_target_wakeup_time API, it is recommended to set missed_beacon_count of sl_wifi_set_advanced_client_configuration API greater than 2 times of the configured TWT Interval.
- Secure OTA: Keys need to be programmed before validating Secure OTA
BLE
- In BLE, recommended range of Connection Interval in
- Power Save (BLE Only) - 100 ms to 1.28 s.
- In BLE, during Connection, the configuration of Scan Interval and Scan Window with the same value is not recommended. The suggested ratio of Scan Window to Scan Interval is 3:4.
- In BLE, if a device is acting as Central, the scan window (in set_scan_params and create_connection commands) must be less than the existing Connection Interval. The suggested ratio of Scan Window to Connection Interval is 2:3.
- In BLE mode, if scanning and advertising are in progress on the SiWx91x module and it subsequently gets connected and moves to the central role, scanning stops else if it moves to the peripheral role, advertising stops. To further establish a connection to another peripheral device or to a central device, the application should give a command for starting advertising and scanning again.
Co-Existence
- For concurrent Wi-Fi + BLE, and while a Wi-Fi connection is active, we recommend setting the ratio of the BLE scan window to BLE scan interval to 1:3 or 1:4.
- Wi-Fi + BLE Advertising
- All standard advertising intervals are supported. As Wi-Fi throughput is increased, a slight difference in on-air advertisements compared to configured intervals may be observed.
- BLE advertising is skipped if the advertising interval collides with Wi-Fi activity.
- Wi-Fi + BLE scanning
- All standard scan intervals are supported. For better scan results, we recommend setting the ratio of the BLE scan window to BLE scan interval to 1:3 or 1:4.
- BLE scanning will be stopped for intervals that collide with Wi-Fi activity.
- Wi-Fi + BLE Central/Peripheral Connections
- All standard connection intervals are supported.
- 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 achieve higher throughput for both Wi-Fi and BLE, use medium connection intervals, such as 45 to 80 ms with maximum supervision timeout.
- Ensure Wi-Fi activity consumes lower intervals.
Known Issues
Network Stack
- Sometimes during SSL Handshake, ECC curve parameters generated are wrong, resulting in connection failure with BBD2 error. However, this recovers in the next attempt.
- Recommended MQTT Publish payload is 1 kBytes.
- 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.
Wi-Fi
- Device with active TWT will not go to sleep when the buffer is full.
- There are performance and IOP issues with MU MIMO.
- WPA3 connection takes 2.5 seconds.
- Issue observed with WPA2 Enterprise Connectivity using Microsoft RADIUS Server.
- EAP connection with certificates of 4096-bit key length is not supported.
- Low Wi-Fi+BLE throughput
- Data stall and disconnection with TCP Tx data transfer when TA power save is enabled
- TCP/UDP TX/RX Data stall observed in CoEx scenarios
- HTTPS Continuous download fails with TA Power save
- Low-performance metrics.
- Data stall when WLAN TCP data transfer, BLE scanning, BLE advertising, and BLE notification are enabled
BLE
- BLE Range is less with A0/B0 dual flash Radio boards when compared to A0/B0 common flash Radio boards.
- BLE applications hang after disconnection due to Disable Power save API failure
- Observing data stall with TCP Tx/Rx when connecting BLE With wifi_throughput_ble_dual_role application.
System
- None
MCU
- Refer the respective Radio board user guides for specific pinout details. Example readme's currently refer to A0 board versions
- IOSTREAM by default works only with 115200 baud rate. To work with different baud rates , undefine the USART_UC macro in sl_91x..usart.c.
- SSI bitrate above 10 Mbps is not working as expected.
- when using SL DMA, UDMA1 is not working as expected
- SIO-SPI few channels are not working as expected. (working of MOSI & MISO channel 4 and above is inconsistent)
- Few peripherals like WDT when configured with RO clock is not working as expected. No impact on the feature but the clocks are not accurate.
Limitations and Unsupported Features
Wi-Fi/Network Stack
- TLS 1.3 Server is not supported
- In AP mode, IPv6 Router Advertisements are not supported. Although STA connected to the APUT can transfer IPv6 data to the peers by using SLAAC for address configuration.
- When sl_wifi_enable_target_wakeup_time() API is used, observed occasional MQTT disconnections with longer TWT intervals (>30secs) with embedded MQTT + TWT.
- AMSDU TX is not supported.
- Fragmentation is not supported.
- AMSDUs 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 2.4 GHz band is not supported.
- 802.11J channel 14 is not supported.
- MQTT versions 3 and 4 are supported.
- Maximum of 3 SSL connections are supported in Wi-Fi alone mode.
- In SSL ECC Curve ID supported is 23. SSL handshake with 3rd party clients depends on the SSL ECC Curve ID.
- LP mode is not supported.
- Fine Tuning 802.11ax Spectral mask in Progress
- Fine Tuning 11b mask in Ch11 in progress
- In iTWT mode, downlink data traffic should be limited. Disconnections may be observed if AP fails to send all the buffered data in the next TWT Service Period.
- Number of MBSSIDs processed is limited by the beacon length that can be processed by the stack (which is limited to 1024 bytes). Beacons greater than 1024 Bytes in length will not be processed.
- In A0 SoC mode, M4 power save will work with 384k TA and 320 M4 memory configuration only. It is not supported for "448K TA and 256k M4" and "512k TA and 192k M4" memory configurations
- Timeout value should be a minimum 1 second for socket select and socket receive calls. Timeout value less than 1 second is not currently supported.
- M4 OTA update on dual flash will work for same flash sizes only (internal and External).
- CoEx + EAP Security in 352K/320k is not feasible. This issue is observed due to a lack of memory in the 352k/320k Memory Configuration. It is supported with other EXT_FEAT_416K_M4SS_256K and EXT_FEAT_480K_M4SS_192K memory configurations.
- UL MUMIMO is not supported.
- The embedded HTTP server is not supported.
- SNI is not supported
- Baremetal is not supported
BLE
- For BLE, if the connection is established with a small connection interval (less than 15 ms), simultaneous roles (i.e., Central + Scanning and Peripheral + Advertising) are not supported.
- BLE maximum two concurrent connections are supported, which can be either a connection to two peripheral devices, to one central and one peripheral device or two central devices.
- BLE Slave latency value is valid up to 32 only.
- BLE TX/RX throughput is less when tested with EFM as compared to EFR
- Maximum supported AE data length is 200 bytes.
- Supports only two ADV_EXT sets.
- Supports only two BLE connections( 1 Central and 1 Peripheral) with AE.
- Filtering policy is not supported for Periodic advertising.
MCU
- ULP Peripherals examples configurations are for RAM-based execution, as flash is powered off in ULP Mode
- On 4338a board, two I2C instances(I2C1 and I2C2) are using same GPIOs ,so support is not there for using two I2C instances simultaneously
- I2C Fast and High speed mode not supported
- when using GSPI and SSI, manual chip select option not supported
Simplicity Studio and Commander
- Default GDB debug configuration is not supported for SoC projects, work around details provided in "Getting-Started-with-SiWx917"
- Observing flash download failures(ERROR 108) for a few image sizes
- While creating project through Simplicity Studio, "copy contents" option not supported.
- Simplicity commander does not support options under "Debug Lock tools" .
Terminology
| Term | Description |
|---|---|
| New Features | These items are new to this release |
| Changes/Issues Fixed | Changes made to existing features found in previous software releases. |
| Enhancements to existing product flow and feature set. | |
| Bug fixes done in the Release | |
| Deprecated Items | Features or functions or APIs that are removed from the distributed release to align with the software roadmap |
| Known Issues | Features or functions that do not work as planned at the time of release. Workarounds may be offered to meet short-term development goals, but longer-term solutions will be added in future software releases |
| Limitations/Recommendations | Describes the limitations on product usage and recommendations for optimal use cases |
Note
- NA
This SDK package supports SoC Mode and NCP Mode for A0 and B0:
- In SoC Mode: Customer Applications can run on Cortex M4. Wireless, network, and security stacks run on the Wireless subsystem.
- In NCP mode: Wireless, network, and security stacks run on the Wireless subsystem. Customer applications run on the external host MCU.
- Silicon Labs' SiWx917 includes an ultra-low power Wi-Fi 6 plus Bluetooth Low Energy (BLE) 5.1 wireless subsystem and an integrated micro-controller application subsystem.
Note: Use Simplicity Studio version SV5.7.0.1 onwards
- Operating Modes : Wi-Fi STA (802.11ax, 802.11n), Wi-Fi 802.11n AP, Wi-Fi STA (802.11ax, 802.11n) + 802.11n AP, Wi-Fi STA (802.11ax, 802.11n) + BLE
- Wireless Protocols : IEEE 802.11b, 802.11g, 802.11n, 802.11ax, BLE 5.1
- Multiple Ultra Low Power Modes : Support Ultra low power Wi-Fi Standby associated current in Wi-Fi 4 mode, Ultra low power Wi-Fi Standby associated current in Wi-Fi 6 mode leveraging TWT, Always on Cloud connected power, BLE connected power, and, deep sleep ULP mode
- MCU examples : GPIO, I2C, Calendar, SPI, SSI, SIO, UDMA, UART/USART, WDT, Timers, Config Timers, ULP (Ultra Low Power) Timers, Sleeptimer, IOSTREAM, NVM3, MEMLCD.
- Wi-Fi : 2.4GHz Wi-Fi Support - WPA2/WPA3 Personal, Wi-Fi 6 OFDMA/MU-MIMO Support that enhances network capacity and reduces latency
- Cloud : Amazon Cloud Connectivity Support, Amazon FreeRTOS
- BLE : BLE 5.1, BLE dual role (Central and Peripheral Support)
- Integrated Stacks and Profiles : Wi-Fi Stack, BLE Stack, and Profiles, TCP/IP stack with TLS 1.3, HTTP/HTTPS, DHCP, MQTT Client, DNS client
- IDE : Simplicity Studio with Windows 10(64-bit), Linux, Mac OS
- TA/M4 Firmware Update Tool : Simplicity Commander
- Hardware kits to evaluate SoC Mode :
o Si-MB4002A Main board
o SiWx917 Radio boards
| RadioBoard Type | SiWx917A0 with Board Version | SiWx917B0 with Board Version |
|---|---|---|
| Common flash | Si917-BRD4325A(1.0 /1.1 /1.2) | - |
| Common flash | - | Si917-BRD4338A(2.0) |
| Dual flash | Si917-BRD4325B(1.0 /1.1 /1.2) | - |
| Item | Details |
|---|---|
| Release date | Aug 10th, 2023 |
| SDK Version | 3.0.12 |
| Firmware Version | 1711.2.9.0.0.19 |
| Package Name | WiSeConnect3_SDK_3.0.12 |
| Supported RTOS | FreeRTOS |
| Operating Modes Supported | Wi-Fi STA, Wi-Fi AP, Wi-Fi STA+BLE, Wi-Fi STA+AP |
| Build Quality | Beta |
- SiWx917 release consists of two components
- Wireless Firmware - SiWx917 Firmware Binaries
- Wiseconnect3 Library - Wiseconnect3 SDK Library runs on internal Cortex M4 in SoC Mode.
- This release is meant only for use with designs based on SiWx917 Silicon
- The firmware to load in your design are available in the following format:
- SiWG917-A.2.9.0.0.x.rps - A0 Full-featured firmware binary
- SiWG917-B.2.9.0.0.x.rps - B0 Full-featured firmware binary
MCU
- ADC Single Channel, ADC Static Mode, Analog Comparator, Blinky, Bod, CTS, DAC FIFO, DAC Static, GPIO, I2C, I2S, NVM3, OPAMP, PSRAM, PWM, QEI, RTC, SDIO Slave, SPI Master and Slave, UART, UDMA, USART, WDT, USART Master and Slave
- UC Supported Peripherals - GPIO, I2C, Calendar, SPI, SSI, SIO, UDMA, UART/USART, WDT, Timers , Config Timers, ULP (Ultra Low Power) Timers, Sleeptimer, IOSTREAM, MEMLCD
- ULP (Ultra Low Power) Peripherals - ulp_gpio, ulp_adc ulp_i2c, ulp_i2s, ulp_ir_decoder, ulp_spi, ulp_timer, ulp_uart, ulp_udma
Wi-Fi
- WPA2/WPA3 Personal, WPS and WPA2-EAP Support for Station Mode
- TCP/IP stack with IPv4, IPv6, TCP, UDP, TLS, HTTP/HTTPS, DHCPv4, DHCPv6, MQTT Client, DNS Client, SNTP client.
- Support for SSL client versions TLSV1.0, TLSV1.2, TLSV1.3 and SSL server versions TLSV1.0 and TLSV1.2
- Wi-Fi STA (802.11n/802.11ax) + 802.11n AP Support
- HE (802.11ax) and Individual TWT Feature Support
- Multiple BSSID feature support as an STA
- Secure OTA support on B0 radio boards.
- Support for LWIP network stack
- Support for AWS MQTT library
- Support for BSD and IoT sockets application programming interface(API)
Bluetooth Low Energy
- BLE central & peripheral connections are supported.
- Ultra-low power save is supported in Test Mode to support Tx/Rx performance testing
Power Save
- The powersave profiles supported are Max PSP, enhanced MAX PSP, and 802.11ax TWT.
MCU
- Added project support for 1.2 dual flash and 2.0 boards
- SIO related bug fixes reported on SIO-USART and SIO-SPI
- Updated Readme files to provide pin configuration details
- WDT Example related bug fix
Wi-Fi
- TWT power number improvements.
- Added support for Si91X asynchronous sockets
- Added support for SNTP documentation
- Updated documentation for SL_SI91X_EXT_FEAT_XTAL_CLK_ENABLE
- Replacement of convert_string_to_sl_ipv4_address() with sl_net_inet_addr()
- Updation of sl_net_interface_t enums
- Added Frontend switch selection in SRM
- Added timeout fixes for RF test example
- Added fixes related to socket bind
- Bug fixes HTTP/HTTPS file download in COEX mode
- M4 soft reset support in http_otaf example
- Bug fixes related to certificate loading in COEX mode
- Bug fixes related to BLE connection in powersave mode
- Application bug fixes in wifi_wlan_throughput_v6, ble_multiconnection_gatt example
- Bug fixes related to Wi-Fi rejoins in powersave mode
- Stability fixes for M4 sleep
- Support to SiWx917B0 2.0 radio boards
- Support for Wi-Fi transmission rate for the given 802.11b, 802.11g, and 802.11n protocols.
- Renaming of access_point, concurrent_mode, aws_mqtt, powersave_standby_associated, select_app, station_ping, lwip_tcp_client, sntp_client application with _soc suffix
- Fixes MQTT username and password length checks in requests and asynchronous MQTT requests handling
- Support for functional OFDMA DL/UL.
BLE
- Fixes application timeouts in the ble_throughput application
- Support to BLE PER mode
System
- None
System
- The current revision of SiWx917 A0 has:
- RAM memory of 704k bytes which can be shared between TA and M4 processors in NCP/SoC mode. The following memory configuration modes are supported.
- EXT_FEAT_704K_M4SS_0K- This mode configures TA with 704k and M4 with 0K bytes of memory which is applicable only in the case of NCP mode
- The below configurations are applicable in SoC mode and can be configured based on the application requirement By Default EXT_FEAT_384K_M4SS_320K configuration will be selected in SoC mode
- EXT_FEAT_512K_M4SS_192K - This mode configures TA with 512k and M4 with 192K bytes of memory
- EXT_FEAT_448K_M4SS_256K - This mode configures TA with 448k and M4 with 256K bytes of memory
- EXT_FEAT_384K_M4SS_320K - This mode configures TA with 384k and M4 with 320K bytes of memory
- The currently supported memory configuration for NCP mode is 704K_M4SS_0K.
- SoC mode should not use 704k_M4SS_0k Memory configuration.
- In SoC mode, M4 power save will work with 384k TA and 320 M4 memory configuration only. It is not supported for "448K TA and 256k M4" and "512k TA and 192k M4" memory configurations.
- RAM memory of 704k bytes which can be shared between TA and M4 processors in NCP/SoC mode. The following memory configuration modes are supported.
- The current revision of SiWx917 B0 has:
- RAM memory of 672k bytes which can be shared between TA and M4 processors in NCP/SoC mode. The following memory configuration modes are supported.
- EXT_FEAT_672K_M4SS_0K- This mode configures TA with 672k and M4 with 0K bytes of memory which is applicable only in the case of NCP mode
- The below configurations are applicable in SoC mode and can be configured based on the application requirement By Default EXT_FEAT_352K_M4SS_320K configuration will be selected in SoC mode
- EXT_FEAT_480K_M4SS_192K - This mode configures TA with 480k and M4 with 192K bytes of memory
- EXT_FEAT_416K_M4SS_256K - This mode configures TA with 416k and M4 with 256K bytes of memory
- EXT_FEAT_352K_M4SS_320K - This mode configures TA with 352k and M4 with 320K bytes of memory
- The currently supported memory configuration for NCP mode is 672K_M4SS_0K.
- SoC mode should not use 672k_M4SS_0k Memory configuration.
- In SoC mode, M4 power save will work with any memory configuration.
- RAM memory of 672k bytes which can be shared between TA and M4 processors in NCP/SoC mode. The following memory configuration modes are supported.
- Set the recommended Power Save Profile (PSP) type to Enhanced Max PSP.
IDE
- Download the latest Simplicity Studio (SV5.7.0.1)
- Refer to the latest version of the SoC "Getting-Started-with-SiWx917" guide for more details
Wi-Fi
- It is recommended to enable bit 16 of the 'Extended TCP IP Feature' bit map in the opermode command for all Wi-Fi Socket Operations from the host to ensure graceful handling during asynchronous closures from the peer.
- Aggregation (bit 2 of feature_bit_map) is recommended to be enabled in opermode. This enables sw to aggregate multiple packets to achieve better throughput
- TCP retransmission count value is recommended to be 30 or higher so that the TCP does not disconnect while the rejoin happens.
- To restart the module, the application needs to call sl_wifi_deinit() followed by sl_wifi_init().
- 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.
- User can enable SL_SI91X_EXT_TCP_IP_SSL_16K_RECORD in 'Extended TCP IP Feature'bit map in opermode, if HTTPS download is failing after receiving HTTP headers..
- iTWT setup is recommended after IP assignment/TCP connection/application connection.
- When using sl_wifi_enable_target_wakeup_time API, increase TCP / ARP Timeouts at the remote side depending upon the configured TWT interval configured.
- In case of TWT+coex, when using sl_wifi_enable_target_wakeup_time API, use TWT wake duration <= 16 ms and TWT wake interval >= 1 sec. If wake duration > 16 ms or TWT wake interval < 1sec, there might be performance issues.
- For iTWT GTK Interval Should be kept max possible value or zero. If GTK interval is not configurable, recommended TWT interval (in case of sl_wifi_enable_target_wakeup_time API)
- Disable Power Save for High Throughput Applications.
- The application needs to ensure that it sets RTC with the 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 of less than 1 second is not currently supported.
- When sl_wifi_enable_target_wakeup_time API is used, configuring TWT Wake interval beyond 1 min might lead to disconnections from the AP. Recommended to use TWT wakeup interval of less than or equal to 1 min.
- MQTT keep alive interval should be either 0 or a value greater than 35 seconds.
- When using sl_wifi_enable_target_wakeup_time API, it is recommended to set missed_beacon_count of sl_wifi_set_advanced_client_configuration API greater than 2 times of the configured TWT Interval.
- Secure OTA: Keys need to be programmed before validating Secure OTA
BLE
- In BLE, recommended range of Connection Interval in
- Power Save (BLE Only) - 100 ms to 1.28 s.
- In BLE, during Connection, the configuration of Scan Interval and Scan Window with the same value is not recommended. The suggested ratio of Scan Window to Scan Interval is 3:4.
- In BLE, if a device is acting as Central, the scan window (in set_scan_params and create_connection commands) must be less than the existing Connection Interval. The suggested ratio of Scan Window to Connection Interval is 2:3.
- In BLE mode, if scanning and advertising are in progress on the SiWx91x module and it subsequently gets connected and moves to the central role, scanning stops else if it moves to the peripheral role, advertising stops. To further establish a connection to another peripheral device or to a central device, the application should give a command for starting advertising and scanning again.
Co-Existence
- For concurrent Wi-Fi + BLE, and while a Wi-Fi connection is active, we recommend setting the ratio of the BLE scan window to BLE scan interval to 1:3 or 1:4.
- Wi-Fi + BLE Advertising
- All standard advertising intervals are supported. As Wi-Fi throughput is increased, a slight difference in on-air advertisements compared to configured intervals may be observed.
- BLE advertising is skipped if the advertising interval collides with Wi-Fi activity.
- Wi-Fi + BLE scanning
- All standard scan intervals are supported. For better scan results, we recommend setting the ratio of the BLE scan window to BLE scan interval to 1:3 or 1:4.
- BLE scanning will be stopped for intervals that collide with Wi-Fi activity.
- Wi-Fi + BLE Central/Peripheral Connections
- All standard connection intervals are supported.
- 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 achieve higher throughput for both Wi-Fi and BLE, use medium connection intervals, such as 45 to 80 ms with maximum supervision timeout.
- Ensure Wi-Fi activity consumes lower intervals.
Network Stack
- Sometimes during SSL Handshake, ECC curve parameters generated are wrong, resulting in connection failure with BBD2 error. However, this recovers in the next attempt.
- Recommended MQTT Publish payload is 1 kBytes.
- 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.
Wi-Fi
- Device with active TWT will not go to sleep when the buffer is full.
- There are performance and IOP issues with MU MIMO.
- WPA3 connection takes 2.5 seconds.
- Issue observed with WPA2 Enterprise Connectivity using Microsoft RADIUS Server.
- EAP connection with certificates of 4096-bit key length is not supported.
- Low Wi-Fi+BLE throughput
- Data stall and disconnection with TCP Tx data transfer when TA power save is enabled
- TCP/UDP TX/RX Data stall observed in CoEx scenarios
- HTTPS Continuous download fails with TA Power save
- HTTP get and post are not working from the second iteration i.e., upon WLAN reconnection
- Low-performance metrics.
BLE
- BLE Range is less with A0/B0 dual flash Radio boards when compared to A0/B0 common flash Radio boards.
- Wireless Init failure observed in BLE Central application with (352k,320k) configuration
- BLE applications hang after disconnection due to Disable Power save API failure
System
- None
- Refer the respective Radio board user guides for specific pinout details. Example readme's currently refer to A0 board versions
- IOSTREAM by default works only with 115200 baud rate. To work with different baud rates , undefine the USART_UC macro in sl_91x..usart.c.
- SSI bitrate above 10 Mbps is not working as expected.
- when using SL DMA, UDMA1 is not working as expected
- SIO-SPI few channels are not working as expected. (working of MOSI & MISO channel 4 and above is inconsistent)
- Few peripherals like WDT when configured with RO clock is not working as expected. No impact on the feature but the clocks are not accurate.
Wi-Fi/Network Stack
- TLS 1.3 Server is not supported
- In AP mode, IPv6 Router Advertisements are not supported. Although STA connected to the APUT can transfer IPv6 data to the peers by using SLAAC for address configuration.
- When sl_wifi_enable_target_wakeup_time() API is used, observed occasional MQTT disconnections with longer TWT intervals (>30secs) with embedded MQTT + TWT.
- AMSDU TX is not supported.
- Fragmentation is not supported.
- AMSDUs 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 2.4 GHz band is not supported.
- 802.11J channel 14 is not supported.
- MQTT versions 3 and 4 are supported.
- Maximum of 3 SSL connections are supported in Wi-Fi alone mode.
- In SSL ECC Curve ID supported is 23. SSL handshake with 3rd party clients depends on the SSL ECC Curve ID.
- LP mode is not supported.
- Fine Tuning 802.11ax Spectral mask in Progress
- Fine Tuning 11b mask in Ch11 in progress
- In iTWT mode, downlink data traffic should be limited. Disconnections may be observed if AP fails to send all the buffered data in the next TWT Service Period.
- Number of MBSSIDs processed is limited by the beacon length that can be processed by the stack (which is limited to 1024 bytes). Beacons greater than 1024 Bytes in length will not be processed.
- In A0 SoC mode, M4 power save will work with 384k TA and 320 M4 memory configuration only. It is not supported for "448K TA and 256k M4" and "512k TA and 192k M4" memory configurations
- Timeout value should be a minimum 1 second for socket select and socket receive calls. Timeout value less than 1 second is not currently supported.
- M4 OTA update on dual flash will work for same flash sizes only (internal and External).
- CoEx + EAP Security in 352K/320k is not feasible. This issue is observed due to a lack of memory in the 352k/320k Memory Configuration. It is supported with other EXT_FEAT_416K_M4SS_256K and EXT_FEAT_480K_M4SS_192K memory configurations.
- UL MUMIMO is not supported.
- The embedded HTTP server is not supported.
- SNI is not supported
- Baremetal is not supported
BLE
- For BLE, if the connection is established with a small connection interval (less than 15 ms), simultaneous roles (i.e., Central + Scanning and Peripheral + Advertising) are not supported.
- BLE maximum two concurrent connections are supported, which can be either a connection to two peripheral devices, to one central and one peripheral device or two central devices.
- BLE Slave latency value is valid up to 32 only.
- BLE TX/RX throughput is less when tested with EFM as compared to EFR
- Maximum supported AE data length is 200 bytes.
- Supports only two ADV_EXT sets.
- Supports only two BLE connections( 1 Central and 1 Peripheral) with AE.
- Filtering policy is not supported for Periodic advertising.
MCU
- ULP Peripherals examples configurations are for RAM-based execution, as flash is powered off in ULP Mode
- On 4338a board, two I2C instances(I2C1 and I2C2) are using same GPIOs ,so support is not there for using two I2C instances simultaneously
- I2C Fast and High speed mode not supported
- when using GSPI and SSI, manual chip select option not supported
Simplicity Studio and Commander
- Default GDB debug configuration is not supported for SoC projects, work around details provided in "Getting-Started-with-SiWx917"
- Observing flash download failures(ERROR 108) for a few image sizes
- While creating project through Simplicity Studio, "copy contents" option not supported.
- Simplicity commander does not support options under "Debug Lock tools" .
| Term | Description |
|---|---|
| New Features | These items are new to this release |
| Changes/Issues Fixed | Changes made to existing features found in previous software releases. |
| Enhancements to existing product flow and feature set. | |
| Bug fixes done in the Release | |
| Deprecated Items | Features or functions or APIs that are removed from the distributed release to align with the software roadmap |
| Known Issues | Features or functions that do not work as planned at the time of release. Workarounds may be offered to meet short-term development goals, but longer-term solutions will be added in future software releases |
| Limitations/Recommendations | Describes the limitations on product usage and recommendations for optimal use cases |
- NA
This SDK package supports SoC Mode only.
- In SoC Mode: Customer Applications can run on Cortex M4 and Wireless stacks, Networking stacks run on the Wireless subsystem.
- Silicon Labs SiWx917 includes an ultra-low power Wi-Fi 6 plus Bluetooth Low Energy (BLE) 5.4 wireless subsystem and an integrated micro-controller application subsystem.
Note: The release supports only Simplicity Studio 5.7 & above versions.
- Operating Modes: Wi-Fi STA, Wi-Fi AP, Concurrent (AP + STA), Wi-Fi STA+BLE (CoEx)
- Wireless Protocols: IEEE 802.11b, 802.11g, 802.11n, 802.11ax, BLE 5.4
- MCU Peripherals: ADC Static Mode, Analog Comparator, Bod, CTS, DAC FIFO, DAC Static, OPAMP, GPIO, I2C, I2S, PWM, RTC, QEI, SPI, UART, USART, UDMA, WDT
- ULP (Ultra Low Power) Peripherals: ulp_gpio, ulp_i2c, ulp_i2s, ulp_ir_decoder, ulp_spi, ulp_timer, ulp_uart, ulp_udma
- UART and I2C Deep Sleep Wakeup Without RAM Retention
- Multiple Ultra Low Power Modes: Wi-Fi 6 TWT (Target Wake Time) - for improved network efficiency and device battery life
- Wi-Fi: 2.4GHz Wi-Fi Support - WPA2/WPA3 Personal, Wi-Fi 6 OFDMA/MU-MIMO Support that enhances network capacity and latency
- Cloud: Amazon Cloud Connectivity Support
- BLE: BLE 5.4, BLE dual role (Central and Peripheral Support)
- Integrated Stacks and Profiles: Wi-Fi Stack, BLE Stack and Profiles, TCP/IP stack with TLS 1.3, HTTP/HTTPS, DHCP, MQTT Client, SNTP Client, DNS Client
- IDE: Simplicity Studio with Windows 10 (64-bit), Linux, MacOS
- TA/M4 Firmware Update Tool: Simplicity Commander
- Hardware kits to evaluate SoC Mode: Si917-BRD4325A (Common Flash Radio board), Si917-BRD4325B (Dual Flash Radio board), Si917-BRD4325G (Common Flash Radio board + extended PSRAM)
| Item | Details |
|---|---|
| Release date | July 27th, 2023 |
| SDK Version | 3.0.10(Build 1) |
| Firmware Version | 2.9.0.0.15 |
| Package Name | WiSeConnect3_SDK_3.0.10 |
| Supported RTOS | FreeRTOS |
| Operating Modes Supported | Wi-Fi STA, Wi-Fi AP, Concurrent(AP + STA), Wi-Fi STA+BLE(CoEx) |
| Build Quality | pre-beta |
This release includes the Wireless Library, which operates on the internal Cortex M4 in SoC Mode.
- Added support for command line interface application (cli_demo).
- IOSTREAM support has been integrated into GSDK 4.3.1.
- I2C High-Speed mode is not working as expected.
- SSI bitrate above 10 Mbps is not working as expected.
- DUT is getting hanged while continuously publishing data in the embedded MQTT application during power save mode.
- BLE notification and Continuous BG scan are not working as expected.
- BLE radio's range of 4-5m for BRD4325B A02 boards, .
- Intermittent Bus thread hang issue with LWIP external stack.
- The "Browser File Viewer" plugin has issues. It can't render the last image included in the markdown files and has observed issues accessing some hyperlinks.
- Known issues in ble per and wlan rf features
- Data rates are not effecting on the dut with 11b, 11g, 11n modes.
- BLE connection is not happening when power save is enabled in BLE-Central application
- In SoC mode, M4 power save will only work with the 384k TA and 320 M4 memory configuration. It is not supported for "448K TA and 256k M4" and "512k TA and 192k M4" memory configurations.
- WPA3 connection takes 2.5 seconds more than WPA2 connection.
- An issue has been observed with WPA2 Enterprise Connectivity using Microsoft RADIUS Server.
- 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.
- LMP timeout BLE disconnection has been observed with the latest Realme mobile handsets.
- Throughput is not on par with WiSeConnect 2 in the present release.
- A maximum of 3 SSL connections is supported in WiFi alone mode.
- TWT is not verified in Coex mode.
- BGscan is not verified with the TWT feature.
- SIO currently supports SPI and UART.
- Peripherals currently use UDMA CMSIS driver.
- For BLE, simultaneous roles (i.e., Central + Scanning and Peripheral + Advertising) are not supported if the connection is established with a small connection interval (less than 15 ms).
- BLE supports a maximum of two concurrent connections, which can be either a connection to two peripheral devices, one central and one peripheral device, or two central devices.
- The BLE Slave latency value is valid up to 32 only.
- SNI (HTTPS, TLS/SSL).
- Keep Alive configurability.
- Console application for customers.
- Multi-threaded APIs.
- 917-specific features (debugging utilities).
- APIs for Crypto Hardware (ECDH, DH, SHA, AES), Calibration software & stats.
- SoC Support (Hosted mode): support for switching between internal & external stack in SS.
- Protocols Offload mode: HTTP Server (917 specific), DHCPv6 Server, SNMP, Socket reads up to 64k, POP3, DTLS, mDNS, Web Socket, DNS Server.
- Power save support (Message-based).
- PTA Coexistence with other wireless.
- Baremetal support.
- Asynchronous socket APIs.
- NCP support (SPI, SDIO, UART, Linux, 3rd-party hosts).
| Term | Description |
|---|---|
| New Features | These items are new to this release |
| Changes/Issues Fixed | Changes made to existing features found in previous software releases. |
| Enhancements to existing product flow and feature set. | |
| Bug fixes done in the Release | |
| Deprecated Items | Features or functions or APIs that are removed from the distributed release to align with the software roadmap |
| Known Issues | Features or functions that do not work as planned at the time of release. Workarounds may be offered to meet short-term development goals, but longer-term solutions will be added in future software releases |
| Limitations/Recommendations | Describes the limitations on product usage and recommendations for optimal use cases |
This SDK package supports SoC Mode only.
- In SoC Mode: Customer Applications can run on Cortex M4 and Wireless stacks and Networking stacks run on the Wireless subsystem.
- Silicon Labs SiWx917 includes an ultra-low power Wi-Fi 6 plus Bluetooth Low Energy (BLE) 5.1 wireless subsystem and an integrated micro-controller application subsystem.
Note: To run the application, please install the GSDK patch following the instructions below:
- Install GSDK version 4.3.0.
- Open your terminal application.
- Go to your GSDK path and enter the following command: git apply --ignore-whitespace --ignore-space-change "extension/wiseconnect3/utilities/gsdk_service_patch/gsdk_service.patch"
Note: The
git applycommand needs to be run to apply a GSDK patch not available with the current WiSeConnect 3 release.
- Now you should be able to build and run Dx sample applications.
Note: The release supports only Simplicity Studio 5.7 & above versions.
- Operating Modes: Wi-Fi STA, Wi-Fi AP, Concurrent (AP + STA), Wi-Fi STA+BLE (CoEx)
- Wireless Protocols: IEEE 802.11b, 802.11g, 802.11n, 802.11ax, BLE 5.1
- MCU Peripherals: ADC Static Mode, Analog Comparator, Blinky, Bod, CTS, DAC FIFO, DAC Static, OPAMP, GPIO, I2C, I2S, PWM, RTC, QEI, SPI, UART, USART, UDMA, WDT, Combined Peripheral App
- ULP (Ultra Low Power) Peripherals: ulp_gpio, ulp_i2c, ulp_i2s, ulp_ir_decoder, ulp_spi, ulp_timer, ulp_uart, ulp_udma
- UART and I2C Deep Sleep Wakeup Without RAM Retention
- Multiple Ultra Low Power Modes: Wi-Fi 6 TWT (Target Wake Time) - for improved network efficiency and device battery life
- Wi-Fi: 2.4GHz Wi-Fi Support - WPA2/WPA3 Personal, Wi-Fi 6 OFDMA/MU-MIMO Support that enhances network capacity and latency
- Cloud: Amazon Cloud Connectivity Support
- BLE: BLE 5.1, BLE dual role (Central and Peripheral Support)
- Integrated Stacks and Profiles: Wi-Fi Stack, BLE Stack and Profiles, TCP/IP stack with TLS 1.3, HTTP/HTTPS, DHCP, MQTT Client, SNTP Client
- IDE: Simplicity Studio with Windows 10 (64-bit)
- TA/M4 Firmware Update Tool: Simplicity Commander
- Hardware kits to evaluate SoC Mode: Si917-BRD4325A (Common flash Radio board), Si917-BRD4325B (Dual flash Radio board), Si917-BRD4325G (Common Flash Radio board + extended PSRAM)
| Item | Details |
|---|---|
| Release date | July 10th, 2023 |
| API Version | 3.0.9(Build 1) |
| Firmware Version | 2.9.0.0.8 |
| Package Name | WiSeConnect3_SDK_3.0.9 |
| Supported RTOS | FreeRTOS |
| Operating Modes Supported | Wi-Fi STA, Wi-Fi AP, Concurrent(AP + STA), Wi-Fi STA+BLE(CoEx) |
This release includes the Wireless Library, which operates on the internal Cortex M4 in SoC Mode.
- Supported DX Peripherals: Calendar, ULP Timer, GSPI, SSI, GPIO, I2C, Watchdog Timer, DMA, USART, Config Timer, SIO.
- Supported Services: Sleeptimer, IOStream, NVM3.
- Added support for IPv6.
- Added support for FreeRTOS.
- Added support for LWIP stack.
- Added support for AWS MQTT library.
- Added support for EAP-FAST and EAP-PEAP.
- Added support for 802.11ax protocol & TWT.
- Added support for TCP, UDP, TLS/SSL sockets.
- Added support for TA & M4 Powersave profiles.
- Added Support for Common & dual Flash radio boards.
- Added support for multi-threaded application development.
- Added support for WPA2/WPA3 Personal, Enterprise security in station Mode.
- Added support for BSD and IoT socket application programming interface (API).
- Added support for Network Application protocol for Offloaded mode (TCP/IP internal stack) with HTTP/HTTPS, DHCP, MQTT Client, DNS Client, SNTP Client.
- Added support for Bluetooth Low Energy (BLE) central & peripheral connections.
- Added support for Wireless firmware upgradation (OTA).
- Added support for Platform-agnostic Wi-Fi, Network APIs.
- Added API documentation, migration guide, Getting Started Guide.
- B0 (V2.0) support will be provided in subsequent releases.
- I2C High-Speed mode is not working as expected.
- SSI bitrate above 10 Msps is not working as expected.
- Powersave Deepsleep is not working as expected on Common Flash B0 Board.
- DUT is getting hanged while continuously publishing data in the embedded MQTT application during power save mode.
- BLE notification and Continuous BG scan are not working as expected.
- Ongoing efforts to update the readme file are in progress.
- The "Browser File Viewer" plugin has issues. It can't render the last image included in the markdown files and has observed issues accessing some hyperlinks.
- In SoC mode, M4 power save will only work with the 384k TA and 320 M4 memory configuration. It is not supported for "448K TA and 256k M4" and "512k TA and 192k M4" memory configurations.
- WPA3 connection takes 2.5 seconds more than WPA2 connection.
- An issue has been observed with WPA2 Enterprise Connectivity using Microsoft RADIUS Server.
- 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.
- LMP timeout BLE disconnection has been observed with the latest Realme mobile handsets.
- Throughput is not on par with WiSeConnect 2 in the present release.
- A maximum of 3 SSL connections is supported in WiFi alone mode.
- TWT is not verified in Coex mode.
- BGscan is not verified with the TWT feature.
- SIO currently supports SPI and UART.
- Peripherals currently use UDMA CMSIS driver.
- For BLE, simultaneous roles (i.e., Central + Scanning and Peripheral + Advertising) are not supported if the connection is established with a small connection interval (less than 15 ms).
- BLE supports a maximum of two concurrent connections, which can be either a connection to two peripheral devices, one central and one peripheral device, or two central devices.
- The BLE Slave latency value is valid up to 32 only.
- SNI (HTTPS, TLS/SSL).
- Keep Alive configurability.
- Console application for customers.
- Multi-threading support for relevant APIs.
- 917-specific features (debugging utilities).
- APIs for Crypto Hardware (ECDH, DH, SHA, AES), Calibration software & stats.
- SoC Support (Hosted mode): support for switching between internal & external stack in SS.
- Protocols Offload mode: HTTP Server (917 specific), DHCPv6 Server, SNMP, Socket reads up to 64k, POP3, DTLS, mDNS, Web Socket, DNS Server.
- Power save support (Message-based).
- PTA Coexistence with other wireless.
- Baremetal support.
- Asynchronous socket APIs.
- NCP support (SPI, SDIO, UART, Linux, 3rd-party hosts).
| Term | Description |
|---|---|
| New Features | These items are new to this release |
| Changes/Issues Fixed | Changes made to existing features found in previous software releases. |
| Enhancements to existing product flow and feature set. | |
| Bug fixes done in the Release | |
| Deprecated Items | Features or functions or APIs that are removed from the distributed release to align with the software roadmap |
| Known Issues | Features or functions that do not work as planned at the time of release. Workarounds may be offered to meet short-term development goals, but longer-term solutions will be added in future software releases |
| Limitations/Recommendations | Describes the limitations on product usage and recommendations for optimal use cases |