SILICON LABS UG255 EFM32HG Gecko Starter Kit User Guide

SILICON LABS UG255 EFM32HG Gecko Starter Kit

Specifications:

• Target Device: EFM32HGTM Gecko Microcontroller
• Kit Features: Sensors, peripherals, debugger, energy monitoring tool
• Software Support: Available for application development

Product Usage Instructions

1. Getting Started

Begin by connecting the SLSTK3400A Starter Kit to a power source using the provided cables.

2. Kit Block Diagram

Refer to the block diagram to understand the layout and connections of the various components on the kit.

3. Kit Hardware Layout

Familiarize yourself with the physical layout of the kit and locate the different connectors and components.

4. Power Supply and Reset

Ensure proper power selection for the MCU, board controller, and EFM32HG reset. Follow the guidelines provided in the manual.

5. Advanced Energy Monitor

Utilize the energy monitor to track power consumption and optimize energy usage in your applications.

6. On-board debugger

Explore the different debug modes available and learn how to debug during battery operation for efficient troubleshooting.

7. Kit Configuration and Upgrades

Stay updated with firmware upgrades to enhance the performance and capabilities of your EFM32HG Gecko applications.

FAQ

• Q: Can I use the SLSTK3400A Starter Kit with external applications?
  • A: Yes, the kit can be used with external applications as it features a fully-featured debugger and energy monitoring tool.
• Q: How do I upgrade the firmware on the kit?
  • A: To upgrade the firmware, refer to section 9.1 in the user manual for detailed instructions on firmware upgrades.

Product Overview

The SLSTK3400A is an excellent starting point to become familiar with the EFM32HG™ Gecko Microcontroller. The Starter Kit contains sensors and peripherals demonstrating some of the EFM32HG’s many capabilities. The kit provides all the necessary tools for developing an EFM32HG Gecko application

TARGET DEVICE

• EFM32HG Gecko Microcontroller
• (EFM32HG322F64G-C-QFP48)
• CPU: 32-bit ARM® Cortex-M0+®
• Memory: 64 kB flash and 8 kB RAM

KIT FEATURES

• USB connectivity
• Advanced Energy Monitor (AEM)
• SEGGER J-Link on-board debugger
• Debug multiplexer supporting external hardware as well as on-board MCU
• Ultra-low power 128×128 pixel Memory LCD
• Capacitive Touch Pads
• 20-pin 2.54 mm header for expansion boards
• Breakout pads for direct access to I/O pins
• Power sources include USB and CR2032 coin cell battery

SOFTWARE SUPPORT

• Simplicity Studio™
• IAR Embedded Workbench
• Keil MDK

Introduction

Description

The SLSTK3400A is an ideal starting point for application development on the EFM32HG Gecko Microcontrollers. The board features sensors and peripherals, demonstrating some of the many capabilities of the EFM32HG Gecko Microcontroller. Additionally, the board is a fully featured debugger and energy monitoring tool that can be used with external applications.

Features

• EFM32HG Gecko Microcontroller
• 64 kB Flash
• 8 kB RAM
• QFP48 package
• Advanced Energy Monitoring system for precise current and voltage tracking
• Integrated Segger J-Link USB debugger/emulator with the possiblity to debug external Silicon Labs devices
• 20-pin expansion header
• Breakout pads for easy access to I/O pins
• Power sources include USB and CR2032 battery
• Ultra-low-power 128×128 pixel Memory-LCD
• 2 push buttons and 2 user LEDs connected to EFM32 for user interaction
• 2 capacitive touch pads for user interaction
• Crystals for LFXO and HFXO: 32.768 kHz and 24.000 MHz.

Getting Started

Detailed instructions for how to get started with your new SLSTK3400A can be found on the Silicon Labs Web pages: https://www.silabs.com/mcu/32-bit/efm32 -happy-gecko

Kit Block Diagram

An overview of the EFM32 Happy Gecko Starter Kit is shown in the figure below .

Kit Hardware Layout

The EFM32 Happy Gecko Starter Kit layout is shown below.

Connectors

Breakout Pads

Most of the EFM32HG’s GPIO pins are available on two pin header rows at the top and bottom edges of the board. These have a standard 2.54 mm pitch, and pin headers can be soldered in if required. In addition to the I/O pins, connections to power rails and ground are also provided. Note that some of the pins are used for kit peripherals or features and may not be available for a custom application without tradeoffs. The figure below shows the pinout of the breakout pads and the pinout of the EXP header on the right edge of the board. The EXP header is further explained in the next section. The breakout pad connections are also printed in silkscreen next to each pin for easy reference .

The table below shows the pin connections of the breakout pads. It also shows which kit peripherals or features are connected to the different pins.

Table 4.1. Bottom Row (J101) Pinout

Pin| EFM32HG I/O

Pin

| Shared Feature|  | Pin| EFM32HG I/O

Pin

| Shared Feature
---|---|---|---|---|---|---
1| VMCU| EFM32HG voltage domain (measured by AEM)|  | 2| VMCU| EFM32HG voltage domain (measured by AEM)
3| GND| Ground|  | 4| GND| Ground
5| PA0| VCOM_RX|  | 6| PC0| EXP3
7| PA1| EXP13|  | 8| PC1| EXP5
Pin| EFM32HG I/O

Pin

| Shared Feature|  | Pin| EFM32HG I/O

Pin

| Shared Feature
---|---|---|---|---|---|---
9| PA2| EXP9|  | 10| PC2| EXP7
11| NC| –|  | 12| NC| –
13| PA8| DISP_ENABLE|  | 14| PC8| SENSOR_ENABLE
15| PA9| VCOM_ENABLE|  | 16| PC9| BUTTON0
17| PA10| DISP_CS|  | 18| PC10| BUTTON1
19| NC| –|  | 20| NC| –
21| PB11| EXP11|  | 22| NC| –
23| NC| –|  | 24| NC| –
25| NC| –|  | 26| NC| –
27| NC| –|  | 28| NC| –
29| GND| Ground|  | 30| GND| Ground
31| 3V3| Board controller supply|  | 32| 3V3| Board controller supply

Table 4.2. Top Row (J102) Pinout

Pin| EFM32HG I/O

Pin

| Shared Feature|  | Pin| EFM32HG I/O

Pin

| Shared Feature
---|---|---|---|---|---|---
1| 5V| Board USB voltage|  | 2| 5V| Board USB voltage
3| GND| Ground|  | 4| GND| Ground
5| PF0| DEBUG_SWCLK|  | 6| PD4| EXP12
7| PF1| DEBUG_SWDIO|  | 8| PD5| EXP14
9| PF2| VCOM_TX|  | 10| PD6| EXP16, SENSOR_I2C_SDA
11| PF3| DISP_COM|  | 12| PD7| EXP15, SENSOR_I2C_SCL
13| PF4| LED0|  | 14| NC| –
15| PF5| LED1|  | 16| PE10| EXP4, DISP_SI
17| NC| –|  | 18| PE11| EXP6
19| NC| –|  | 20| PE12| EXP8, DISP_SCLK
21| NC| –|  | 22| PE13| EXP10
23| NC| –|  | 24| NC| –
25| NC| –|  | 26| NC| –
27| NC| –|  | 28| NC| –
29| GND| Ground|  | 30| GND| Ground
31| 3V3| Board controller supply|  | 32| 3V3| Board controller supply

EXP Header

On the right side of the board, an angled 20-pin EXP header is provided to allow connection of peripherals or plugin boards. The connector contains a number of I/O pins that can be used with most of the EFM32HG Gecko’s features. Additionally, the VMCU, 3V3, and 5V power rails are also exposed. The connector follows a standard which ensures that commonly used peripherals such as a SPI, UART, and I2C bus are available on  fixed locations on the connector. The rest of the pins are used for general purpose I/O. This layout allows the definition of expansionboards that can plug into a number of different Silicon Labs kits. The figure below shows the EXP header pin assignment for the EFM32 Happy Gecko Starter Kit. Because of limitations in the number of available GPIO pins, some of the EXP header pins are shared with kit features

Table 4.3. EXP Header Pinout

Pin| Connection| EXP Header Function| Shared Feature| Peripheral Mapping
---|---|---|---|---
20| 3V3| Board controller supply
18| 5V| Board controller USB voltage
16| PD6| I2C_SDA| ADC0_CH6| I2C0_SDA
14| PD5| UART_RX| ADC0_CH5| LEUART0_RX
12| PD4| UART_TX| ADC0_CH4| LEUART0_TX
10| PE13| SPI_CS| ADC0_CH1| USART0_CS
8| PE12| SPI_SCLK| ADC0_CH0| USART0_CLK
6| PE11| SPI_MISO| –| USART0_RX
4| PE10| SPI_MOSI| –| USART0_TX
2| VMCU| EFM32HG voltage domain, included in AEM measurements.

19| BOARD_ID_SDA| Connected to Board Controller for identification of add-on boards.
17| BOARD_ID_SCL| Connected to Board Controller for identification of add-on boards.
15| PD7| I2C_SCL| ADC0_CH7| I2C0_SCL
13| PA1| GPIO| –| –
11| PB11| IDAC_OUT| –| IDAC0_OUT
9| PA2| GPIO| –| –
Pin| Connection| EXP Header Function| Shared Feature| Peripheral Mapping
---|---|---|---|---
7| PC2| –| ACMP0_CH2| –
5| PC1| –| ACMP0_CH1| –
3| PC0| –| ACMP0_CH0| –
1| GND| Ground

Debug Connector (DBG)

The Debug Connector serves a dual purpose, depending on the “debug mode”, which can be set up using Simplicity Studio. In the “Debug IN” mode, this connector allows an external debug emulator to be used with the on-board EFM32HG. In the “Debug OUT” mode, this connector allows the kit to be used as a debugger towards an external target. In the “Debug MCU” (default) mode, this connector is isolated from the debug interface of both the board controller and the on-board target device. Because this connector is automatically switched to support the different operating modes, it is only available when the board controller is powered (J-Link USB cable connected). If debug access to the target device is required when the board controller is unpowered, connect directly to the appropriate breakout pins. The connector pinout follows that of the standard ARM Cortex Debug+ETM 19-pin connector. The pinout is described in detail below. Note that when using the on-board debugger to debug an MCU on an external board, JTAG and ETM functionality are only available if the target device supports it.

Note that the pinout matches the pinout of an ARM Cortex Debug+ETM connector, but these are not fully compatible because pin 7 is physically removed from the Cortex Debug+ETM connector. Some cables have a small plug that prevent them from being used when this pin is present. If this is the case, remove the plug or use a standard 2×10 1.27 mm straight cable instead.

Table 4.4. Debug Connector Pin Descriptions

between target and debugger.
2| TMS / SDWIO / C2D| JTAG test mode select, Serial Wire data, or C2 data
4| TCK / SWCLK / C2CK| JTAG test clock, Serial Wire clock, or C2 clock
6| TDO/SWO| JTAG test data out or Serial Wire Output
8| TDI / C2Dps| JTAG test data in or C2D “pin sharing” function
10| RESET / C2CKps| Target device reset or C2CK “pin sharing” function
12| TRACECLK| ETM Trace Clock
14| TRACED0| ETM Trace Data 0
16| TRACED1| ETM Trace Data 1
18| TRACED2| ETM Trace Data 2
20| TRACED3| ETM Trace Data 3
9| Cable detect| Connect to ground
11, 13| NC| Not connected
3, 5, 15, 17, 19| GND|

Simplicity Connector

The Simplicity Connector featured on the EFM32 Happy Gecko Starter Kit enables advanced debugging features such as the AEM and Virtual COM port to be used towards an external target. The pinout is illustrated in the figure below.

The signal names in the figure and the pin description table are referenced from the board controller. This means that VCOM_TX should be connected to the RX pin on the external target, VCOM_RX to the target’s TX pin, VCOM_CTS to the target’s RTS pin, and VCOM_RTS to the target’s CTS pin.
Note: Current drawn from the VMCU voltage pin is included in the AEM measurements, while the 3V3 and 5V voltage pins are not. To monitor the current consumption of an external target with the AEM, put the on-board MCU in its lowest energy mode to minimize its impact on the measurements.

Table 4.5. Simplicity Connector Pin Descriptions

Power Supply and Reset

MCU Power Selection

The EFM32HG on the Starter Kit can be powered by one of these sources:

• The debug USB cable
• 3 V coin cell battery

The power source for the MCU is selected with the slide switch in the lower left corner of the Starter Kit. The figure below shows how the different power sources can be selected with the slide switch.

With the switch in the AEM position, a low noise 3.3 V LDO on the Starter Kit is used to power the EFM32HG. This LDO is again powered from the debug USB cable. The Advanced Energy Monitor is now connected in series, allowing accurate high-speed current measurements and energy debugging/profiling. With the switch in the BAT position, a 20 mm coin cell battery in the CR2032 socket can be used to power the device. With the switch in this position, no current measurements are active. This is the recommended switch position when powering the MCU with an external power source.

Note: The Advanced Energy Monitor can only measure the current consumption of the EFM32HG when the power selection switch is in the AEM position.

Board Controller Power

The board controller is responsible for important features, such as the debugger and the AEM, and is powered exclusively through the USB port in the top left corner of the board. This part of the kit resides on a separate power domain, so a different power source can be selected for the target device while retaining debugging functionality. This power domain is also isolated to prevent current leakage from the target power domain when power to the board controller is removed. The board controller power domain is not influenced by the position of the power switch. The kit has been carefully designed to keep the board controller and the target power domains isolated from each other as one of them powers down. This ensures that the target EFM32HG device will continue to operate in the BAT mode.

EFM32HG Reset

The EFM32HG MCU can be reset by a few different sources:

• A user pressing the RESET button
• The on-board debugger pulling the #RESET pin low
• An external debugger pulling the #RESET pin low

In addition to the reset sources mentioned above, a reset to the EFM32HG will also be issued during board controller boot-up. This means that removing power to the board controller (unplugging the J-Link USB cable) will not generate a reset but plugging the cable back in will as the board controller boots up.

Peripherals

The Starter Kit has a set of peripherals that showcase some of the EFM32HG features.
Note that most EFM32HG I/Os routed to peripherals are also routed to the breakout pads or the EXP header, which must be taken into consideration when using these I/Os.

Push Buttons and LEDs

The kit has two user push buttons marked BTN0 and BTN1. They are connected directly to the EFM32HG and are debounced by RC filters with a time constant of 1 ms. The buttons are connected to pins PC9 and PC10. The kit also features two yellow LEDs marked LED0 and LED1 that are controlled by GPIO pins on the EFM32HG. The LEDs are connected to pins PF4 and PF5 in an active-high configuration.

Memory LCD-TFT Display

A 1.28-inch SHARP Memory LCD-TFT is available on the kit to enable interactive applications to be developed. The display has a high resolution of 128 x 128 pixels and consumes very little power. It is a reflective monochrome display, so each pixel can only be light or dark, and no backlight is needed in normal daylight conditions. Data sent to the display is stored in the pixels on the glass, which means no continuous refreshing is required to maintain a static image. The display interface consists of a SPI-compatible serial interface and some extra control signals. Pixels are not individually addressable, instead data is sent to the display one line (128 bits) at a time. The Memory LCD-TFT display is shared with the kit’s board controller, allowing the board controller application to display useful information when the user application is not using the display. The user application always controls ownership of the display with the

DISP_ENABLE signal:

• DISP_ENABLE = LOW: The board controller has control of the display
• DISP_ENABLE = HIGH: The user application (EFM32HG) has control of the display
• Power to the display is sourced from the target application power domain when the EFM32HG controls the display and from the board controller’s power domain when the DISP_ENABLE line is low. Data is clocked in on DISP_SI when DISP_CS is high, and the clock is sent on DISP_SCLK. The maximum supported clock speed is 1.1 MHz.
• DISP_EXTCOMIN is the “COM Inversion” line. It must be pulsed periodically to prevent static build-up in the display itself. Refer to theLS013B7DH03 documentation for more information on driving the display

Capacitive Touch Pads

Two touch pads are available, TOUCH0 and TOUCH1, utilizing the capacitive touch capability of the EFM32HG. They are located on the lower right side of the board, beneath the EFM32HG. The pads are connected to PC3 and PC4 .

The capacitive touch pads work by sensing changes in the capacitance of the pads when touched by a human finger. Sensing the changes in capacitance involves setting up the touch pad as part of an RC relaxation oscillator using the EFM32HG’s analog comparator and then counting the number of oscillations during a fixed period of time.

Si7021 Relative Humidity and Temperature Sensor

The Si7021 I2C relative humidity and temperature sensor is a monolithic CMOS IC integrating humidity and temperature sensor elements, an analog-to-digital converter, signal processing, calibration data, and an I2C Interface. The patented use of industry-standard,  low-K polymeric dielectrics for sensing humidity enables the construction of low-power, monolithic CMOS Sensor ICs with low drift andhysteresis, and excellent long term stability. The humidity and temperature sensors are factory-calibrated and the calibration data is stored in the on-chip non-volatile memory. This ensures that the sensors are fully interchangeable with no recalibration or software changes required. The Si7021 is available in a 3×3 mm DFN package and is reflow solderable. It can be used as a hardware and software-compatible drop-in upgrade for existing RH/temperature sensors in 3×3 mm DFN-6 packages, featuring precision sensing over a wider range and lower power consumption. The optional, factory- installed cover offers a low profile, convenient means of protecting the sensor during assembly (e.g., reflow soldering) and throughout the life of the product, excluding liquids (hydrophobic/oleophobic) and particulates.The Si7021 offers an accurate, low-power, factory-calibrated digital solution ideal for measuring humidity, dew point, and temperature in applications ranging from HVAC/R and asset tracking to industrial and consumer platforms. The I2C bus used for the Si7021 is shared with the EXP header. The temperature sensor is normally isolated from the I2C line. To use the sensor, PC8 must be set high. When enabled, the sensor’s current consumption is included in the AEM measurements

Refer to the Silicon Labs web pages for more information: http://www.silabs.com/humidity-sensors

USB Micro-AB Connector

The SLSTK3400A board is equipped with a USB Micro-AB connector interfacing with the EFM32HG’s USB peripheral. This setup allows the development and evaluation of applications using USB in both host and device mode. For host mode, the board can supply 5V power to the USB VBUS if the board itself has been powered using the debug-USB connector. The VBUS power switch also provides an overcurrent flag which can be read to detect if a connected device draws too much current. The secondary AEM channel (see chapter on Advanced Energy Monitoring) is placed between the USB connector and the EFM32HG, and allows monitoring of the current sourced from the USB cable when developing a bus-powered USB application. The AEM circuit includes an input filter and a sense resistor on the VBUS line, which could potentially influence USB compliance testing. If it is required, the AEM circuit can be bypassed by removing some components and shorting a footprint on the PCB. More details about this can be found in the schematic. The secondary AEM channel will only measure current consumption when the power selector switch is set to the “USB” position. The EFM32 has an internal LDO regulator that powers the USB PHY inside the chip. 5 V from VBUS is applied to the USB_VREGI pin, and the output is decoupled on the USB_VREGO pin. When the power select switch is set to the USB position, USB_VREGO is connected to the VMCU net, which powers the chip and all peripherals in the target voltage domain. When the J-Link USB cable is inserted, it is possible to monitor the current that supplies the USB PHY, the EFM32 device, and all user peripherals on the board.

Virtual COM Port

An asynchronous serial connection to the board controller is provided for application data transfer between a host PC and the target EFM32HG, which eliminates the need for an external serial port adapter

The Virtual COM port consists of a physical UART between the target device and the board controller, and a logical function in the board controller that makes the serial port available to the host PC over USB. The UART interface consists of two pins and an enablesignal.

Table 6.1. Virtual COM Port Interface Pins

board controller

Note: The VCOM port is only available when the board controller is powered, which requires the J-Link USB cable to be inserted.

Advanced Energy Monitor

Usage

The Advanced Energy Monitor (AEM) data is collected by the board controller and can be displayed by the Energy Profiler, available through Simplicity Studio. By using the Energy Profiler, current consumption and voltage can be measured and linked to the actual code running on the EFM32HG in realtime.

Theory of Operation

To accurately measure current ranging from 0.1 μA to 47 mA (114 dB dynamic range), a current sense amplifier is utilized together with a dual gain stage. The current sense amplifier measures the voltage drop over a small series resistor. The gain stage further amplifies this voltage with two different gain settings to obtain two current ranges. The transition between these two ranges occurs around 250 μA. Digital filtering and averaging is done within the board controller before the samples are exported to the Energy Profiler application.During kit startup, an automatic calibration of the AEM is performed, which compensates for the offset error in the sense amplifiers .

Secondary AEM Channel

The EFM32 Happy Gecko Starter Kit contains a secondary AEM channel in addition to the default one. This secondary channel has a sense resistor on the USB VBUS line connected to the EFM32HG’s USB regulator input, which allows energy monitoring of a bus powered USB application, showcasing the EFM32HG Gecko’s low energy USB peripheral. To use the secondary AEM channel, set the power switch to the “USB” position so that the EFM32HG is configured as a bus powered device with the internal USB LDO regulator powering the device’s VDD rail. The board controller monitors the switch position and performs an automatic switch-over and calibration when the USB position is selected and a valid voltage is present on the VBUS rail. Both the current and the voltage measurement will now show the VBUS supply instead of the normal 3.3 V supply.

Note that the recalibration that occurs when switching between the “USB” and “AEM” modes on the power switch causes the target EFM32HG to lose power for a few seconds.

Accuracy and Performance

The AEM is capable of measuring currents in the range of 0.1 μA to 47 mA. For currents above 250 μA, the AEM is accurate within 0.1 mA. When measuring currents below 250 μA, the accuracy increases to 1 μA. Although the absolute accuracy is 1 μA in the sub 250 μA range, the AEM is able to detect changes in the current consumption as small as 100 nA. The AEM produces 6250 current samples per second.

On-Board Debugger

The SLSTK3400A contains an integrated debugger, which can be used to download code and debug the EFM32HG. In addition to programming the EFM32HG on the kit, the debugger can also be used to program and debug external Silicon Labs EFM32, EFM8, EZR32, and EFR32 devices.

The debugger supports three different debug interfaces used with Silicon Labs devices:

• Serial Wire Debug, which is used with all EFM32, EFR32, and EZR32 devices
• JTAG, which can be used with EFR32 and some EFM32 devices
• C2 Debug, which is used with EFM8 devices

To ensure accurate debugging, use the appropriate debug interface for your device. The debug connector on the board supports all three of these modes.

Debug Modes

To program external devices, use the debug connector to connect to a target board and set the debug mode to [Out]. The same connector can also be used to connect an external debugger to the EFM32HG MCU on the kit by setting debug mode to [In]. Selecting the active debug mode is done in Simplicity Studio.

• Debug MCU: In this mode, the on-board debugger is connected to the EFM32HG on the kit.
• Debug OUT: In this mode, the on-board debugger can be used to debug a supported Silicon Labs device mounted on a custom board.
• Debug IN: In this mode, the on-board debugger is disconnected and an external debugger can be connected to debug the EFM32HG on the kit.

Note: For “Debug IN” to work, the kit board controller must be powered through the Debug USB connector.

Debugging During Battery Operation

When the EFM32HG is battery-powered and the J-Link USB is still connected, the on-board debug functionality is available. If the USB power is disconnected, the Debug IN mode will stop working. If debug access is required when the target is running off another energy source, such as a battery, and the board controller is powered down, make direct connections to the GPIOs used for debugging, which are exposed on the breakout pads.

Kit Configuration and Upgrades

The kit configuration dialog in Simplicity Studio allows you to change the J-Link adapter debug mode, upgrade its firmware, and change other configuration settings. To download Simplicity Studio, go to silabs.com/simplicity. In the main window of the Simplicity Studio’s Launcher perspective, the debug mode and firmware version of the selected J-Link adapter are shown. Click the [Change] link next to any of these settings to open the kit configuration dialog.

Firmware Upgrades

You can upgrade the kit firmware through Simplicity Studio. Simplicity Studio will automatically check for new updates on startup. You can also use the kit configuration dialog for manual upgrades. Click the [Browse] button in the [Update Adapter] section to select the correct file ending in .emz. Then, click the [Install Package] button.

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.

Kit Revision History and Errata

Revision History

The kit revision can be found printed on the box label of the kit, as outlined in the figure below.

Table 11.1. Kit Revision History

(BRD2012B_A01).
C01| 18 November 2019| Upgraded board controller section.
B00| 28 September 2016| Coin-cell battery no longer included with kit due to shipping restrictions.
A04| 20 November 2015| Updated board revision to B01 – Added input filter for secondary AEM channel.
A03| 30 April 2015| Updated board revision to B01 – Added input filter for secondary AEM channel.
A02| 20 March 2015| Updated board revision to B00 – Pinout changes related to internal operation of the Board Controller
A01| 2 February 2015| Initial Kit Revision.

Errata

There are no known errata at present.

Document Revision History

• 2.00
  March, 2024
  Updated user guide to reflect new major board revision (BRD2012B).

• 1.02
  March, 2020
  Updated document to current template.

• 1.01
  November, 2016
  Updated document title.

• 1.00
  April, 2015
  Initial document version

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. Note: This content may contain offensive terminology that is now obsolete. Silicon Labs is replacing these terms with inclusive language wherever possible. For more information, visit www.silabs.com/about-us/inclusive- lexicon-project 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, ThreadArch®, 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

References

• Silicon Labs
• Simplicity Studio - Silicon Labs
• Silicon Labs
• Relative Humidity and Temperature Sensors - Silicon Labs
• Simplicity Studio - Silicon Labs
• EFM32 32-bit USB Low Power Microcontroller - Silicon Labs

Read User Manual Online (PDF format)

Download This Manual (PDF format)

Download this manual  >>