Sterling-LWB5 Dual-Band WiFi Module with Bluetooth 4.2

Recommended for New Design (RND)

Overview

Dual-Band 802.11ac WiFi + Bluetooth v4.2 Combo Module

The Sterling-LWB5 dual-band Wi-Fi, Bluetooth® Smart, and Bluetooth® Smart Ready module offers significant value to developers by providing an unmatched breadth of options, certifications, and antenna options, which altogether provide greater flexibility to meet the challenging requirements of many wireless designs. This certified module is based on the Cypress (formerly Broadcom) CYW43353 chipset to create one of the very first commercially available solutions that offers IEEE 802.11ac capabilities for ultra-high data rate 5 GHz Wi-Fi connectivity, while also featuring classic Bluetooth and BLE connectivity as well. The module comes in three configurations to best address specific applications, each boasting an industrial temperature rating (-40° to +85° C) and an industry-leading range of certifications and antenna options.

Specifications

BT Capable
4.2
BT Chipset
Combo
BT Dual Mode
Yes
BT Interfaces
UART
Dimension (Height - mm)
1.2 mm
Dimension (Length - mm)
10 mm
Dimension (Width - mm)
10 mm
Line
Professional
Operating Temp (Max) (°C)
+85 °C
Operating Temp (Min) (°C)
-40 °C
Spatial Streams
SISO
Wi-Fi Chipset
BCM 43353
Wi-Fi Interfaces
SDIO
Wi-Fi Spec
a/b/g/n/ac
Product Type Technology OS/Software System Architecture Chipset (Wireless) Antenna Type Logical Interfaces Frequency Range (Min) Frequency Range (Max) Frequency Range 2 (Min) Frequency Range 2 (Max) Description Dimension (Height - mm) Dimension (Length - mm) Dimension (Width - mm) Type
450-0162 Embedded Module 802.11abgn, 802.11ac, Bluetooth 4.2, Dual Mode (Classic + BLE) Linux, Android Hosted Infineon (Cypress) CYW43353 External Serial, GPIO, SDIO, PCM, I2S 2400 MHz 2495 MHz 5150 MHz 5825 MHz Sterling-LWB5 SiP 1.2 mm 10 mm 10 mm SiP Module
Product Type Technology OS/Software System Architecture Chipset (Wireless) Antenna Type Logical Interfaces Frequency Range (Min) Frequency Range (Max) Frequency Range 2 (Min) Frequency Range 2 (Max) Description Dimension (Height - mm) Dimension (Length - mm) Dimension (Width - mm) Type
450-0168 Embedded Module 802.11abgn, 802.11ac, Bluetooth 4.2, Dual Mode (Classic + BLE) Linux, Android Hosted Infineon (Cypress) CYW43353 External Serial, GPIO, SDIO, PCM, I2S 2400 MHz 2495 MHz 5150 MHz 5825 MHz Sterling-LWB5 Module with U.FL 2 mm 21 mm 15 mm Module
Product Type Technology OS/Software System Architecture Chipset (Wireless) Antenna Type Logical Interfaces Frequency Range (Min) Frequency Range (Max) Frequency Range 2 (Min) Frequency Range 2 (Max) Description Dimension (Height - mm) Dimension (Length - mm) Dimension (Width - mm) Type
450-0169 Embedded Module 802.11abgn, 802.11ac, Bluetooth 4.2, Dual Mode (Classic + BLE) Linux, Android Hosted Infineon (Cypress) CYW43353 Internal Serial, GPIO, SDIO, PCM, I2S 2400 MHz 2495 MHz 5180 MHz 5835 MHz Sterling-LWB5 Module with Chip Antenna 2 mm 21 mm 15 mm Module
Product Type Technology OS/Software System Architecture Chipset (Wireless) Antenna Type Logical Interfaces Frequency Range (Min) Frequency Range (Max) Frequency Range 2 (Min) Frequency Range 2 (Max) Description
450-0171 Development Kit 802.11abgn, 802.11ac, Bluetooth 4.2, Dual Mode (Classic + BLE) Linux, Android Hosted Infineon (Cypress) CYW43353 External Serial, GPIO, SDIO, PCM, I2S 2400 MHz 2495 MHz 5180 MHz 5835 MHz Sterling-LWB5 SD Card Dev Board with U.FL
Product Type Technology OS/Software System Architecture Chipset (Wireless) Antenna Type Logical Interfaces Frequency Range (Min) Frequency Range (Max) Frequency Range 2 (Min) Frequency Range 2 (Max) Description
450-0172 Development Kit 802.11abgn, 802.11ac, Bluetooth 4.2, Dual Mode (Classic + BLE) Linux, Android Hosted Infineon (Cypress) CYW43353 Internal Serial, GPIO, SDIO, PCM, I2S 2400 MHz 2495 MHz 5180 MHz 5835 MHz Sterling-LWB5 SD Card Dev Board with Antenna

Photo Gallery

450-0171

450-0172

Certified Antennas

  • 001-0009

    001-0009

    2.4 / 5.5 GHz Dipole RF Antennas

    Pre-certified 2.4 and 5 GHz RF antennas, IP67-rated for dust and water protection.

    Learn More
  • FlexPIFA Antenna

    001-0016

    FlexPIFA Flexible Adhesive-Backed PIFA Internal Antenna

    Industry-first, flexible, planar inverted-F antenna for curved surfaces 2.5-3 dBi gain. 2.4 GHz and dual-band 2.4/5.5 GHz. 

    Learn More

Become a Laird Connectivity Customer and Gain Exclusive Access to Our Design Services Team

  • Antenna Scans
  • Antenna selection and placement
  • Custom antenna design
  • Worldwide EMC testing / certifications
  • Embedded RF hardware / firmware design
  • Cloud architecture and integration
  • Mobile application development
  • Product & Industrial Design

Talk to an Expert

Documentation

Name Part Type Last Updated
Application Note - Guidelines for Replacing Antennas v1.0 All Application Note 01/17/2019
Application Guide, Sterling-LWB5 All Documentation 03/29/2019
Datasheet - Sterling-LWB5 All Datasheet 01/14/2021
Product Brief All Brochure 03/29/2019
Sterling LWB5 Declaration of Conformity All Documentation 03/29/2019
Sterling-LWB Certification Guide All Documentation 10/19/2020
Test Report, EN60950-1 2006, Sterling-LWB5 Module All Documentation 03/29/2019
Test Report, EN60950-1 2006, Sterling-LWB5 SD Card All Documentation 03/29/2019
CAD Files Sterling-LWB5 U.FL and Chip Antenna Modules All Technical Drawings 03/29/2019
CAD Files Sterling-LWB5 U.FL and Chip Antenna SD Cards All Technical Drawings 03/29/2019
Sterling-LWB SD Card User Guide All Documentation 03/29/2019
Product Change Notice 1-2017 (Sterling-LWB & LWB5) All Quality and Environmental 03/29/2019
EU Certifications - Sterling LWB5 All Certification 01/14/2021
FCC and ISED (Canada) Certifications - Sterling LWB5 All Certification 12/17/2020
MIC Certifications - Sterling LWB5 All Certification 12/17/2020
Radio Equipment Directive (RED) Updates All Certification 03/29/2019
Sterling-LWB5 Bluetooth SIG Listing All Certification 03/29/2019
Software, Sterling-LWB, LWB5, and LWB5+ All Software 04/14/2021
RoHS 3 Compliance - Wi-Fi Products All Certification 10/30/2020
Regulatory Information - Sterling-LWB5 All Certification 01/14/2021
Application Note - PetaLinux Software Integration - 60 Series and LWB Series All Application Note 08/13/2020

FAQ

What are the requirements to be able to leverage "Modular Approval"?

In order to be able to leverage the Modular Approval of a wireless module the following requirements have to be met:

  • The RF circuitry must be shielded
  • The module must have buffered modulation/data inputs. Module must inherently ensure compliance under host fault (watch dog) conditions
  • The module must have a regulated power supply
  • An antenna needs to be attached permanently or a unique antenna connector must be mounted on the module
  • The module must be compliant with the regulations in a stand-alone configuration
  • The module must be labeled with its permanently affixed FCC ID label or use an electronic display
  • A user manual needs to provide comprehensive instructions to explain compliance requirements.
  • The module must comply with RF exposure requirements

What is my best chance to use an antenna that is not pre-certified for my wireless module?

To use an antenna that is not listed on your wireless modules datasheet, it must be of the same topology (e.g. dipole, PIFA, etc.), equal or lesser gain, and have the same in-band and out of band characteristics.

Note: Japan (MIC) lists applicable antennas on its certificates. If your antenna is not on the approved list, regardless of whether it is comparative, it must be added to the certificate before it can be used in Japan.

Backports fails to compile with 'refcount_t {aka struct refcount_struct}' has no member named 'counter'

There are certain patch ranges within kernels 4.4 and 4.9 that need a modification so backports can build, the reason why we cannot fix it in backports is that we cannot track and differentiate between patch versions of the same 'major.minor' version of kernel. To fix this issue, move the function kobject_has_children from linux/kobject.h to drivers/base/core.c in your kernel source, rebuild the kernel and then rebuild backports.

How do I manually cross-compile the Sterling supplicant from source?

It is best practice to include the source in your build system. If using Yocto, our external layer will do this for you.
Here is an example manually compiling using our SOM60 as a target in a Buildroot environment:

 

  1. Download and extract the Sterling supplicant source.
  2. Navigate to the "laird" directory.
  3. Edit the config_laird file:
  4. Find the following line, uncomment and change the path to your "openssl/include" directory:
    original line:
    #CFLAGS += -I/usr/local/openssl/include
    modified line:
    CFLAGS += -I/wb/buildroot/output/som60sd/build/host-libopenssl-1.1.1d/include
  5. Run make with the following flags
    set:
    CC="" for your cross-compile binary
    PKG_CONFIG="" for your pkg-config binary
    PKG_CONFIG_PATH="" for your pkgconfig directory
    OBJCOPY="" for your objcopy binary

 

Note the following example is a single line command:
make CC="/wb/buildroot/output/som60sd/host/bin/arm-buildroot-linux-gnueabihf-gcc" PKG_CONFIG="/wb/buildroot/output/som60sd/host/bin/pkg-config" OBJCOPY="/wb/buildroot/output/som60sd/host/arm-buildroot-linux-gnueabihf/bin/objcopy" PKG_CONFIG_PATH="/wb/buildroot/output/som60sd/host/arm-buildroot-linux-gnueabihf/sysroot/usr/lib/pkgconfig"

How do I use your precompiled dynamically linked binaries such as your supplicants or radio testing tools?

If the binary returns "not found" or does not work after confirming the executable bit is set with chmod +x <filename>, then you will need to create a symlink pointing to the system's interpreter. The file tool will show the expected interpreter and architecture of a binary, readelf is a lot more verbose and is used to discover the expected "sonames" of shared libraries. These utilities do not have to be used on the target system and is convenient to use on a common x86 Linux machine. These utilities can be installed on Ubuntu with sudo apt install binutils.

Example output from the file command:
sterling_supplicant-arm-7.0.0.139/usr/sbin$ file wpa_supplicant
wpa_supplicant: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.3, for GNU/Linux 3.0.0, stripped

Example output from the readelf command:
sterling_supplicant-arm-7.0.0.139/usr/sbin$ readelf -ld wpa_supplicant Elf file type is EXEC (Executable file)
Entry point 0xba28
There are 10 program headers, starting at offset 52 Program Headers:
...
<edited>
...
      [Requesting program interpreter: /lib/ld-linux.so.3]
...
<edited>
...
Dynamic section at offset 0x176ee8 contains 30 entries:
  Tag        Type                         Name/Value
 0x00000001 (NEEDED)                     Shared library: [librt.so.1]
 0x00000001 (NEEDED)                     Shared library: [libnl-3.so.200]
 0x00000001 (NEEDED)                     Shared library: [libnl-genl-3.so.200]
 0x00000001 (NEEDED)                     Shared library: [libdl.so.2]
 0x00000001 (NEEDED)                     Shared library: [libdbus-1.so.3]
 0x00000001 (NEEDED)                     Shared library: [libgcc_s.so.1]
 0x00000001 (NEEDED)                     Shared library: [libc.so.6]
...
<edited>
...

To use this binary, we will have to confirm this symlink exists or create a new symlink pointing to the interpreter on the target filesystem:
cd /lib/
ls -l ld-*
-rwxr-xr-x    1 root     root        158772 Dec  2  2019 /lib/ld-2.26.so
ln -sf ld-2.26.so ld-linux.so.3
ls -l ld-*
-rwxr-xr-x    1 root     root        158772 Dec  2  2019 /lib/ld-2.26.so
lrwxrwxrwx    1 root     root            10 Dec 21 18:55 /lib/ld-linux.so.3 -> ld-2.26.so

If the binary now reports that a library is not found when executed, repeat the steps shown above for creating a library symlink/soname pointing to it's real name. This may require you to use the find command to discover the location of the library. Example for libnl-genl-3:
find / -name 'libnl-genl-3*' -exec ls -l {} 2>/dev/null \;
-rwxr-xr-x    1 root     root         18524 Feb 14 23:42 /usr/lib/libnl-genl-3.so.200.26.0
cd /usr/lib/
ln -sf libnl-genl-3.so.200.26.0 libnl-genl-3.so.200
ls -l libnl-genl-3*
-rwxr-xr-x    1 root     root         18524 Feb 14 23:42 /usr/lib/libnl-genl-3.so.200.26.0
lrwxrwxrwx    1 root     root            24 Feb 14 23:37 /usr/lib/libnl-genl-3.so.200 -> libnl-genl-3.so.200.26.0

If the library does not exist, you will have to include that package in your build. For instance if the above example libnl was missing, include the libnl package when building your filesystem.

Does Laird Connectivity have plans to get KCC approval for the Sterling-LWB, Sterling-EWB or the Sterling-LWB5 modules?

Currently, there are no plans to get the KCC certifications for Sterling-LWB, Sterling-EWB or the Sterling-LWB5.

How can I receive notifications of the latest updates to the driver and firmware?

Simply log into GitHub, go to the corresponding release packages page and click the "Watch" button (eye icon) in the top right of the page. Some radios (such as the LWB Series) requires you to download firmware separately from the product page; this firmware is updated on the product page in conjunction with GitHub releases.

Release Packages

How many clients are supported when using the SoftAP capability on the Sterling-LWB5?

Up to 5 clients are supported

How do I test layer 2 Bluetooth stability without setting up a profile on a Linux platform?

In BlueZ, some commands such as l2test or l2ping are able to generate traffic on L2CAP layer. To test performance and reliability, you can use the l2test command:

On the server, run the command:

l2test -I 2000 -r

On the client side, run the command:

l2test -O 2000 -s XX:XX:XX:XX:XX:XX