Sona™ IF573 - WiFi 6E + Bluetooth® 5.4 Module

There was a change in kernel 5.19 and higher, lrd-11 is built against the kernel 6.1 kernel backports), where there is a requirement to add cfg80211 to your image as a module (m) in the base platform kernel configuration. It must not be left out and must not be included as built-in (y). Networking support->Wireless->cfg80211 - wireless configuration API

Do I need to do anything differently in lrd-11 release?

There was a change in kernel 5.19 and higher, lrd-11 is built against the kernel 6.1 kernel backports), where there is a requirement to add cfg80211 to your image as a module (m) in the base platform kernel configuration. It must not be left out and must not be included as built-in (y).

• Networking support->Wireless->cfg80211 - wireless configuration API

I am seeing an error: error: 'struct net_device' has no member named 'ieee80211_ptr' while trying to build the lrd-11.0 release in Yocto.

This is due to a change in kernel 5.19 and higher, (lrd-11.0 is built against 6.1 kernel backports), where there is a requirement to add cfg80211 to your image.

To accomplish this:

1. Edit your kernel configuration by entering bitbake -c menuconfig virtual/kernel
2. Edit Networking support/Wireless and set cfg80211 to "M" for module
3. Save your changes.
4. Run your build again.

No. The creation of 6GHz soft APs is not supported due to the complexity of regulations and testing for APs in the 6GHz band.

Yes, it's mandatory to do this. 

While you design IF573 PCB module, need to have a GPIO to control BT_REG_ON; with M.2 module, wire to W_DISABLE2. During BT firmware download, need to have reset signal to indicate the firmware loading event.

Here is an example of the script to download BT firmware.

#!/bin/sh

# de-assert BT_REG_ON (assert W_DISABLE2# on M.2 interface)

gpioset 5 7=0

sleep 0.1

# Start firmware download in background

brcm_patchram_plus --no2bytes --autobaud_mode --baudrate 921600 \

                   --use_baudrate_for_download --enable_hci \

                   --patchram /lib/firmware/cypress/CYW55560A1.hcd /dev/ttymxc0 &

# assert BT_REG_ON (de-assert W_DISABLE2# on M.2 interface)

sleep 0.1

gpioset 5 7=1

The Sona-IF573 is the first Laird Wifi module that introduces "Fast Virtual Simultaneous Dual Band Operation" that allows for being connected in the 2.4GHz band as a client as well as in the 5GHz band.

It is also thinkable to open a soft AP in one band while being connected as a client in the other.

In 2.4GHz and 5GHz bands, the answer is yes. However, in 6GHz band, according to the WiFi 6E spec, only SAE or OWE is supported, not included PSK.

There are several patches from Infineon for SAE mode and 6GHz band related. Unless you want to patch all of these by yourself, otherwise need to use Laird summit supplicant to make it work properly.

Yes, this will be supported in IF573.

No, the traditional btattach implementation for BT serial interfaces that relies on vendor

specific modules in the kernel is not sufficient because it has no mechanism to

incorporate BT_REG_ON/W_DISABLE2# control.

Yes, it's mandatory to enable CTS/RTS in UART, otherwise BT firmware won't be loaded.

Transition mode is to support WPA2 and WPA3 at the same time. In 6GHz band, WPA2 is no longer supported, but just WPA3, and no support of  transition mode as well.

According to WI-Fi alliance, only H2E mode is supported in WPA3. It's no longer possible to use HNP (hunt/peck).

In the Regulatory Tools package you receive there are many files. The filename structure is:

{radio-type}-{toolchain}-{version}.tar.bz2

For example, the file mfg60n-arm-eabihf-10.135.0.6.tar.bz2 would be for our 60 Series radio running on a system with a GNU Embedded Application Binary Interface (High Float) running version 10.135.0.6 of the Laird firmware. 

An easy way to determine your toolchain is to use the command:

ls -l /ld-linux*

For Regulatory Testing you will be required to load a special firmware to put the radio into "Test Mode". The code for our Wi-Fi modules is available-by-request by opening a case with our Support Team at https://www.lairdconnect.com/resources/support.

Laird Connectivity is committed to the long-term supply of all its standard embedded wireless modules and packaged products. Laird Connectivity’s products are specifically designed to meet the needs of the industrial and medical markets, which typically require 7 – 10 years product lifecycle. Although Laird Connectivity can’t guarantee that a component used in our products will not be obsoleted and cannot be reasonably substituted, Laird Connectivity can assure customers we will continue to sell our product when we have customer demand and can obtain the necessary components to build our products.

View our full policy here.