commit | 0ba791a8d336bc751598be36099998439184b033 | [log] [tgz] |
---|---|---|
author | Naveen Kaje <naveen.kaje@juul.com> | Wed Oct 28 10:26:33 2020 -0500 |
committer | Fabio Utzig <utzig@utzig.org> | Mon Nov 02 07:36:45 2020 -0300 |
tree | 6ff75211f42a7d17658a89b6a13a2917a89d99c6 | |
parent | 62a813605b2a1cba2c36d8373c0e8fe91015bcb3 [diff] |
mynewt-mcumgr-cli: update to latest newt/newtmgr deps Update the newt and newtmgr hashes to the latest. Signed-off-by: Naveen Kaje naveen.kaje@juul.com
MCU Manager (mcumgr
) is the application tool that enables a user to communicate with and manage remote devices running an mcumgr server.
The mcumgr
tool is a thin wrapper over the Apache newtmgr
tool. Thus, the newtmgr
documentation provides some useful help with using the mcumgr
tool.
Build the mcumgr tool as follows:
apache-mynewt-mcumgr-1.3.0
directory to $GOPATH/src/mynewt.apache.org/mcumgr
cd $GOPATH/src/mynewt.apache.org/mcumgr/mcumgr
go build
Here are some example mcumgr
invocations.
The following sends an echo command to a Bluetooth device advertising the name “Zephyr”:
mcumgr --conntype ble --connstring peer_name=Zephyr echo hello
This series of commands performs an image upgrade over Bluetooth. The device is assumed to be advertising the name “Zephyr”.
# 1. Query device for its current image list. mcumgr --conntype ble --connstring 'peer_name=Zephyr' image list # 2. Upload new image to device. mcumgr --conntype ble --connstring 'peer_name=Zephyr' image upload <filename> # 3. Tell the device to run the new image on its next boot ("test" the new # image). mcumgr --conntype ble --connstring 'peer_name=Zephyr' image test <image-hash> # 4. Reboot the device. mcumgr --conntype ble --connstring 'peer_name=Zephyr' reset # 5. Query device for its current image list; ensure new image is running. mcumgr --conntype ble --connstring 'peer_name=Zephyr' image list # 6. Make the image swap permanent. mcumgr --conntype ble --connstring 'peer_name=Zephyr' image confirm