Requirements#

Hardware#

Development Kits#

The required development kit is defined for each application example. Information on the required development kit is described in the project's readme files in the repository of the example.

The most frequently used development, starter, and explorer kits are listed in the table below.

Description

Identifier

Documentation/Links

EFR32xG22 Wireless Gecko Starter Kit

SLWSTK6021A

SLWSTK6021A

BGM220 Bluetooth Module Explorer Kit

BGM220-EK4314A

BGM220-EK4314A

Thunderboard Sense 2

SLTB004A

SLTB004A

EFR32xG24 Dev Kit

SLWSTK6021A

xG24-DK2601B

Description

Identifier

Documentation/Links

SparkFun Qwiic Cable Kit

KIT-15081

KIT-15081

Silabs Click Shield

MIKROE-4464

MIKROE-44641

Third-Party Hardware#

The hardware drivers and some of the virtual applications require third-party hardware. These third-party hardware boards can be purchased from the following suppliers.

The documentation of each hardware driver and application example describes the required type of third-party board.

The most frequently used third-party suppliers

Supplier

Link

MikroeMikroe

https://www.mikroe.com

SparkfunSparkfun

https://www.sparkfun.com

AdafruitAdafruit

https://www.adafruit.com

Software#

Development Environment#

Simplicity Studio is the core development environment designed to support the Silicon Labs IoT portfolio of system-on-chips (SoCs) and modules. It provides access to target device-specific web and SDK resources; software and hardware configuration tools; an integrated development environment (IDE) featuring industry-standard code editors, compilers and debuggers, and advanced, value-add tools for network analysis and code-correlated energy profiling.

SSSS

Download Simplicity Studio

Simplicity Studio Overview

Software Development Kit#

The required GSDK version is described in the readme files for each project.

In general, GSDK v4.x.x version or higher is required to compile and run the examples.

Some of the examples require Third Party Hardware Driver GSDK Extension.

Setup#

Silabs development kits can be connected to any third-party shield via simple wiring, however, most of the boards support quick and easy connectivity via Qwiic and mikroBUS connectors.

Mikroe Click Boards#

MikroElektronika Click boards can be connected to host controllers via the mikroBUS connectors; see the pinout specification below.

mikroBUSmikroBUS

Sparkfun Qwiic or Adafruit STEMMA QT Boards#

The sparkfun Qwiic and Adafruit STEMMA QT capable boards use the same 4 pins - JST SH 1.0mm pitch connectors to provide quick and easy I2C connectivity between development kits and third-party boards.

QwiicCableConnectorQwiicCableConnector

All Qwiic/STEMMA QT cables have the following color scheme and arrangement:

  • Black = GND

  • Red = 3.3V

  • Blue = SDA

  • Yellow = SCL

These are the most frequently used cables for Sparkfun Qwiic and Adafruit STEMMA QT connections.

QwiicCableSetQwiicCableSet

BGM220 Bluetooth Module Explorer Kit#

BGM220PmikroBUSBGM220PmikroBUS

The kit features support for hardware add-on boards via a mikroBus socket and a Qwiic connector. The hardware add-on support allows developers to create and prototype applications using a virtually endless combination of off-the-shelf boards from mikroE, sparkfun, AdaFruit, and Seeed Studios.

MikroeSilabsClickShieldMikroeSilabsClickShield

EFR32xG22 Wireless Gecko Starter Kit/ Thunderboard Sense 2 / EFR32xG24 Dev Kit#

Mikroe provides a Silabs Click Shield for easily connecting Silabs development kits from the Thunderboard family or any other Silabs wireless or MCU starter kit through the expansion header (EXP) to the Mikroe Click boards.

Sparkfun Qwiic/Adafruit STEMMA QT boards also can be connected to these development kits through the expansion header.

MikroeSilabsClickShieldOverviewMikroeSilabsClickShieldOverview

Mikroe Click Temperature sensor board connected to a Thunderboard Sense 2 via a Silabs Click shield.

MikroeSilabsClickShieldMikroeSilabsClickShield