| commit | f6c88ed61e933cbc6a9fe93670725343ac766926 | [log] [tgz] |
|---|---|---|
| author | Christopher Collins <ccollins@apache.org> | Thu Aug 08 15:45:14 2019 -0700 |
| committer | Christopher Collins <ccollins@apache.org> | Thu Aug 08 15:45:14 2019 -0700 |
| tree | b0d14475a9c8e9b586b5c0a0b86a996aa18013fd | |
| parent | 982b276df3a27ea9ad2e1e90f85efbf3909a3f6e [diff] |
Depend on latest newtmgr This fixes #8.
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/mcumgrcd $GOPATH/src/mynewt.apache.org/mcumgr/mcumgrgo buildHere 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