UG162: Simplicity Commander Reference Guide

1 UG162: Simplicity Commander ReferenceGuideThis document describes how and when to use the Command-Line Interface (CLI) of Simplicity Commander . SimplicityCommander supports all EFR32 Wireless SoCs, EFR32 WirelessSoC modules (such as the MGM111 or MGM12P), EFM32 MCUfamilies, and EM3xx Wireless SOCs. EFM8 MCU families are notsupported at this document is intended for software engineers, hardware engineers, and releaseengineers. Silicon Labs recommends that you review this document to familiarize your-self with the CLI commands and their intended uses. You can refer to specific sectionsof this document to access operational information as needed. This document also in-cludes examples so you can gain an understanding of Simplicity Commander in document is up-to-date with Simplicity Commander version See section7.

2 Software Revision History for a list of new features and commands for previous ver-sions of the POINTS Introduces Simplicity Commander . Adds new features and commands. Describes the file formats supported bySimplicity Commander . Includes detailed syntax of all SimplicityCommander commands and examplecommand line inputs and | Building a more connected 2022 by Silicon LaboratoriesRev. Table of Contents1. File Format Motorola S-record (s37) File Update Image File Intel HEX-32 File General Installing Simplicity Command Line General Help (--help) .. Version (--version) .. Device (--device <device name>) .. J-Link Connection Debug Interface Graphical User Timestamp (--timestamp) .. Output and Exit EFR32 Custom Custom Token Creating Custom Token Defining Memory Token File Format Using Custom Token Using Custom Token Files in Any Security Security Access Challenge and Command Simplicity Commander Device Flashing Flash Image Flash Using IP Address without Verification and Flash Several Patch Patch Using Input Flash | Building a more connected | Flash Verification Memory Read Print Flash Dump Flash Contents to Token Print Dump Tokens to Dump Tokens from Image Generate C Header Files from Token Convert and Modify File Combine Two Define Specific Define Dump File Signing an Application for Secure Signing an Application for Secure

3 Boot using a Hardware Security Signing an Application for Secure Boot Signing using a Signature Created by a HardwareSecurity Adding a CRC32 for Gecko Bootloader .. Signing an Application for Secure Boot using an Intermediary Add a Trust Zone Decryption Extract Sections from ELF EBL Print EBL EBL Key EBL File EBL File Memory Usage Information from GBL GBL File GBL File Creation with Create a GBL File for Bootloader Creating a GBL File for Secure Element Creating a Signed and Encrypted GBL Upgrade Image File from an Creating a Partial Signed and Encrypted GBL Upgrade File for Use with a Hardware SecurityModule .. Creating a Signed GBL File Using a Hardware Security GBL File GBL Key Generating a Signing Generate a Signing Key Using a Hardware Security Creating a Signed GBL File Using a Hardware Security Create a GBL File from an ELF File.

4 Create an Encrypted GBL File with an Unencrypted Secure Element Upgrade Create a GBL File with Version Kit Utility Firmware | Building a more connected | Kit Information Adapter Reset Adapter Debug Mode List Adapter IP Configuration Adapter DHCP Set Static IP Configuration Command .. Device Erase Erase Erase Erase Pages in Address Device Lock and Protection Debug Debug Write Protect Flash Write Protect Flash Disable Write Device Utility Device Information Command .. Device Reset Device Recovery Device Z-Wave QR Code Command .. External SPI Flash Erase External SPI Flash Command .. Read External SPI Flash Command .. Write External SPI Flash Command .. Advanced Energy Monitor Measure Serial Wire Output Read Configure SWO Read SWO Until Read SWO Until a Marker Is Dump Hex Encoded SWO NVM3 Read NVM3 Data From a Parse NVM3 Initialize NVM3 Area in a Write NVM3 Data Using a Text Write NVM3 Data Using CLI CTUNE CTUNE Get CTUNE Set CTUNE Autoset Security Get Device Generate Key Write Public Key to Read Public Key from | Building a more connected | Configure Lock Lock Debug Secure Debug Disable Device Erase using Secure Disable Device Roll Generate Example Authorization Generate Access Generate Unsigned Command Generate Example Configuration Write User Read User Get Security Store Write AES Decryption Read

5 Device Vault Device Util Key Generating a Signing Key to Generate Sign Verify Signature .. Application Print Section Header Information from an ELF OTA Create an OTA Bootloader Create a Null OTA Print OTA File Post-Build Execute a Project Post-Build Software Revision Version Version Version Version Version Version Version Version Version Version Version | Building a more connected | Version Version Version Version Version Version Version Version Version Version Version Version | Building a more connected | 61. IntroductionSimplicity Commander is a single, all-purpose tool to be used in a production environment. It is invoked using a simple Command LineInterface (CLI) that is also scriptable.

6 Simplicity Commander enables customers to complete these essential tasks: Flash their own applications. Configure their own applications. Create binaries for Commander is designed to support the Silicon Labs Wireless STK and STK primary intended audience for this document is software engineers, hardware engineers, and release engineers who are familiarwith programming the EFR32 and EM3xx. This Reference Guide describes how to use the Simplicity Commander CLI. It provides gener-al information on file formats supported by Simplicity Commander and the Silicon Labs bootloaders, and includes details on using theSimplicity Commander commands, options, and arguments. It also includes example command line inputs and outputs so you can gaina better understanding of how to use Simplicity Commander : Simplicity Commander Reference | Building a more connected | 72.

7 File Format OverviewSimplicity Commander works with different file formats: .bin, .s37, .ebl, .gbl, and .hex. Each file format serves a slightly different pur-pose. The file formats supported by Simplicity Commander are summarized Motorola S-record (s37) File FormatSilicon Labs uses the Simplicity Studio as its Integrated Development Environment (IDE) and leverages the IAR Embedded Workbenchfor ARM platforms. This tool combination produces Motorola S-record files, s37 specifically, as its output. (For more information on Mo-torola S-record file format, see ) In Silicon Labs development, an s37 file contains programmingdata about the built firmware and generally only represents a single piece of firmware application firmware or bootloader firmware but not both. An application image in s37 format can be loaded into a supported target device using the Simplicity Commander flashcommand.

8 The s37 format can represent any combination of any byte of flash in the device. The Simplicity Commander convert com-mand can also be used to read multiple s37 files and hex files; output an s37 file for combining multiple files into a single file; andmodify individual bytes of a Update Image File FormatsAn update image file provides an efficient and fault-tolerant image format for use with Silicon Labs bootloaders to update an applicationwithout the need for special programming devices. Two image formats are supported: Gecko Bootloader (GBL) format for use with theSilicon Labs Gecko Bootloader introduced for use with EFR32 devices and Ember Bootloader (EBL) format for use with legacy Emberbootloaders. See : Application Development Fundamentals: Bootloading for more details about these image file formats andbootloader use with different image files are generated by the Simplicity Commander gbl create or ebl create command.

9 These formats can only repre-sent firmware images; they cannot be used to capture Simulated EEPROM token data (as described by AN703: Using Simulated EE-PROM Version 1 and Version 2 for the EM35x and EFR32 Series 1 SoC Platforms). GBL upgrade files may contain data that getsflashed outside the main can receive an update image file either over-the-air (OTA) or via a supported peripheral interface, such as a serial port,and reprogram the flash in place. Update image files are generally used in later stage development and for upgrading manufactureddevices in the development, bootloaders should be loaded onto the device using the .s37 or .hex file format. If the Gecko Bootloader with sup-port for in-field bootloader upgrades is used, it is possible to perform a bootloader upgrade using a GBL update image.

10 For other boot-loaders or file formats, do not attempt to load a bootloader image onto the device as an update : Simplicity Commander Reference GuideFile Format | Building a more connected | Intel HEX-32 File FormatProduction programming uses the standard Intel HEX-32 file format. The normal development process for EFR32 chips involves creat-ing and programming images using the s37 and ebl file formats. The s37 and ebl files are intended to hold applications, bootloaders,manufacturing data, and other information to be programmed during development. The s37 and ebl files, though, are not intended tohold a single image for an entire chip. For example, it is often the case that there is an s37 file for the bootloader, an s37 file for theapplication, and an s37 file for manufacturing data.