Add documentation about `mbed dm` #681

theotherjimmy · 2018-08-23T16:56:38Z

Depens on ARMmbed/mbed-cli#735 and ARMmbed/mbed-os#7844

theotherjimmy · 2018-08-23T16:57:17Z

@AnotherButler Edits welcome.

melwee01

Only looked at the name changes so far, but will give language a look in a sec.

melwee01 · 2018-08-24T05:17:07Z

docs/tools/offline/cli-device-management.md

+
+Mbed CLI includes features that help prepare and ship updates for devices managed through Pelion. The Mbed CLI uses the subcommands starting with `mbed device-management`, `mbed dev-mgmt` or `mbed dm` to manage devices.
+
+Start by configuring your Mbed Cloud SDK API Key, target and toolchain. Obtain the API Key from the Pelion portal.


For now, it's the Device Management Portal. Yes, this is a mouthful. :/

API key (not Key)

Start what? It would help if you explained the process you're going to detail.

melwee01 · 2018-08-24T05:17:46Z

docs/tools/offline/cli-device-management.md

+* A certificate in `.update-certificates/default.der`.
+* A matching private key in `.update-certificates/default.key.pem`.
+* A set of default settings in `.manifest_tool.json`.
+* Mbed Cloud settings in `.mbed_cloud_config.json`.


Device Management settings (though the filenames are still the same...)

melwee01 · 2018-08-24T05:18:20Z

docs/tools/offline/cli-device-management.md

+<span class="notes">**Note:** The certificate created in `mbed dm init` is not suitable for production. Use it for testing and development only. To create a certificate for production purposes, please use an air-gapped computer or a Hardware Security Module. When going to production, conduct a security review on your manifest signing infrastructure, as it is the core of the security guarantees for update client.</span>
+
+#### Single-device update
+Once you have run `mbed device-management init`, you can perform updates on a single device by:


Device Management isn't shortened here?

We also haven't been 'allowed' to shorten it on our side, but I'm not sure that requirements still stands for what things are named in code. Also not willing to risk making that decision myself 😑

Code is its own thing; they need to sort it out between them

I don't like using "once you have x". Also, why is single-device hyphenated?

@iriark01 I'll reword it. ~~Single device is not hyphenated as that's not how I would write. I'll drop single.~~

melwee01 · 2018-08-24T05:21:00Z

docs/tools/offline/cli-device-management.md

+```
+
+This will perform several actions:
+1. Upload the payload, generated by `mbed compile`, to Mbed Cloud.


Device Management

That applies for all instances of Mbed Cloud in this list.

melwee01 · 2018-08-24T05:21:49Z

docs/tools/offline/cli-device-management.md

+This allows development with a device for testing purposes.
+
+#### Multidevice update
+If you need to update more than one device, you can use the Mbed Cloud portal to create device filters that can include many devices into an update campaign. First, you need a manifest. Once you have run `mbed device-management init`, you can create manifests by:


Device Management Portal

melwee01 · 2018-08-24T05:22:19Z

docs/tools/offline/cli-device-management.md

+
+Both methods of creating a manifest use the defaults created in `mbed dm init`. You can override each default using an input file or command-line arguments. See below for more details.
+
+Once you execute `mbed dm update prepare`, Mbed CLI automatically uploads to Mbed Cloud and you can then create and start an update campaign using the Mbed Cloud portal.


Device Management, Device Management Portal

A link to where we explain that (in the Pelion docs) would help massively. Also, it's not obvious that the commands you give me have nothing to do with the filter you sent me to create a second before.

melwee01 · 2018-08-24T05:23:24Z

docs/tools/offline/cli-device-management.md

+Once you execute `mbed dm update prepare`, Mbed CLI automatically uploads to Mbed Cloud and you can then create and start an update campaign using the Mbed Cloud portal.
+
+### Advanced usage
+Mbed CLI allows for significantly more flexibility than the model above shows in exactly the same way as Manifest Tool. You can override each of the defaults that `mbed dm init` sets by using the command-line or an input file. Mbed CLI supports a variety of commands. You can print a full list of commands by using `manifest-tool --help`.


Mbed CLI keeps its name as far as I'm aware.

Also looks like in our manifest tool documentation, it's not capitalized, and instead referred to as "the manifest tool."

Link to the tool's docs

iriark01 · 2018-08-24T08:04:15Z

docs/tools/offline/cli-device-management.md

@@ -0,0 +1,76 @@
+### Updating Devices with Mbed CLI
+
+Mbed CLI includes features that help prepare and ship updates for devices managed through Pelion. The Mbed CLI uses the subcommands starting with `mbed device-management`, `mbed dev-mgmt` or `mbed dm` to manage devices.


Mbed CLI doesn't take "the"

I think I'd also clarify that these are all the same command, that they're just aliases. I'd suggest something along these lines (but feel free to tweak):

Mbed CLI provides the subcommand mbed device-management to manage devices (mbed dev-mgmt are mbed dm are also available as shorter aliases).

iriark01 · 2018-08-24T08:05:37Z

docs/tools/offline/cli-device-management.md

+Start by configuring your Mbed Cloud SDK API Key, target and toolchain. Obtain the API Key from the Pelion portal.
+
+```
+$ mbed config -G CLOUD_SDK_API_KEY ak_...


We normally use something like <API_KEY>, not ...

Agreed, I'd drop the CLOUD_SDK_ part

iriark01 · 2018-08-24T08:06:00Z

docs/tools/offline/cli-device-management.md

+$ mbed device-management init -d "<company domain name>" -m "<product model identifier>"
+```
+
+First, this command asks for information about your update certificate. When Mbed CLI has enough information, it creates several files:


Do we really need "first" here?

Total nit pick: The line "When Mbed CLI has enough information" tripped up my brain for a second (enough information from the command line args? Where is it coming from?). How do you feel about this as an alternative:

After completing the prompts, Mbed CLI creates several files:

iriark01 · 2018-08-24T08:06:16Z

docs/tools/offline/cli-device-management.md

+```
+
+First, this command asks for information about your update certificate. When Mbed CLI has enough information, it creates several files:
+* A certificate in `.update-certificates/default.der`.


Don't think this will render as a list without an empty line before the first bullet

iriark01 · 2018-08-24T08:06:45Z

docs/tools/offline/cli-device-management.md

+* A matching private key in `.update-certificates/default.key.pem`.
+* A set of default settings in `.manifest_tool.json`.
+* Mbed Cloud settings in `.mbed_cloud_config.json`.
+* Mbed Cloud developer credentials in `mbed_cloud_dev_credentials.c`


So this is only for development? What about production flows?

Since this is in the Mbed OS docs, it should (as part of the intro way up there around line 1) link to the Pelion docs. As an Mbed OS user, I've no idea what all these concepts mean.

There is no production flow yet. That's not part of the requirement as far as I know.

iriark01 · 2018-08-24T08:08:36Z

docs/tools/offline/cli-device-management.md

+* Mbed Cloud developer credentials in `mbed_cloud_dev_credentials.c`
+* Mbed Cloud update credentials in `update_defalut_resources.c`
+
+The default settings include:


These are the default settings in mbed_cloud_config.json? Would help to make them sub-bullets of that, rather than make the reader go back to figure out where default settings come in (this is only obvious to people who already know - most readers won't remember that they've just read about default settings two lines ago).

And needs an empty line to render the bullets

iriark01 · 2018-08-24T08:09:05Z

docs/tools/offline/cli-device-management.md

+* Mbed Cloud update credentials in `update_defalut_resources.c`
+
+The default settings include:
+* A unique vendor identifier, based on the domain name supplied to `init`.


When did I supply things to init?

You supplied them to mbed dm init above.

iriark01 · 2018-08-24T08:09:23Z

docs/tools/offline/cli-device-management.md

+The default settings include:
+* A unique vendor identifier, based on the domain name supplied to `init`.
+* A unique model identifier, based on the vendor identifier and the model name supplied to `init`.
+* The path of the certificate and private key.


Which certificate? Developer? Update?

iriark01 · 2018-08-24T08:09:43Z

docs/tools/offline/cli-device-management.md

+* A unique model identifier, based on the vendor identifier and the model name supplied to `init`.
+* The path of the certificate and private key.
+
+If you do not want to enter the subject information for your update certificate (country, state, city, organization and so on), add the `-q` flag to the command above.


How far above? Why not add this as a note right below the command?

iriark01 · 2018-08-24T08:10:14Z

docs/tools/offline/cli-device-management.md

+
+If you do not want to enter the subject information for your update certificate (country, state, city, organization and so on), add the `-q` flag to the command above.
+
+As `device-management` is very long to type, the remainder of this document will use the `mbed dm` alias for all device management subcommands.


You should have said that right after you listed the three possible forms and never used the full form again. It's so random here.

iriark01 · 2018-08-24T08:10:45Z

docs/tools/offline/cli-device-management.md

+
+As `device-management` is very long to type, the remainder of this document will use the `mbed dm` alias for all device management subcommands.
+
+<span class="notes">**Note:** The certificate created in `mbed dm init` is not suitable for production. Use it for testing and development only. To create a certificate for production purposes, please use an air-gapped computer or a Hardware Security Module. When going to production, conduct a security review on your manifest signing infrastructure, as it is the core of the security guarantees for update client.</span>


I would like someone from Update to look at this note. @bremoran ?

Also it should come earlier (right around where I asked about a production flow)

iriark01 · 2018-08-24T08:11:14Z

docs/tools/offline/cli-device-management.md

+
+<span class="notes">**Note:** The certificate created in `mbed dm init` is not suitable for production. Use it for testing and development only. To create a certificate for production purposes, please use an air-gapped computer or a Hardware Security Module. When going to production, conduct a security review on your manifest signing infrastructure, as it is the core of the security guarantees for update client.</span>
+
+#### Single-device update


Need empty line after headers, too

iriark01 · 2018-08-24T08:12:01Z

docs/tools/offline/cli-device-management.md

+Once you have run `mbed device-management init`, you can perform updates on a single device by:
+
+```
+$ mbed compile


But what am I compiling? Where should I be at this point?

probably immediately after mbed dm init, as the text above indicated.

iriark01 · 2018-08-24T08:12:43Z

docs/tools/offline/cli-device-management.md

+1. Hash the payload and create a manifest that links to its location in Mbed Cloud.
+1. Create an update campaign for the supplied device ID, with the newly created manifest.
+1. Start the campaign.
+1. Wait for the campaign to complete.


It's waiting? Even though devices could take ages to come on line and receive an update? What happens if it fails? Do I see that here?

The whole point of the command is to update a device. so, yes it waits for that to happen, and yes that can take a while.

iriark01 · 2018-08-24T08:13:14Z

docs/tools/offline/cli-device-management.md

+1. Create an update campaign for the supplied device ID, with the newly created manifest.
+1. Start the campaign.
+1. Wait for the campaign to complete.
+1. Delete the payload, manifest and update campaign out of Mbed Cloud.


Deletes the update campaign seems odd - don't we show all finished campaigns in the portal?

It's intended for development, so I would expect a developer to do this flow 4-40 times/hour. That would flood the campaign list.

iriark01 · 2018-08-24T08:13:46Z

docs/tools/offline/cli-device-management.md

+1. Wait for the campaign to complete.
+1. Delete the payload, manifest and update campaign out of Mbed Cloud.
+
+This allows development with a device for testing purposes.


That should come before you start giving me commands - I want to know why I'm bothering to compile and run things.

iriark01 · 2018-08-24T08:14:06Z

docs/tools/offline/cli-device-management.md

+$ mbed dm update prepare
+```
+
+Optionally, a name and description for the payload and corresponding manifest can be provided:


Why passive?

copy paste.

bridadan

Some initial comments. This a really great feature, can't wait to see it in action!

bridadan · 2018-08-24T13:49:56Z

docs/tools/offline/cli-device-management.md

+Start by configuring your Mbed Cloud SDK API Key, target and toolchain. Obtain the API Key from the Pelion portal.
+
+```
+$ mbed config -G CLOUD_SDK_API_KEY ak_...


Agreed, I'd drop the CLOUD_SDK_ part

bridadan · 2018-08-24T13:52:42Z

docs/tools/offline/cli-device-management.md

@@ -0,0 +1,76 @@
+### Updating Devices with Mbed CLI
+
+Mbed CLI includes features that help prepare and ship updates for devices managed through Pelion. The Mbed CLI uses the subcommands starting with `mbed device-management`, `mbed dev-mgmt` or `mbed dm` to manage devices.


I think I'd also clarify that these are all the same command, that they're just aliases. I'd suggest something along these lines (but feel free to tweak):

Mbed CLI provides the subcommand mbed device-management to manage devices (mbed dev-mgmt are mbed dm are also available as shorter aliases).

bridadan · 2018-08-24T13:55:14Z

docs/tools/offline/cli-device-management.md

+$ mbed device-management init -d "<company domain name>" -m "<product model identifier>"
+```
+
+First, this command asks for information about your update certificate. When Mbed CLI has enough information, it creates several files:


Total nit pick: The line "When Mbed CLI has enough information" tripped up my brain for a second (enough information from the command line args? Where is it coming from?). How do you feel about this as an alternative:

After completing the prompts, Mbed CLI creates several files:

bridadan · 2018-08-24T14:01:43Z

docs/tools/offline/cli-device-management.md

+Once you execute `mbed dm update prepare`, Mbed CLI automatically uploads to Mbed Device Management and you can then create and start an update campaign using the Mbed Cloud portal.
+
+### Advanced usage
+Mbed CLI allows for significantly more flexibility than the model above shows in exactly the same way as Manifest Tool. You can override each of the defaults that `mbed dm init` sets by using the command-line or an input file. Mbed CLI supports a variety of commands. You can print a full list of commands by using `manifest-tool --help`.


Seeing how this is the first mention of the manifest tool, I would provide a link to the tool's page.

/docs/working/updating-firmware/manifest-tool.html

bridadan · 2018-08-24T14:02:05Z

docs/tools/offline/cli-device-management.md

+
+Both methods of creating a manifest use the defaults created in `mbed dm init`. You can override each default using an input file or command-line arguments. See below for more details.
+
+Once you execute `mbed dm update prepare`, Mbed CLI automatically uploads to Mbed Device Management and you can then create and start an update campaign using the Mbed Cloud portal.


"Mbed CLI automatically uploads to Mbed Device Management"

What does Mbed CLI upload?

AnotherButler · 2018-08-24T14:04:48Z

@MarceloSalazar @ashok-rao FYI

theotherjimmy · 2018-08-24T14:53:25Z

@AnotherButler @iriark01 @MelindaWeed I'm done updating this for now. Feel free to review/suggest edits/edit at your leisure.

MarceloSalazar · 2018-08-27T08:24:29Z

Thanks for sharing. This looks great :)
We'll be OOBing in few days.

bridadan

A few naming concerns and little nits to improve readability.

bridadan · 2018-08-27T15:13:08Z

docs/tools/offline/cli-device-management.md

@@ -0,0 +1,86 @@
+### Updating Devices with Mbed CLI
+
+Mbed CLI includes features to prepare and ship updates for devices managed through the [Device Management Portal](https://cloud.mbed.com/docs/current/introduction/index.html). Mbed CLI uses the subcommands starting with `mbed device-management`, `mbed dev-mgmt` or `mbed dm` to manage devices.  As `device-management` is very long to type, the remainder of this document uses the `mbed dm` alias for all device management subcommands. This document explains the steps to enable and use Mbed Device Managment with a project.


The document I have states that the full name is "Pelion Device Managment", not "Mbed Device Managment".

@bridadan That's what I had before @MelindaWeed Asked me to change it to what it is now.

@MelindaWeed @AnotherButler is "Mbed Device Management" correct? Everything I've seen so far says wither "Pelion Device Management" or just "Device Management". Sorry, not trying to belabor this but since Mbed CLI is pretty forward facing it'd be worth it to get this one right. Also, I guess I want to know for myself going forward what the right phrasing is. Thanks!

Sorry, I should've been more specific.

'Mbed Device Management' is never used. Pelion Device Management is used at the first mention in a page or at the top level of any nested pages, but after that, the Pelion is dropped and it's just Device Management.

Mbed CLI, Mbed OS, and Mbed client (but NOT Mbed Cloud client) keep their names "for brand recognition" 🙄

This is indeed really confusing. Sorry for being unclear!

No problem! Thanks for clarifying!

bridadan · 2018-08-27T15:14:23Z

docs/tools/offline/cli-device-management.md

+
+#### Project Setup
+
+Configuring your Mbed Cloud SDK API key, target and toolchain. Obtain the API key from the the Device Management Portal.


I would honestly just drop the "Mbed Cloud SDK" bit here. Even though that's the library being used behind the scenes, its a bit confusing with the Pelion naming before it. Plus its fairly obvious what "API key" is.

That's there to explain the configuration variable below, which is consistent with other configs: it's prefixed by MBED_ and added to the environment.

Hmm, fair enough. It's very minor either way 👍 I imagine these naming problems will get easier one all of the packages have been updated.

bridadan · 2018-08-27T15:15:55Z

docs/tools/offline/cli-device-management.md

+    * A unique vendor identifier, based on the domain name supplied as the `-d` parameter to `mbed dm init`.
+    * A unique model identifier, based on the vendor identifier and the model name supplied as the `--model-name` to `mbed dm init`.
+    * The path of the update certificate and private key.
+* Mbed Device Management developer credentials in `mbed_cloud_dev_credentials.c`


Ditto about the "Mbed" prefix for "Device Management" here. Since you mentioned Pelion above I think you're ok just saying "Device Management" here.

Again, @MelindaWeed Asked for this name change.

That'd just be Device Management. Sorry for not communicating the standards clearly.

bridadan · 2018-08-27T15:17:17Z

docs/tools/offline/cli-device-management.md

+
+#### Multidevice update
+
+To update more than one device, you can use Mbed CLI to generate and upload a manifest and payload and the Mbed Device Management portal to create device filters that include many devices in an update campaign. After the steps in Project Setup, you can create and upload manifests and palyoads by:


First sentence is quite dense. How do you feel about breaking it up a bit? Something like:

"
To update more than one device, you can use Mbed CLI to generate and upload a manifest and payload. Then you can use the Mbed Device Management portal to create device filters that include many devices in an update campaign.
"

nit: maybe at the end say "upload manifests and payloads by running:"? Seems to read a little easier.

Yeah, that reads better.

bridadan · 2018-08-27T15:18:45Z

docs/tools/offline/cli-device-management.md

+1. Create an update campaign for the supplied device ID, with the newly created manifest.
+1. Start the campaign.
+1. Wait for the campaign to complete.
+1. Delete the payload, manifest and update campaign out of Mbed Device Management.


Ditto about the "Mbed" prefixes.

ditto about the name changes.

bridadan · 2018-08-27T15:19:10Z

docs/tools/offline/cli-device-management.md

+
+#### Single-device update
+
+Mbed CLI provides a subcommand, `mbed dm update device`, for development with a device and for testing purposes. After following the steps in Project Setup, perform firmware updates on a single-device by:


nit: maybe at the end say "upload manifests and payloads by running:"? Seems to read a little easier.

Sure. I can add running.

bridadan

Changes look good, but I still wouldn't mind having one last sign-off on the brand/naming mentioned above.

melwee01 · 2018-08-28T05:42:55Z

I've added some comments: you're right that it's just Device Management (excepting the first mention, which adds the Pelion). I thought I'd communicated that clearly enough, but I didn't. Sorry, will be more specific and give some examples next time.

bridadan

🚀

Make the rest of the requested changes, and copy edit for consistent tense and spelling.

AnotherButler · 2018-08-30T23:41:16Z

@MelindaWeed @iriark01 Please make your final review. Also, did @bremoran ever review that note?

theotherjimmy · 2018-08-31T13:31:05Z

@AnotherButler, @bremoran wrote the original text in that note.

iriark01 · 2018-09-03T09:59:49Z

@AnotherButler Brendan and I are missing each other in terms of holidays. Please can you review this with him?

docs/tools/offline/cli-device-management.md

MarceloSalazar

Small but important change on using mbed dm update

Update phrasing for product positioning.

Add requested code changes.

Add documentation about mbed dm

0dd6a93

Depens on ARMmbed/mbed-cli#735 and ARMmbed/mbed-os#7844

AnotherButler requested review from peknis01, melwee01 and iriark01 August 23, 2018 17:00

AnotherButler added the code dependency label Aug 23, 2018

AnotherButler requested review from bridadan and cmonr August 23, 2018 18:25

melwee01 suggested changes Aug 24, 2018

View reviewed changes

iriark01 reviewed Aug 24, 2018

View reviewed changes

Rename all the things

a01cdbb

bridadan suggested changes Aug 24, 2018

View reviewed changes

Move all the text

e987f72

theotherjimmy added 3 commits August 24, 2018 09:12

Name setup and refer to it by it's name

3985136

Link to pelion docs; improve some text

3bbde13

Reword to avoid confusion

8b3053a

This was referenced Aug 27, 2018

Simple Cloud Client Tests PelionIoT/simple-mbed-cloud-client#12

Merged

Introduce device-management/dev-mgmt/dm subcommand ARMmbed/mbed-cli#735

Merged

bridadan reviewed Aug 27, 2018

View reviewed changes

Edit with Brian

40a757f

bridadan approved these changes Aug 27, 2018

View reviewed changes

Mbed Device Management -> Pelion Device Management

72f1710

bridadan approved these changes Aug 28, 2018

View reviewed changes

Edit cli-device-management.md

6137ca5

Make the rest of the requested changes, and copy edit for consistent tense and spelling.

AnotherButler approved these changes Aug 30, 2018

View reviewed changes

AnotherButler removed the code dependency label Aug 31, 2018

MarceloSalazar reviewed Sep 3, 2018

View reviewed changes

docs/tools/offline/cli-device-management.md Outdated Show resolved Hide resolved

MarceloSalazar reviewed Sep 3, 2018

View reviewed changes

AnotherButler added the 5.10 urgent label Sep 4, 2018

Amanda Butler added 2 commits September 4, 2018 06:06

Rephrase sentence in cli-device-management.md

91cee41

Update phrasing for product positioning.

Add requested change to cli-device-management.md

3d9066d

Add requested code changes.

AnotherButler merged commit 3665b5a into ARMmbed:development Sep 4, 2018


		Mbed CLI includes features that help prepare and ship updates for devices managed through Pelion. The Mbed CLI uses the subcommands starting with `mbed device-management`, `mbed dev-mgmt` or `mbed dm` to manage devices.

		Start by configuring your Mbed Cloud SDK API Key, target and toolchain. Obtain the API Key from the Pelion portal.


		Both methods of creating a manifest use the defaults created in `mbed dm init`. You can override each default using an input file or command-line arguments. See below for more details.

		Once you execute `mbed dm update prepare`, Mbed CLI automatically uploads to Mbed Cloud and you can then create and start an update campaign using the Mbed Cloud portal.

		@@ -0,0 +1,76 @@
		### Updating Devices with Mbed CLI

		Mbed CLI includes features that help prepare and ship updates for devices managed through Pelion. The Mbed CLI uses the subcommands starting with `mbed device-management`, `mbed dev-mgmt` or `mbed dm` to manage devices.


		If you do not want to enter the subject information for your update certificate (country, state, city, organization and so on), add the `-q` flag to the command above.

		As `device-management` is very long to type, the remainder of this document will use the `mbed dm` alias for all device management subcommands.


		As `device-management` is very long to type, the remainder of this document will use the `mbed dm` alias for all device management subcommands.

		<span class="notes">Note: The certificate created in `mbed dm init` is not suitable for production. Use it for testing and development only. To create a certificate for production purposes, please use an air-gapped computer or a Hardware Security Module. When going to production, conduct a security review on your manifest signing infrastructure, as it is the core of the security guarantees for update client.</span>


		<span class="notes">Note: The certificate created in `mbed dm init` is not suitable for production. Use it for testing and development only. To create a certificate for production purposes, please use an air-gapped computer or a Hardware Security Module. When going to production, conduct a security review on your manifest signing infrastructure, as it is the core of the security guarantees for update client.</span>

		#### Single-device update

		@@ -0,0 +1,86 @@
		### Updating Devices with Mbed CLI

		Mbed CLI includes features to prepare and ship updates for devices managed through the [Device Management Portal](https://cloud.mbed.com/docs/current/introduction/index.html). Mbed CLI uses the subcommands starting with `mbed device-management`, `mbed dev-mgmt` or `mbed dm` to manage devices. As `device-management` is very long to type, the remainder of this document uses the `mbed dm` alias for all device management subcommands. This document explains the steps to enable and use Mbed Device Managment with a project.


		#### Project Setup

		Configuring your Mbed Cloud SDK API key, target and toolchain. Obtain the API key from the the Device Management Portal.


		#### Multidevice update

		To update more than one device, you can use Mbed CLI to generate and upload a manifest and payload and the Mbed Device Management portal to create device filters that include many devices in an update campaign. After the steps in Project Setup, you can create and upload manifests and palyoads by:


		#### Single-device update

		Mbed CLI provides a subcommand, `mbed dm update device`, for development with a device and for testing purposes. After following the steps in Project Setup, perform firmware updates on a single-device by:

Add documentation about mbed dm #681

Add documentation about mbed dm #681

Uh oh!

Conversation

theotherjimmy commented Aug 23, 2018

Uh oh!

theotherjimmy commented Aug 23, 2018

Uh oh!

melwee01 left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

theotherjimmy Aug 24, 2018 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Add documentation about `mbed dm` #681

Add documentation about `mbed dm` #681

theotherjimmy Aug 24, 2018 •

edited

Loading