Sterling™-EWB IoT Module

If programming the Sterling-EWB outside of WICED ensure that the address locations match. WICED will change the addresses. This has been seen specifically with the the filesystem.bin file.

The external SPI of the Sterling-EWB can be programmed on the DVK using Segger Jflash-SPI.

Use Pinout SPI 20-pin from the Segger site to connect jlink plus to following Sterling-EWB pins.

The Sterling-EWB has internal and external spi with the following file locations:

Internal SPI

• bootloader
• DCT (Device Configuration Table)
• application

External SPI

• apps.bin (index of files for external flash)
• filesystem.bin (Wi-Fi firmware)

R4 of the Sterling-EWB is using a Macronix - MX25L1633E and is supported by WICED.

Infineon/Cypress supports the QDID host software stack in the WICED platform as shown below. 

WICED Host SDK for BT5.0

D038395 :  https://launchstudio.bluetooth.com/ListingDetails/61365

WICED Host SDK for BT5.2

D050754 : https://launchstudio.bluetooth.com/ListingDetails/120227

Yes hardware modification is required please contact support for more information.

On the base SiP module (453-00012) Vref is connected to pin 65 (VDD_3V3) On the chip antenna or U.FL modules (453-00013 or 453-00014) it is connected to pin 37 (VDD_MCU).

The Sterling-EWB supports TCP, UDP, and SSL connections with concurrent connections by using a connection id.
The connection id is used when sending commands and also appears in the strings coming back to the Sterling-EWB to support concurrent connections.
Please see the Sterling-EWB AT Command Guide for examples.

The STM32 is able to support a CAN interface on MCU pins PC11 (CAN1_RX) and PE3 (CAN1_TX).
These are pins 45 (RX - MICRO_GPIO_28) and pin 69 (TX – MICRO_I2S2_WS) accordingly on the Sterling-EWB module.
WICED has STM32 drivers for the CAN bus, however, the CAN bus has not been tested by Laird Connectivity.

No, the current version of firmware does not provide access to the STM32F412 I/Os.

The current version of AT-Cmd firmware supports scan and provisioning over BLE.

In order to leverage our modular certifications, you must follow the RF design of the module associated with the chip/SIPT. Design files will be provided upon request so you can reproduce our design on your custom board. We highly suggest you to take advantage of our free design review to prevent any issues when going for certification testing.

Please submit a ticket using our support portal when you are ready to begin the process.

A basic WICED app with Wi-Fi and BT will require about 300k bytes of internal flash. The Wi-Fi firmware is about 400k bytes and can live in either internal or SPI flash memory. The internal flash is 1 Mbyte.

If you’re using SPI flash for the Wi-Fi firmware, there is roughly 700k bytes free in the internal flash. If you’re using internal flash for the Wi-Fi firmware, you have roughly 300k bytes available.

Unfortunately the LWB Series can only be configured for a static region. We do have options with our other radios, please contact support and we can make a recommendation based on your project's needs.

We do not support the USB interface on the Sterling-EWB. The VDD_USB power supply pin ,as labeled, only provides bias to pins PA11 and PA12.  That is why it specified as 3.0 – 3.6V in the datasheet.

The USB interface on the DVK (J24) is only to the FTDI USB-UART translator, the communication to the EWB is on UART1 from the FTDI part. 

A basic WICED app with Wi-Fi and BT will require about 300k bytes of internal flash. The Wi-Fi firmware is about 400k bytes and can live in either internal or SPI flash memory. The internal flash is 1 Mbyte.

If you’re using SPI flash for the Wi-Fi firmware, there is roughly 700k bytes free in the internal flash. If you’re using internal flash for the Wi-Fi firmware, you have roughly 300k bytes available.

There is a penalty at power-up for putting W-iFi firmware in SPI flash. Loading the firmware from SPI flash takes several (approx. 5) seconds. Loading the firmware from internal flash is considerably faster. After power-up, there is no difference.

Yes, The EWB can operate as a soft AP and/or client.

The following debuggers were tested to program and debug the Sterling-EWB

• Olimex ARM-USB-TINY-H
• JLink Plus

The FTDI chip that is on the EWB dev kit board is nearly identical to what is inside of the Olimex adapter (FT2232).

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

To determine the max number of connections, use the wwd_wifi_get_max_associations() API. On version 6.2 of the WICED SDK, this API returns 32. Note however that actual numbers depends on the use case. Depending on the resources available on the host, it may or may not be able to service all 32 connections.

Yes it does. This can be easily tested with the apsta  sample app that's included with the WICED SDK. The sample app can be found in the ..\WICED-Studio-Folder\43xxx_Wi-Fi\apps\snip\apsta folder. Note when using this feature, the AP and STA has to be on the same channel.

Yes, it does. Per the Cypress' "Enterprise Security  User Guide", which is included with the WICED SDK, EAP-TLS, EAP-TTLS are PEAPv0-MSCHAPv2 are supported.

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

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.