Summit Software Stack for 60 Series
Overview
The Summit Software Stack is an enterprise-grade software update that unlocks the full potential of Laird Connectivity’s 60 Series modules. Understanding that each RF environment is different, we have taken careful considerations into the configurability and feature enhancements of the Summit Stack to ensure that devices perform at peak performance. The Summit Software Stack includes optimizations that reduce channel scan times, provides up to 15 times faster roaming, and up to 50 percent more consistent roaming when compared with other radios.
The Summit Stack includes Tier-2 support with Laird Connectivity’s industry-best support team. Let our support and engineering experts speed your design to market with our most comprehensive feature set to date.
Note: Sold as separate item with Sterling hardware, one-time per module license.
Power Supply
Wake-on-Wireless allows the device to sleep until an intended packet arrives, saving significant power consumption

Security
Highly customizable with configurable authentication timeout, EAP-FAST support, Middle CA certificate support and fast startup connections

Software
Custom module firmware with Adaptive Worldwide Mode, custom Laird Connectivity wireless supplicant, and upgraded connection manager

For the most mission-critical wireless where failure is not an option.
Our Summit stack unlocks the full potential of our 60 Series Wi-Fi + Bluetooth modules. With the fastest scanning and roaming, your device enjoys the most reliable connection, even in mobile devices. And stability enhancements in key caching and TLS improvements render your device more stable and your connection more reliable.

Need integration support? Our industry-best support team has you covered.
Purchase of the Summit software stack includes increased access to Laird Connectivity's global support staff. We offer Tier 2 and FAE support with a deep understanding of wireless design and with access to Laird Connectivity's engineering team. Don't go it alone – count on us to safely guide your product to market.

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
Documentation
Name | Part | Type | Last Updated |
---|---|---|---|
Product Brief - Summit Stack | All | Documentation | 10/16/2020 |
Summit Stack Evaluation Request | All | Software | 03/25/2020 |
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.
Does the ST60-2230C support 3.3 VIO?
No, the ST60 SIPT module on the 2230C carrier board is strapped for 1.8 VIO operation only. Design for an embedded SDIO operation and does not allow 3.3 VIO even during card enumeration.
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.
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:
- Download and extract the Sterling supplicant source.
- Navigate to the "laird" directory.
- Edit the config_laird file:
- 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
- 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.
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.
Where can I find additional documentation for the 60 series radios?
Additional documentation can be located in the Sterling 60 GitHub repository