Skip to content

Update demo_testing.md #882

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 14, 2018
Merged

Update demo_testing.md #882

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions docs/porting/porting_full_process/demo_testing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@
You can use two applications to test your port:

1. When you've ported GPIO (and all preceeding modules), use `mbed-os-example-blinky`.
1. When you've ported all mandatory modules, use `mbed-cloud-client-example` (the Device Management Client is part of Mbed OS, and you didn't need to manually port it). This test includes a reference bootloader for firmware update testing.
1. When you've ported all mandatory modules, use `mbed-cloud-client-example` (the Device Management Client runs on top of Mbed OS, and you don't need to manually port it). This test includes a reference bootloader for firmware update testing.

### mbed-os-example-blinky

Expand Down Expand Up @@ -60,7 +60,7 @@ Then, test connectivity and firmware update:

1. Application repository:[https://github.com/armmbed/mbed-cloud-client-example](https://github.com/armmbed/mbed-cloud-client-example).
1. Again, if you have not merged your target into `mbed-os` you will need to add your fork.
1. [Set up a Pelion account](https://cloud.mbed.com/docs/current/account-management/users.html).
1. [Set up a Pelion Device Management account](https://cloud.mbed.com/docs/current/account-management/users.html).
1. [Generate an API key](https://cloud.mbed.com/docs/current/integrate-web-app/api-keys.html) from the [Device Management Portal](https://portal.mbedcloud.com//login).
1. In the `mbed-cloud-client-example` clone on your machine, run the following command with the generated API key:

Expand Down Expand Up @@ -92,8 +92,8 @@ Then, test connectivity and firmware update:

- If your target uses WiFi, fill in the SSID and Password fields in `mbed_app.json`.

- Add SOTP descriptors to `mbed-cloud-client-example/mbed_lib.json`. For example:

- Add NVStore descriptors (previously known as SOTP) for storage to `mbed-cloud-client-example/mbed_lib.json`. For example:
<!-- Don: How does someone figure out what these parameters should be? -->
```
...
"sotp-section-2-size" : "(16*1024)"
Expand Down Expand Up @@ -178,7 +178,7 @@ Then, test connectivity and firmware update:
```

1. Verify that the device is registered by finding it in the [Device Management Portal](https://portal.mbedcloud.com//login).
1. Make change in the application, and rebuild the firmware.
1. Make a change in the application, and rebuild the firmware.
1. Perform a firmware update:

```
Expand Down