QNX Technical Articles
QNX® Software Development Platform 7.1 Networking io-pkt WiFi BCM-4339 Drivers and Supplicant (Build 1155): Release Notes
Date of this edition: November 18, 2021
Target OS: This update is compatible with targets that are running QNX® Neutrino® 7.1.
Host OS: To install this update, you must have installed the QNX Software Development Platform 7.1 on one of the following development hosts:
- Microsoft Windows 10 Pro 64-bit, or Windows 8.1 Pro 64-bit
- macOS version 10.14, or 10.15
- Linux Red Hat Enterprise Linux 7 64-bit, or Ubuntu Desktop 18.04 LTS 64-bit, on x86_64 processors (QNX SDP isn't supported on Linux on ARM processors)
Contents
Throughout this document, you may see reference numbers associated with particular issues, changes, etc. When corresponding with our Technical Support staff about a given issue, please quote the relevant reference number. You might also find the reference numbers useful for tracking issues as they become fixed.
What's in this update?
This update includes the following packages found in the Updates or Available tab under QNX Software Development Platform -> Networking:
| Name | Package | Build ID | Content |
|---|---|---|---|
| QNX SDP 7.1 Networking - Wireless driver for the Cypress SDIO based wifi module (wpa-2.9) | com.qnx.qnx710.target.driver.broadcom_bcm4339_0.0.4.01155T202109031257L | 1155 | See "Fixed Issues" |
| QNX SDP 7.1 Networking - WPA/WPA2/IEEE 802.1X Supplicant | com.qnx.qnx710.target.net.wpa_supplicant_0.0.4.01155T202109031257L | 1155 | See "Fixed Issues" |
To see a list of the contents of a package, right-click it in the QNX Software Center, choose Properties, and then click Package Contents.
Fixed issues
We’ve added support for the following SDIO wireless driver: BCM4339 driver (a generic Cypress SDIO based wifi driver) for Raspberry Pi 4. (Ref# 2893710)
- The wireless driver devnp-qwdi-2.9_bcm4339-rpi4.so now has a recognizable interface media type. Previously it was showing an unknown type. (Ref# 2902932)
- The wireless driver devnp-qwdi-2.9_bcm4339-rpi4.so no longer fails to connect with WPA2-EAP. (Ref# 2902963)
- Telnet no longer locks when sending a disconnect or remove_network command to an internal supplicant with driver devnp-qwdi-2.9_bcm4339-rpi4.so. External supplicants were not affected. (Ref# 2902982)
- If the AGO interface was not successfully removed, it stopped the transition to setting up another wireless mode (for example, AP mode). We’ve updated the remove sequence to fix this issue. (Ref# 2903979)
- We’ve fixed an issue that caused a certain customer board to fail because it was mounting the wireless driver a second time after the shutdown command was sent. (Ref# 2904014)
- We’ve fixed a issue with low throughput by optimizing interrupt handling and correcting the setting of SDIO clock. (Ref# 2904382).
- We’ve fixed an io-pkt core dump issue that could happen when sending/receiving data, if the memory buffer size exceeded the allowed size. (Ref# 2904384)
- We’ve removed module-specific NVRAM and blob files from our shiplist. (Ref# 2905036)
- The station (STA) target was not re-associating to an external access point (AP) when the AP disconnected the STA (or the AP was slayed). We’ve fixed this behaviour so that the target will successfully re-associate to the AP, and a subsequent ping will find it. (Ref# 2905204)
- We’ve added a mount option to disable the SDIO bus sleep feature (by default) for CYW89373 and Raspberry Pi 4 because they don’t work well with the sleep and wakeup features enabled. (Ref# J2905679)
We’ve added support for the driver internal supplicant for BCM34355 WPA3. (Ref# 2898385)
- The wpa_supplicant-2.9 utility no longer mishandles a PSK key value in a way that could result in authentication failure. We’ve fixed the issue that occurred when the PSK key value contained 0x00 bytes. (Ref# 2903820)
- We’ve updated the information that the use command provides for the wpa_supplicant-2.9 utility. (Ref# 2902882)
- We’ve update the hostapd_cli status command on the access point to display the frequency after the initial setup. (Ref# 2902316)
- If you're using hostapd-2.9, you might notice a change to the way its command-line interface reports status after a channel switch. (The channel number matches the external AP that the STA connected with.) (Ref# 2900198)
Known issues
None currently known.
Technical support
For information about technical support for any QNX product, go to the Developers menu on our website (www.qnx.com). You'll find a wide range of support options, including community forums.