SILICON LABS EFM32PG26 Explorer Kit User Guide

Programming the EFM32PG26 Explorer Kit is easy using a USB
Type-C cable and the on-board J-Link debugger. A USB virtual COM
port provides a serial connection to the target application. The
kit is supported in Simplicity StudioTM, and a Board Support
Package (BSP) is provided for application development.

1.1 Kit Contents

Refer to the Silicon Labs web page for detailed information on
the contents of the kit.

1.2 Getting Started

Visit the following link for step-by-step instructions on how to
get started with your EFM32PG26 Explorer Kit: https://www.silabs.com/dev-tools

External Hardware Connection

Connect external hardware to the kit using the 28 breakout pads
that present peripherals from the EFM32PG26 Pearl Gecko MCU, such
as I2C, SPI, UART, and GPIOs. The mikroBUS socket allows adding
mikroBUS boards through SPI, UART, or I2C. The Qwiic connector can
be used for hardware from the Qwiic Connect System via I2C.

FAQ

Q: Where can I find more information about the kit
contents?

A: Detailed information about the kit contents can be found on
the Silicon Labs web page.

“`

View Fullscreen

UG608: EFM32PG26 Explorer Kit User’s Guide

The EFM32PG26 Explorer Kit is an ultra-low-cost, small form factor development and evaluation platform for the EFM32PG26 Pearl Gecko MCU.
The EFM32PG26 Explorer Kit is focused on rapid prototyping and concept creation of multi-purpose applications. It is designed around the EFM32PG26 MCU, which is an ideal device family for developing energy-friendly embedded applications.
The kit features a USB interface, an on-board SEGGER J-Link debugger, two user-LEDs and two buttons, and support for hardware add-on boards via a mikroBUSTM 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 Studio.

TARGET DEVICE
· EFM32PG26 Pearl Gecko MCU (EFM32PG26B500F3200IM68-B)
· 32-bit ARM® Cortex®-M33 with 80 MHz maximum operating frequency
· 3200 kB flash and 512 kB RAM
KIT FEATURES
· 2x User LEDs and push buttons · 28-pin 2.54 mm breakout pads · mikroBUSTM socket · Qwiic® connector · SEGGER J-Link on-board debugger · Virtual COM port · USB-powered

SOFTWARE SUPPORT

· Simplicity StudioTM

ORDERING INFORMATION

· PG26-EK2711A

silabs.com | Building a more connected world.

Rev. 1.0

Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1 Kit Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.2 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.3 Hardware Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.4 Kit Hardware Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 2.1 Recommended Operating Conditions . . . . . . . . . . . . . . . . . . . . . . 5 2.2 Current Consumption . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 3.1 Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 3.2 Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 3.3 EFM32PG26 Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 3.4 Push Button and LED. . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 3.5 On-board Debugger . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 3.6 Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 3.6.1 Breakout Pads . . . . . . . . . . . . . . . . . . . . . . . . . . . .10 3.6.2 Mini Simplicity Connector . . . . . . . . . . . . . . . . . . . . . . . . .11 3.6.3 MikroBUS Socket . . . . . . . . . . . . . . . . . . . . . . . . . . .12 3.6.4 Qwiic Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . .13 3.6.5 Debug USB Type-C Connector . . . . . . . . . . . . . . . . . . . . . . .14
4. Debugging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 4.1 On-board Debugger . . . . . . . . . . . . . . . . . . . . . . . . . . . .15 4.2 Virtual COM Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
5. Schematics, Assembly Drawings, and BOM . . . . . . . . . . . . . . . . . . . 16
6. Kit Revision History and Errata . . . . . . . . . . . . . . . . . . . . . . .17 6.1 Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17 6.2 Errata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
7. Board Revision History and Errata . . . . . . . . . . . . . . . . . . . . . . 18 7.1 Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18 7.2 Errata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
8. Document Revision History . . . . . . . . . . . . . . . . . . . . . . . . . 19

silabs.com | Building a more connected world.

Rev. 1.0 | 2

UG608: EFM32PG26 Explorer Kit User’s Guide
Introduction
1. Introduction
The EFM32PG26 Explorer Kit has been designed to inspire customers to explore the Silicon Labs EFM32PG26 Pearl Gecko MCU. The kit includes a mikroBUSTM socket and Qwiic® connector, allowing users to add features to the kit with a large selection of off-the-shelf boards.
Programming the EFM32PG26 Explorer Kit is easy using a USB Type-C cable and the on-board J-Link debugger. A USB virtual COM port provides a serial connection to the target application. The EFM32PG26 Explorer Kit is supported in Simplicity StudioTM and a Board Support Package (BSP) is provided to give application developers a flying start.
External hardware is connected to the EFM32PG26 Explorer Kit by using the 28 breakout pads which present peripherals from the EFM32PG26 Pearl Gecko MCU such as I2C, SPI, UART, and GPIOs. The mikroBUS socket allows inserting mikroBUS add-on boards which interface with the EFM32PG26 through SPI, UART, or I2C. The Qwiic connector can be used to connect hardware from the Qwiic Connect System through I2C.
1.1 Kit Contents
The following item is included in the box: · 1x EFM32PG26 MCU Explorer Kit Board (BRD2711A)
1.2 Getting Started
Detailed instructions for how to get started with your new EFM32PG26 Explorer Kit can be found on the Silicon Labs web page: https:// www.silabs.com/dev-tools
1.3 Hardware Content
The following key hardware elements are included on the EFM32PG26 Explorer Kit: · EFM32PG26 Pearl Gecko MCU with 80 MHz operating frequency, 3200 kB flash, and 512 kB RAM · Two LEDs and two push buttons · On-board SEGGER J-Link debugger for easy programming and debugging, which includes a USB virtual COM port · MikroBUS socket for connecting click boardsTM and other mikroBUS add-on boards · Qwiic connector for connecting Qwiic Connect System hardware · Breakout pads for GPIO access and connection to external hardware · Reset button

silabs.com | Building a more connected world.

Rev. 1.0 | 3

1.4 Kit Hardware Layout EFM32PG26 Explorer Kit layout is shown below.

35.56 mm

UG608: EFM32PG26 Explorer Kit User’s Guide
Introduction

Top View
Push Button Push Button
LED Breakout Pads
mikroBUS Socket

EFM32PG26 MCU
Qwiic Connector

LED

57.38 mm

On-board USB J-Link Debugger

USB Type-C Connector – Virtual COM port – Debug access

Reset Button

Figure 1.1. EFM32PG26 Explorer Kit Hardware Layout

silabs.com | Building a more connected world.

Rev. 1.0 | 4

2. Specifications
2.1 Recommended Operating Conditions

UG608: EFM32PG26 Explorer Kit User’s Guide
Specifications

Table 2.1. Recommended Operating Conditions

Parameter USB Supply Input Voltage Supply Input Voltage (VMCU supplied externally)

Symbol

Min

VUSB

—

VVMCU

—

Typ +5.0 +3.3

Max — —

Unit V V

2.2 Current Consumption
The operating current of the board greatly depends on the application and the amount of external hardware connected. The table below attempts to give some indication of typical current consumptions for the EFM32PG26 and the on-board debugger. Note that the numbers are taken from the datasheets for the devices. For a full overview of the conditions that apply for a specific number from a datasheet, the reader is encouraged to read the specific datasheet.
Table 2.2. Current Consumption

Parameter

Symbol

Condition

Typ

EFM32PG26 Current Con-

IEM4

No BURTC, no LF oscillator

0.23

sumption1

IEM2

EM2 mode with 512 kB RAM, RTC running from LFXO

5.0

(VREGVDD = 3.0 V. AVDD = DVDD = IOVDD = 1.8 V

from DCDC)

IEM0

EM0 mode with all peripherals disabled (VREGVDD = 3.0

41.8

V. AVDD = DVDD = IOVDD = 1.8 V from DCDC,

VSCALE2, 80 MHz HFRCO, CPU running Prime from

flash)

On-board Debugger Sleep Current Consumption 2

IDBG

On-board debugger current consumption when USB cable

is not inserted (EFM32GG12 EM4S mode current con-

sumption)

1 From EFM32PG26 data sheet 2 From EFM32GG12 data sheet

Unit µA µA
µA/MHz
nA

silabs.com | Building a more connected world.

Rev. 1.0 | 5

UG608: EFM32PG26 Explorer Kit User’s Guide
Hardware
3. Hardware
The core of the EFM32PG26 Explorer Kit is the EFM32PG26 Pearl Gecko MCU. Refer to section 1.4 Kit Hardware Layout for placement and layout of the hardware components.

3.1 Block Diagram An overview of the EFM32PG26 Explorer Kit is illustrated in the figure below.
Device Connectivity & Debugging

USB Type-C Connector

J-Link Debugger

Mini-Simplicity Breakout Pads

Connector

(EXP-Header pinout)

Buttons and LEDs
User Buttons & LEDs

EFM32PG26 MCU

Expandability

Qwiic Connector

mikroBUS Socket

Figure 3.1. Kit Block Diagram

silabs.com | Building a more connected world.

Rev. 1.0 | 6

3.2 Power Supply The kit is powered by the debug USB cable as illustrated in the figure below.

UG608: EFM32PG26 Explorer Kit User’s Guide
Hardware

5V0

3V3

USB Type-C

OUT

LDO

Automatic Isolation

VMCU

Peripherals

EFM32PG26 MCU
Peripherals
Figure 3.2. EFM32PG26 Explorer Kit Power Topology
The 5 V power net on the USB bus is regulated down to 3.3 V using a low-dropout regulator (LDO). An automatic isolation circuit isolates the LDO when the USB cable is not plugged in. Power can be injected externally on the VMCU net if the USB cable is removed and no other power sources are present on the kit. Failure to follow this guideline can cause power conflicts and damage the LDO.

3.3 EFM32PG26 Reset
The EFM32PG26 can be reset by a few different sources: · A user pressing the RESET button. · The on-board debugger pulling the #RESET pin low.

3.4 Push Button and LED
The kit has two user push buttons, marked BTN0 and BTN1, that are connected to GPIOs on the EFM32PG26. The buttons are connected to pin PB00 and PB01, respectively, and they are debounced by an RC filter with a time constant of 1 ms. The logic state of a button is high while that button is not being pressed, and low when it is pressed.
The kit also features two yellow LEDs, marked LED0 and LED1, that are controlled by GPIO pins on the EFM32PG26. The LEDs are connected to pin PC08 and PC09, respectively, in an active-high configuration.

EFM32PG26 PB00 (GPIO) PB01 (GPIO)

BUTTON0 BUTTON1

PC08 (GPIO) PC09 (GPIO)

LED0 LED1

User Buttons & LEDs

Figure 3.3. Buttons and LEDs

silabs.com | Building a more connected world.

Rev. 1.0 | 7

UG608: EFM32PG26 Explorer Kit User’s Guide
Hardware
3.5 On-board Debugger
The EFM32PG26 Explorer Kit contains a microcontroller separate from the EFM32PG26 Pearl Gecko MCU that provides the user with an on-board J-Link debugger through the USB Type-C port. This microcontroller is referred to as the “on-board debugger”, and is not programmable by the user. When the USB cable is removed, the on-board debugger goes into a very low power shutoff mode (EM4S), consuming around 80 nA typically (EFM32GG12 data sheet number).
In addition to providing code download and debug features, the on-board debugger also presents a virtual COM port for general purpose application serial data transfer.
The figure below shows the connections between the target EFM32PG26 device and the on-board debugger.
Refer to section 4. Debugging for more details on debugging.

Host PC

VCOM_TX

VCOM_RX

USB

On-Board

VCOM_CTS

J-Link

VCOM_RTS

Debugger

SWCLK_C2CK

SWDIO_C2D

DBG_SWO

DATA FRAME

DBG_RESET

EFEMF3R23P2GM2G6
PB02 (USART1.TX) PB03 (USART1.RX) PA06 (USART1.CTS) PA00 (USART1.RTS) PA01 (GPIO.SWCLK) PA02 (GPIO.SWDIO) PA03 (GPIO.SWO) PD04 (FRC.DOUT) PD05 (FRC.DFRAME) RESETn

Figure 3.4. On-Board Debugger Connections Note: PTI pins are not supported. Refer to section 7.2 Errata for more details.

silabs.com | Building a more connected world.

Rev. 1.0 | 8

UG608: EFM32PG26 Explorer Kit User’s Guide
Hardware
3.6 Connectors
The EFM32PG26 Explorer Kit features a USB Type-C connector, 28 breakout pads, a mikroBUS connector for connecting mikroBUS add-on boards, and a Qwiic connector for connecting Qwiic Connect System hardware. The connectors are placed on the top side of the board, and their placement and pinout are shown in the figure below. For additional information on the connectors, see the following sub chapters.
Breakout Pads

Qwiic Connector

P2
PB05 / PB10 PA08 / PB04 PA10 / PB09 AIN0 / PB08
GND 5V PC07 / PB06 – MIKROE_QWIIC_I2C_SDA PC05 / PA09 – MIKROE_QWIIC_I2C_SCL PA04 / AIN3 – MIKROE_UART_TX PA05 / AIN2 – MIKROE_UART_RX PC00 / AIN1 – MIKROE_INT VREFN / PA07 – PWM VREFP 3V3

P3
PB07 / PC12 PC10 / PC11 PD03 / PD06 PD08 / PD07 GND VMCU PC02 / PB11 – MIKROE_SPI_MOSI PC01 / PC13 – MIKROE_SPI_MISO PC03 / PD04 – MIKROE_SPI_SCK PC04 / PD05 – MIKROE_SPI_CS PC06 / PD09 – MIKROE_RST PD02 / PD10 – MIKROE_ANALOG BOARD_ID_SCL BOARD_ID_SDA

USB Type-C Connector

mikroBUS Connector

qwiic Connector
GND VMCU SDA – PC07 SCL – PC05

Mini Simplicity Connector (not mounted)

PD04 SWCLK_C2CK – PA01
SWO – PA03 VCOM_RX – PB03
GND

PD05 PA02 – SWDIO_C2D PB02 – VCOM_TX DBG_RST VMCU
Pin 1

Figure 3.5. EFM32PG26 Explorer Kit Connectors

silabs.com | Building a more connected world.

Rev. 1.0 | 9

UG608: EFM32PG26 Explorer Kit User’s Guide
Hardware
3.6.1 Breakout Pads
Twenty-eight breakout pads are provided and allow connection of external peripherals. There are 14 pads on the left side of the board, and 14 pads on the right. The breakout pads contain a number of I/O pins that can be used with most of the EFM32PG26 Pearl Gecko MCU’s features. Additionally, the VMCU (main board power rail), 3V3 (LDO regulator output), and 5V power rails are also exposed on the pads.
The pin-routing on the Pearl Gecko MCU is very flexible, so most peripherals can be routed to any pin. However, pins may be shared between the breakout pads and other functions on the EFM32PG26 Explorer Kit. The table below includes an overview of the breakout pads and functionality that is shared with the kit.
Note: To use the alternate connection mentioned, the corresponding resistor needs to be mounted, and the existing resistor for the same breakout must be unmounted.

Connection

PB05

PA08

PA10

AIN0

GND

PC07

PC05

PA04

PA05

PC00

VREFN

VREFP

3V3

PB07

PC10

PD03

PD08

GND

VMCU

PC02

PC01

PC03

PC04

Table 3.1. Breakout Pads Pinout

Shared Feature

Peripheral Mapping

Alternate Connection

Left-side Breakout Pins

—

GPIO

PB10

—

GPIO

PB04

—

GPIO

PB09

—

AIN / GPIO

PB08

Ground

Board USB voltage

QWIIC_I2C_SDA, MIKROE_I2C_SDA

I2C_SDA / GPIO

PB06

QWIIC_I2C_SCL, MIKROE_I2C_SCL

I2C_SCL / GPIO

PA09

MIKROE_TX

UART_TX / GPIO

AIN3

MIKROE_RX

UART_RX / GPIO

AIN2

MIKROE_INT

EXT_INT / GPIO

AIN1

MIKROE_PWM

ADC VREF Negative Input / PWM

PA07

—

ADC VREF Positive Input

—

Board controller supply

Right-side Breakout Pins

—

GPIO

PC12

—

GPIO

PC11

—

GPIO

PD06

—

GPIO

PD07

Ground

EFM32PG26 voltage domain

MIKROE_MOSI

SPI_MOSI / AIN

PB11

MIKROE_MISO

SPI_MISO / AIN

PC13

MIKROE_SCK

SPI_SCLK

PD04

MIKROE_CS

SPI_CS

PD05

silabs.com | Building a more connected world.

Rev. 1.0 | 10

Connection

PC06

PD02

BOARD_ID_SCL

BOARD_ID_SDA

UG608: EFM32PG26 Explorer Kit User’s Guide
Hardware

Shared Feature

Peripheral Mapping

Alternate Connection

MIKROE_RST

RST / GPIO

PD09

MIKROE_AN

AIN / GPIO

PD10

Connected to Board Controller for identification of add-on boards.

3.6.2 Mini Simplicity Connector
The Mini Simplicity Connector (not mounted) is a 10-pin, 1.27 mm pitch connector that allows the use of an external debugger such as the one found on a Silicon Labs Wireless Starter Kit mainboard. The pinout of the connector on the board is described in the table below with the names being referenced from the EFM32PG26.
Table 3.2. Mini Simplicity Connector Pin Descriptions

Pin number 1
2 3 4 5 6 7 8 9 10

Function AEM
GND RST VCOM_RX VCOM_TX SWO SWDIO SWCLK PTI_FRAME PTI_DATA

Connection VMCU
GND RESET PB03 PB02 PA03 PA02 PA01 PD05 PD04

Description Target voltage on the debugged application. May be supplied and monitored by the AEM on an external debugger. Ground EFM32PG26 reset Virtual COM Rx Virtual COM Tx Serial Wire Output Serial Wire Data Serial Wire Clock Packet Trace Frame Packet Trace Data

Note: Since the EFM32PG26 Pearl Gecko MCU is designed primarily for low-power applications without integrated wireless capabilities, it does not support PTI functionality.

silabs.com | Building a more connected world.

Rev. 1.0 | 11

UG608: EFM32PG26 Explorer Kit User’s Guide
Hardware
3.6.3 MikroBUS Socket
The EFM32PG26 Explorer Kit features a mikroBUS socket compatible with mikroBUS add-on boards. MikroBUS add-on boards can expand the functionality of the kit with peripherals such as sensors and LCDs. Add-on boards follow the mikroBUS socket pin mapping and communicate with the on-kit EFM32PG26 through UART, SPI, or I2C. Several GPIOs are exposed on the mikroBUS socket. MikroBUS add-on boards can be powered by the 5V or VMCU power rails, which are available on the mikroBUS socket.
The pinout of the EFM32PG26 on the kit is made such that all required peripherals are available on the mikroBUS socket. The I2C signals are, however, shared with the Qwiic connector.
When inserting a mikroBUS add-on board, refer to the orientation notch on the EFM32PG26 Explorer Kit, shown in the figure below, to ensure correct orientation. Add-on boards have a similar notch that needs to be lined up with the one shown below.

Orientation notch

mikroBUS socket

Figure 3.6. mikroBUS Add-on Board Orientation The table below gives an overview of the mikroBUS socket pin connections to the EFM32PG26.
Table 3.3. mikroBUS Socket Pinout

mikroBUS Pin
Name

mikroBUS Pin Function

Analog

RST

Reset

SPI Chip Select

SCK

SPI Clock

MISO SPI Main Input Secondary Output

MOSI

SPI Main Output Secondary Input

PWM

PWM Output

INT Hardware Interrupt

UART Receive

UART Transmit

SCL

I2C Clock

SDA

I2C Data

Connection
PD02 PC06 PC04 PC03 PC01
PC02
PA07 PC00 PA05 PA04 PC05 PC07

Shared Feature
— — — — —
—
— — — — QWIIC_I2C_SCL QWIIC_I2C_SDA

Suggested Peripheral Mapping
IADC0 —
USARTx.CS USARTx.CLK USARTx.RX
USARTx.TX
TIMER0.CCx —
USARTx.RX USARTx.TX
I2Cx.SCL I2Cx.SDA

silabs.com | Building a more connected world.

Rev. 1.0 | 12

mikroBUS Pin
Name

mikroBUS Pin Function

3V3 VCC 3.3V power

VCC 5V power

GND Reference Ground

Connection
VMCU 5V GND

Shared Feature

UG608: EFM32PG26 Explorer Kit User’s Guide
Hardware
Suggested Peripheral Mapping

EFM32PG26 voltage domain Board USB voltage Ground

3.6.4 Qwiic Connector The EFM32PG26 Explorer Kit features a Qwiic connector compatible with Qwiic Connect System hardware. The Qwiic connector provides an easy way to expand the functionality of the EFM32PG26 Explorer Kit with sensors, LCDs, and other peripherals over the I2C interface. The Qwiic connector is a 4-pin polarized JST connector, which ensures the cable is inserted the right way. Qwiic Connect System hardware is daisy chain-able as long as each I2C device in the chain has a unique I2C address. Note: The Qwiic I2C lines are shared with the on-board I2C sensors.
The Qwiic connector and its connections to Qwiic cables and the EFM32PG26 are illustrated in the figure below.

Qwiic cable
GND VMCU SDA – PC07 SCL – PC05

Figure 3.7. Qwiic Connector The table below gives an overview of the Qwiic connections to the EFM32PG26.
Table 3.4. Qwiic Connector Pinout

Qwiic Pin Ground 3.3V SDA SCL

Connection GND VMCU PC07 PC05

Shared Feature

Suggested Peripherial Mapping

Ground

EFM32PG26 voltage domain

MIKROE_I2C_SDA

I2Cx.SDA

MIKROE_I2C_SCL

I2Cx.SCL

silabs.com | Building a more connected world.

Rev. 1.0 | 13

UG608: EFM32PG26 Explorer Kit User’s Guide
Hardware
3.6.5 Debug USB Type-C Connector
The debug USB port can be used for uploading code, debugging, and as a Virtual COM port. More information is available in section 4. Debugging.

silabs.com | Building a more connected world.

Rev. 1.0 | 14

UG608: EFM32PG26 Explorer Kit User’s Guide
Debugging
4. Debugging
The EFM32PG26 Explorer Kit contains an on-board SEGGER J-Link Debugger that interfaces to the target EFM32PG26 using the Serial Wire Debug (SWD) interface. The debugger allows the user to download code and debug applications running in the target EFM32PG26. Additionally, it provides a virtual COM port (VCOM) to the host computer that is connected to the target device’s serial port for general purpose communication between the running application and the host computer. The on-board debugger is accessible through the USB Type-C connector.
4.1 On-board Debugger
The on-board debugger is a SEGGER J-Link debugger running on an EFM32 Giant Gecko. The debugger is directly connected to the debug and VCOM pins of the target SiWG917.
When the debug USB cable is inserted, the on-board debugger is automatically activated and takes control of the debug and VCOM interfaces. This means that debug and communication will not work with an external debugger connected at the same time. The onboard LDO is also activated, providing power to the board.
4.2 Virtual COM Port
The virtual COM port is a connection to a UART of the target EFM32PG26 and allows serial data to be sent and received from the device. The on-board debugger presents this as a virtual COM port on the host computer that shows up when the USB cable is inserted.
Data is transferred between the host computer and the debugger through the USB connection, which emulates a serial port using the USB Communication Device Class (CDC). From the debugger, the data is passed on to the target device through a physical UART connection.
The serial format is 115200 bps, 8 bits, no parity, and 1 stop bit by default.
Note: Changing the baud rate for the COM port on the PC side does not influence the UART baud rate between the debugger and the target device.

silabs.com | Building a more connected world.

Rev. 1.0 | 15

UG608: EFM32PG26 Explorer Kit User’s Guide
Schematics, Assembly Drawings, and BOM
5. Schematics, Assembly Drawings, and BOM
Schematics, assembly drawings, and Bill of Materials (BOM) are available through Simplicity Studio when the kit documentation package has been installed. They are also available from the kit page on the Silicon Labs website: silabs.com.

silabs.com | Building a more connected world.

Rev. 1.0 | 16

6. Kit Revision History and Errata

UG608: EFM32PG26 Explorer Kit User’s Guide
Kit Revision History and Errata

6.1 Revision History
The kit revision can be found printed on the box label of the kit, as outlined in the figure below. The kit revision history is summarized in the table below.

EFM32PG26 Explorer Kit
PG26-EK2711A

18-11-24

2416000960 A00

Figure 6.1. Revision Info Table 6.1. Kit Revision History

Kit Revision A00

Released 18 November 2024

Description New kit introduction of PG26-EK2711A.

6.2 Errata There are no known errata at present.

silabs.com | Building a more connected world.

Rev. 1.0 | 17

7. Board Revision History and Errata

UG608: EFM32PG26 Explorer Kit User’s Guide
Board Revision History and Errata

7.1 Revision History The board revision can be found laser printed on the board, and the board revision history is summarized in the following table.
Table 7.1. Board Revision History

Revision A02

Released 13 November 2024

Description Initial production release.

7.2 Errata

Table 7.2. Board Errata

Board Revision A02

Problem

Description

PTI pins are not suppor- PTI pins are not supported for the ‘EFM32PG26B500F3200IM68-B.’ PTI con-

ted

nectivity will be removed from the design in future revisions.

silabs.com | Building a more connected world.

Rev. 1.0 | 18

8. Document Revision History
Revision 1.0 January 2025 · Initial document release.

UG608: EFM32PG26 Explorer Kit User’s Guide
Document Revision History

silabs.com | Building a more connected world.

Rev. 1.0 | 19

Simplicity Studio
One-click access to MCU and wireless tools, documentation, software, source code libraries & more. Available for Windows, Mac and Linux!

IoT Portfolio
www.silabs.com/IoT

SW/HW
www.silabs.com/simplicity

Quality
www.silabs.com/quality

Support & Community
www.silabs.com/community

Disclaimer Silicon Labs intends to provide customers with the latest, accurate, and in-depth documentation of all peripherals and modules available for system and software implementers using or intending to use the Silicon Labs products. Characterization data, available modules and peripherals, memory sizes and memory addresses refer to each specific device, and “Typical” parameters provided can and do vary in different applications. Application examples described herein are for illustrative purposes only. Silicon Labs reserves the right to make changes without further notice to the product information, specifications, and descriptions herein, and does not give warranties as to the accuracy or completeness of the included information. Without prior notification, Silicon Labs may update product firmware during the manufacturing process for security or reliability reasons. Such changes will not alter the specifications or the performance of the product. Silicon Labs shall have no liability for the consequences of use of the information supplied in this document. This document does not imply or expressly grant any license to design or fabricate any integrated circuits. The products are not designed or authorized to be used within any FDA Class III devices, applications for which FDA premarket approval is required or Life Support Systems without the specific written consent of Silicon Labs. A “Life Support System” is any product or system intended to support or sustain life and/or health, which, if it fails, can be reasonably expected to result in significant personal injury or death. Silicon Labs products are not designed or authorized for military applications. Silicon Labs products shall under no circumstances be used in weapons of mass destruction including (but not limited to) nuclear, biological or chemical weapons, or missiles capable of delivering such weapons. Silicon Labs disclaims all express and implied warranties and shall not be responsible or liable for any injuries or damages related to use of a Silicon Labs product in such unauthorized applications.
Trademark Information Silicon Laboratories Inc.®, Silicon Laboratories®, Silicon Labs®, SiLabs® and the Silicon Labs logo®, Bluegiga®, Bluegiga Logo®, EFM®, EFM32®, EFR, Ember®, Energy Micro, Energy Micro logo and combinations thereof, “the world’s most energy friendly microcontrollers”, Redpine Signals®, WiSeConnect , n-Link, EZLink®, EZRadio®, EZRadioPRO®, Gecko®, Gecko OS, Gecko OS Studio, Precision32®, Simplicity Studio®, Telegesis, the Telegesis Logo®, USBXpress® , Zentri, the Zentri logo and Zentri DMS, Z-Wave®, and others are trademarks or registered trademarks of Silicon Labs. ARM, CORTEX, Cortex-M3 and THUMB are trademarks or registered trademarks of ARM Holdings. Keil is a registered trademark of ARM Limited. Wi-Fi is a registered trademark of the Wi-Fi Alliance. All other products or brand names mentioned herein are trademarks of their respective holders.
Silicon Laboratories Inc. 400 West Cesar Chavez Austin, TX 78701 USA
www.silabs.com

Documents / Resources

SILICON LABS EFM32PG26 Explorer Kit [pdf] User Guide
EFM32PG26 Explorer Kit, EFM32PG26, Explorer Kit, Kit

References

User Manual

EFM32PG26 Explorer Kit

Specifications

Target Device

Kit Features

Software Support

Ordering Information

Product Usage Instructions

1. Introduction

1.1 Kit Contents

1.2 Getting Started

External Hardware Connection

FAQ

Q: Where can I find more information about the kit
contents?

Documents / Resources

References

Leave a comment

Cancel reply