Sterling™-LWB+ WiFi 4 and Bluetooth 5.2 Modules

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.

Yes, Laird Wifi modules can be integrated with OpenWRT like with almost any other Linux operating system.

See Lairds "Guide" Section for an example on how to integrate the Sterling-LWB5+ Wifi/Bluetooth module with OpenWRT on a Raspberry Pi.

I am getting an error in dmesg "brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50" when trying to start my Sterling-LWB+ radio. 

In general, this error occurs when you do not have a 32kHz external oscillator in your design. This is required for the LWB series radios. 

From the Sterling-LWB+ Datasheet:

PM mode is ignored when operating as an AP.  It is effectively PM=0.

The setting would be similar as TLS setup except these two configurations. 

802-11-wireless-security.proto wpa3

 802-11-wireless-security.key-mgmt wpa-eap-eap-suite-b-192

For example:

nmcli c add type wifi ifname wlo61s0 con-name 'My Wifi Network' \
  802-11-wireless.ssid 'My Wifi' \
      802-11-wireless-security.key-mgmt wpa-eap-eap-suite-b-192 \

      802-11-wireless-security.proto wpa3 \

      802-1x.eap tls \
      802-1x.identity identity@example.com \
      802-1x.ca-cert /etc/cert/ca.pem \
      802-1x.client-cert /etc/cert/user.pem \
      802-1x.private-key /etc/cert/user.prv \
      802-1x.private-key-password the_password

If you configure Wi-Fi setting by wpa_supplicant, you will need to setup a configuration file such as "/etc/wpa_supplicant.conf", and then execute wpa_supplicant as below command.

wpa_supplicant -Dnl80211 -c /etc/wpa_supplicant.conf -i wlan0 -B -ddd

Here is the example of wpa_supplicant.conf to setup "WPA3 Enterprise Suite b 192" network.

ctrl_interface=/var/run/wpa_supplicant

#update_config=1

network={

        ssid="Cisco_2802_WPA3_Enterprise"

        proto=WPA3

        key_mgmt=WPA-EAP-SUITE-B-192

        ieee80211w=2

        pairwise=GCMP-256

        group=GCMP-256

        group_mgmt= BIP-GMAC-256

        eap=TLS

identity=xxxx

ca_cert="/etc/cert/ca.pem"

client_cert="/etc/cert/user.pem"

private_key="/etc/cert/user.prv"

private_key_passwd="password"

phase1=”tls_suiteb=1”

}

The Sterling-LWB, Sterling-LWB5, Sterling-LWB5+ and the Sterling-LWB+ do not support Monitor Mode. As of 3Q-2023, the only Laird Radios that support Monitor mode are the 60-SIPT and the 60-2230C.

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.

No, the LWBx series of WiFi/BT modules do not support WPA3 OWE or SAE-PK (Public Key).

The Sterling-LWBx radios can be used with Raspberry Pis running Raspberry Pi OS.

A module parameter (available from release version 10.54.0.13 on) will have to be used to prevent the module from ideling as OS calls from the mmc driver on RPi will not be answered suitably causing the SDIO communication not to function correctly.

Please reference this tutorial for the 60-series radios and contact Laird for the usage of the above mentioned module parameter for the LWB radios.

Wifi adapters by default often come up in a power save mode. That is a mode in which the adapter shuts off the network connection in a state of inactivity.

While this is a good way to achieve additional power savings it of course introduces a delay for re-connecting.

To set the mode on or off:

iw wlan0 set power_save on
iw wlan0 set power_save off

To query the current setting issue:

iw wlan0 get power_save

Some systems might require "sudo" in front of the commands to be exectuted.

The Jetson TX2 NX does not act the same as the Jetson Nano when providing power to the m.2 slot. The Jetson Nano will automatically toggle PMU_EN, while the TX2 NX will require a manual toggle of the pin in software.

This applies to USB variants, as PCIe variants have a reset built into the PCIe standard.

On a linux system if the dmesg is reporting an unknown symbol this is usually due to one of the following:

1. The backports drivers didn't get compiled against the correct kernel.
2. WLAN, CONFIG_BT, and WIRELESS were not removed from the kernel menuconfig.
3. backports was compiled with different flags than how the kernel was compiled.

Currently none of our Wi-Fi modules support reading a temperature value.

When you have an agreement with Laird to send in your device for testing of anything around your radio you need to make sure your radio can be set to all necessary test modes.

In order to do that please contact the Laird FAE already known to you or write to Laird at "support@lairdconnect.com" to get in contact with us.

Your FAE will be able to help you determine if your device is fit for testing.

(1) By option regdomain

/etc/modprobe.d/brcmfmac.conf

# Sample contents of a brcmfmac.conf file configured for operation in
#  the United States
options brcmfmac regdomain="US"

(2) By device tree

@mmc0 {
  #address-cells = <1>;
  #size-cells = <0>;
  bus-width = <4>;
  non-removable;

  brcmf: wifi@1 {
    reg = <1>;
    compatible = "brcm,bcm4329-fmac";
    laird,regdomain = "US";
  };
};

Please refer this blog as below. Laird are currently investigating these issues internally and investigating with the chipset vendors and our internal QA team to establish test scenarios to evaluate the impacted devices.

/resources/blog/frag-attack-wi-fi-putting-pieces-back-together

The AP and STA are on the same channel potentially causing disconnections if the STA roams to a different AP. The Sterling-70 has the advantage of dual independent radios that can run on different Wi-Fi channels.

MCS stands for Modulation Coding Scheme and is an industry metric index based on Wi-Fi connection parameters between a client and wireless access point. These parameters include modulation type, coding rate, spatial streams, channel width, and guard interval.

This can be found by reviewing the release notes for the specific product on GitHub.

• LWB, LWB5, LWB5+ - Sterling-LWB-and-LWB5-Release-Packages
• Sterling 60 - Sterling-60-Release-Packages

Yes as new kernels are updated in Ubuntu automatically it will break backports and will need to be reinstalled.

Laird modules can be used on a Ubuntu system with a kernel version that is supported by Laird backports.

To check, find the kernel version of the Ubuntu system and then check the release notes of the products to see if the latest backports supports that kernel.

Sterling-60 Release Notes

Sterling-LWB Release Notes

No, if VBAT is 3.6V or greater, this power source should be used for VDDIO_RF, and USB2_AVDD33 if strapped for USB. Otherwise leave this pin disconnected.

The shelf life statements are essentially to prevent mishandling of the product and not storing it properly. If the modules are still sealed in the package, stored at the proper temperature and have not been exposed to moisture they should be fine. However, when working with modules beyond their shelf life you MUST bake the modules before populating the them to your board. Failure to bake the modules could result in the yield rate dropping down lower than expectation due to popcorn or de-lamination on the modules. It is recommended that you follow IPC/JEDEC J-STD-033 which is the general standard for the handling, packing, shipping and use of moisture/reflow sensitive surface mount devices.

Our main concern is around the castellation/pads which solder the module to the board. It is imperative those pads do not get tarnished, as this would cause soldering issues. Humidity can affect solderability as well, as if there is any excess moisture in the solder on the module, during reflow of the module to the board, steam balls can essentially explode the solder and sometimes result in an open circuit (or possibly a short circuit).

As long as all of the moisture handling and temperature guidelines are being followed you will likely have no issues. It is further recommended that when you do the build with modules that have exceeded their shelf life that you start with a handful to perform a test run and do a final test to make sure all is working as expected. As long as there are no issues with the initial test run we would expect that you will not experience any problems.

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.