Apache mynewt

Clone this repo:
  1. 03242ec Allow build when no FLASH_AREA_IMAGE_1 is defined by Jerzy Kasenberg · 8 weeks ago master
  2. 545f2b2 cborattr/test: Add type casting for 64-bit architecture by Michal Gorecki · 11 months ago
  3. 1c9b642 Mcumgr 0.4.0 release by Szymon Janc · 10 months ago mcumgr_0_4_0_tag
  4. f6d58e2 Use syscfg settings for sysinit stage numbers by Philip Burkhardt · 1 year, 4 months ago
  5. 58e444d Update install instructions for go >=1.18 by Alexander Leris · 1 year, 2 months ago


This is mcumgr, version 0.4.0

mcumgr is a management library for 32-bit MCUs. The goal of mcumgr is to define a common management infrastructure with pluggable transport and encoding components. In addition, mcumgr provides definitions and handlers for some core commands: image management, file system management, and OS management.

mcumgr is operating system and hardware independent. It relies on hardware porting layers from the operating system it runs on. Currently, mcumgr runs on both the Apache Mynewt and Zephyr operating systems.

Getting started

For tips on using mcumgr with your particular OS, see the appropriate file from the list below:


To use mcumgr's image management support, your device must be running version 1.1.0 or later of the MCUboot boot loader. The other mcumgr features do not require MCUboot.

Command line tool

The mcumgr command line tool is available at: https://github.com/apache/mynewt-mcumgr-cli. The command line tool requires Go 1.12 or later. Once Go is installed and set up on your system, you can install the mcumgr CLI tool by issuing the following go get or go install command, depending on your Go version:

Go version < 1.18

$ go get github.com/apache/mynewt-mcumgr-cli/mcumgr

Go version >= 1.18

$ go install github.com/apache/mynewt-mcumgr-cli/mcumgr@latest

The mcumgr tool allows you to manage devices running an mcumgr server.


The mcumgr stack has the following layout:

|             <command handlers>            |
|                   mgmt                    |
|           <transfer encoding(s)>          |
|               <transport(s)>              |

Items enclosed in angled brackets represent generic components that can be plugged into mcumgr. The items in this stack diagram are defined below:

  • Command handler: Processes incoming mcumgr requests and generates corresponding responses. A command handler is associated with a single command type, defined by a (group ID, command ID) pair.
  • mgmt: The core of mcumgr; facilitates the passing of requests and responses between the generic command handlers and the concrete transports and transfer encodings.
  • Transfer encoding: Defines how mcumgr requests and responses are encoded on the wire.
  • Transport: Sends and receives mcumgr packets over a particular medium.

Each transport is configured with a single transfer encoding.

As an example, the sample application smp_svr uses the following components:

  • Command handlers:
    • Image management (img_mgmt)
    • File system management (fs_mgmt)
    • Log management (log_mgmt)
    • OS management (os_mgmt)
  • Transfer/Transports protocols:
    • SMP/Bluetooth
    • SMP/Shell

yielding the following stack diagram:

| img_mgmt |  fs_mgmt | log_mgmt |  os_mgmt |
|                   mgmt                    |
|         SMP         |         SMP         |
|      Bluetooth      |        Shell        |

Command definition

An mcumgr request or response consists of the following two components:

  • mcumgr header
  • CBOR key-value map

How these two components are encoded and parsed depends on the transfer encoding used.

The mcumgr header structure is defined in mgmt/include/mgmt/mgmt.h as struct mgmt_hdr.

The contents of the CBOR key-value map are specified per command type.

Supported transfer encodings

Mcumgr comes with one built-in transfer encoding: Simple Management Protocol (SMP). SMP requests and responses have a very basic structure. For details, see the comments at the top of smp/include/smp/smp.h.

Supported transports

The mcumgr project defines two transports:

Implementations, being hardware- and OS-specific, are not included.


Information and documentation for mcumgr is stored within the source.

For more information in the source, here are some pointers:

  • cborattr: Used for parsing incoming mcumgr requests. Destructures mcumgr packets and populates corresponding field variables.
  • cmd: Built-in command handlers for the core mcumgr commands.
  • ext: Third-party libraries that mcumgr depends on.
  • mgmt: Code implementing the mgmt layer of mcumgr.
  • samples: Sample applications utilizing mcumgr.
  • smp: The built-in transfer encoding: Simple management protocol.


Developers welcome!