Edit porting.md

Make further formatting edits.

Author: Amanda Butler

docs/porting/porting.md

@@ -585,244 +585,233 @@ Program the generated .bin or .hex.
 
 ##### 9.2.3 mbed-cloud-client-example
 
-###### 9.2.3.1 Application repository
+Use the following test procedure on the `mbed-cloud-client-example` [application repository](https://github.com/armmbed/mbed-cloud-client-example)
 
-https://github.com/armmbed/mbed-cloud-client-example
-
-###### 9.2.3.2 Test procedure
-
-(1) Setup Pelion Account per instructions on https://cloud.mbed.com/product-overview.
-
-(2) Generate API key on Pelion Portal.
-
-(3) Run the following command with the generated API key in mbed-cloud-client-example directory
-
-```
-$ mbed config -G CLOUD_SDK_API_KEY <API_KEY>
-$ mbed target <new_target>
-$ mbed toolchain GCC_ARM
-$ mbed dm init -d "<company domain name>" --model-name <new_target>
-```
-
-Two files update_default_resources.c and mbed_cloud_dev_credentials.c should be created and used in the build.
-
-(4) Customize json files.
+1. Set up Pelion Account per instructions on https://cloud.mbed.com/product-overview.
+1. Generate API key on Pelion Portal.
+1. Run the following command with the generated API key in mbed-cloud-client-example directory
+   
+   ```
+   $ mbed config -G CLOUD_SDK_API_KEY <API_KEY>
+   $ mbed target <new_target>
+   $ mbed toolchain GCC_ARM
+   $ mbed dm init -d "<company domain name>" --model-name <new_target>
+   ```
 
-The following customization is needed prior to build:
+   Two files update_default_resources.c and mbed_cloud_dev_credentials.c should be created and used in the build.
 
-- Modify mbed-os.lib by changing the URL to https://github.com/ARMmbed/mbed-os-new-target
-- Add the new target to mbed-cloud-client-example/mbed_app.json. For example, the code block below adds CC3220SF:
+1. Customize json files.
+   
+   The following customization is needed prior to build:
+   
+   - Modify mbed-os.lib by changing the URL to https://github.com/ARMmbed/mbed-os-new-target
+   - Add the new target to mbed-cloud-client-example/mbed_app.json. For example, the code block below adds CC3220SF:
+   
+      ```
+      ...
+          "target.macros_remove" : ["MBEDTLS_CONFIG_HW_SUPPORT"]
+      },
+      "CC3220SF": {
+          "target.network-default-interface-type" : "WIFI",
+          "update-client.bootloader-details" : "0x01006F44",
+          "update-client.application-details" : "0x01008000",
+          "client_app.auto_partition": "1"
+      }
+      ```
 
-   mbed_app.json example
-   ```
-   ...
-       "target.macros_remove" : ["MBEDTLS_CONFIG_HW_SUPPORT"]
-   },
-   "CC3220SF": {
-       "target.network-default-interface-type" : "WIFI",
-       "update-client.bootloader-details" : "0x01006F44",
-       "update-client.application-details" : "0x01008000",
-       "client_app.auto_partition": "1"
-   }
-   ```
    In addition, fill in the SSID and Password in mbed_app.json if connectivity method for the new target is WiFi.
    
    Note that bootloader-details is the value displayed on the serial program while running mbed-bootloader program.
 
-- Add SOTP descriptors to mbed-cloud-client-example/mbed_lib.json, e.g.
-   
-   mbed_app.json example
+   - Add SOTP descriptors to mbed-cloud-client-example/mbed_lib.json, e.g.
+      
+      ```
+      ...
+          "sotp-section-2-size"              : "(16*1024)"
+       },
+       "CC3220SF": {
+           "sotp-section-1-address"           : "(0x01000000+1020*1024)",
+           "sotp-section-1-size"              : "(2*1024)",
+           "sotp-section-2-address"           : "(0x01000000+1022*1024)",
+           "sotp-section-2-size"              : "(2*1024)"
+       }
+      ```
+
+1. Build image.
+
    ```
-   ...
-       "sotp-section-2-size"              : "(16*1024)"
-    },
-    "CC3220SF": {
-        "sotp-section-1-address"           : "(0x01000000+1020*1024)",
-        "sotp-section-1-size"              : "(2*1024)",
-        "sotp-section-2-address"           : "(0x01000000+1022*1024)",
-        "sotp-section-2-size"              : "(2*1024)"
-    }
+   cd mbed-cloud-client-example
+   mbed deploy
+   mbed compile --target <new_target> --toolchain GCC_ARM
    ```
 
-(5) Build image.
-
-Build MMC
-```
-cd mbed-cloud-client-example
-mbed deploy
-mbed compile --target <new_target> --toolchain GCC_ARM
-```
-
-(6) Program the generated .bin or .hex to the board.
-
-(7) Verify serial output similar to: 
+1. Program the generated .bin or .hex to the board.
+1. Verify serial output similar to: 
 
-```
-[BOOT] Mbed Bootloader
+   ```
+   [BOOT] Mbed Bootloader
 
-[BOOT] ARM: 00000000000000000000
+   [BOOT] ARM: 00000000000000000000
 
-[BOOT] OEM: 00000000000000000000
+   [BOOT] OEM: 00000000000000000000
 
-[BOOT] Layout: 0 1006F44
+   [BOOT] Layout: 0 1006F44
 
-[BOOT] Active firmware integrity check:
+   [BOOT] Active firmware integrity check:
 
-[BOOT] [++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++]
+   [BOOT] [++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++]
 
-[BOOT] SHA256: ABAF3AC1F2D7B8173BC5540DA50E7093C8A479E4C0148090348BD1EA68A0958F
+   [BOOT] SHA256: ABAF3AC1F2D7B8173BC5540DA50E7093C8A479E4C0148090348BD1EA68A0958F
 
-[BOOT] Version: 1539890967
+   [BOOT] Version: 1539890967
 
-[BOOT] Slot 0 is empty
+   [BOOT] Slot 0 is empty
 
-[BOOT] Active firmware up-to-date
+   [BOOT] Active firmware up-to-date
 
-[BOOT] Application's start address: 0x1008400
+   [BOOT] Application's start address: 0x1008400
 
-[BOOT] Application's jump address: 0x1046081
+   [BOOT] Application's jump address: 0x1046081
 
-[BOOT] Application's stack address: 0x20040000
+   [BOOT] Application's stack address: 0x20040000
 
-[BOOT] Forwarding to application...
+   [BOOT] Forwarding to application...
 
 
 
-mcc_platform_storage_init() - bd->size() = 16021192704
+   mcc_platform_storage_init() - bd->size() = 16021192704
 
-mcc_platform_storage_init() - BlockDevice init OK.
+   mcc_platform_storage_init() - BlockDevice init OK.
 
-Application ready. Build at: Oct 18 2018 14:29:26
+   Application ready. Build at: Oct 18 2018 14:29:26
 
-Mbed OS version 99.99.99
+   Mbed OS version 99.99.99
 
-Start simple mbed Cloud Client
+   Start simple mbed Cloud Client
 
-Using hardcoded Root of Trust, not suitable for production use.
+   Using hardcoded Root of Trust, not suitable for production use.
 
-Starting developer flow
+   Starting developer flow
 
-mcc_platform_init_connection()
+   mcc_platform_init_connection()
 
-NSAPI_STATUS_CONNECTING
+   NSAPI_STATUS_CONNECTING
 
-NSAPI_STATUS_GLOBAL_UP
+   NSAPI_STATUS_GLOBAL_UP
 
-Network initialized, connecting...
+   Network initialized, connecting...
 
 
 
-Client registered
+   Client registered
 
-Endpoint Name: 016688bda0740000000000010010007a
+   Endpoint Name: 016688bda0740000000000010010007a
 
-Device Id: 016688bda0740000000000010010007a
-```
-
-(8) Verify device is registered on Pelion portal
-
-(9) Make change in the MCC client and rebuild the firmware.
+   Device Id: 016688bda0740000000000010010007a
+   ```
 
-(10) Perform firmware update
+1. Verify device is registered on Pelion portal
+1. Make change in the MCC client and rebuild the firmware.
+1. Perform firmware update
 
-```
-$ mbed dm update device -D <device ID> -m <new_target>
-```
+   ```
+   $ mbed dm update device -D <device ID> -m <new_target>
+   ```
 
-The following serial output is expected if firmware update is successful:
+   The following serial output is expected if firmware update is successful:
 
-```
-Firmware download requested
+   ```
+   Firmware download requested
 
-Authorization granted
+   Authorization granted
 
-Downloading: [++++++++++++++++++++++++++++++++++++++++++++++++++] 100 %
+   Downloading: [++++++++++++++++++++++++++++++++++++++++++++++++++] 100 %
 
-Download completed
+   Download completed
 
-Firmware install requested
+   Firmware install requested
 
-Authorization granted
-```
+   Authorization granted
+   ```
 
-Power cycle the board.
+   Power cycle the board.
 
-(11) Verify the newer firmware is running on the device. Serial output should display the following:
+1. Verify the newer firmware is running on the device. Serial output should display the following:
 
-```
-[BOOT] Mbed Bootloader
+   ```
+   [BOOT] Mbed Bootloader
 
-[BOOT] ARM: 00000000000000000000
+   [BOOT] ARM: 00000000000000000000
 
-[BOOT] OEM: 00000000000000000000
+   [BOOT] OEM: 00000000000000000000
 
-[BOOT] Layout: 0 1006F44
+   [BOOT] Layout: 0 1006F44
 
-[BOOT] Active firmware integrity check:
+   [BOOT] Active firmware integrity check:
 
-[BOOT] [++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++]
+   [BOOT] [++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++]
 
-[BOOT] SHA256: ABAF3AC1F2D7B8173BC5540DA50E7093C8A479E4C0148090348BD1EA68A0958F
+   [BOOT] SHA256: ABAF3AC1F2D7B8173BC5540DA50E7093C8A479E4C0148090348BD1EA68A0958F
 
-[BOOT] Version: 1539890967
+   [BOOT] Version: 1539890967
 
-[BOOT] Slot 0 firmware integrity check:
+   [BOOT] Slot 0 firmware integrity check:
 
-[BOOT] [++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++]
+   [BOOT] [++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++]
 
-[BOOT] SHA256: ABAF3AC1F2D7B8173BC5540DA50E7093C8A479E4C0148090348BD1EA68A0958F
+   [BOOT] SHA256: ABAF3AC1F2D7B8173BC5540DA50E7093C8A479E4C0148090348BD1EA68A0958F
 
-[BOOT] Version: 1539892842
+   [BOOT] Version: 1539892842
 
-[BOOT] Update active firmware using slot 0:
+   [BOOT] Update active firmware using slot 0:
 
-[BOOT] [++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++]
+   [BOOT] [++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++]
 
-[BOOT] Verify new active firmware:
+   [BOOT] Verify new active firmware:
 
-[BOOT] [++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++]
+   [BOOT] [++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++]
 
-[BOOT] New active firmware is valid
+   [BOOT] New active firmware is valid
 
-[BOOT] Application's start address: 0x1008400
+   [BOOT] Application's start address: 0x1008400
 
-[BOOT] Application's jump address: 0x1046081
+   [BOOT] Application's jump address: 0x1046081
 
-[BOOT] Application's stack address: 0x20040000
+   [BOOT] Application's stack address: 0x20040000
 
-[BOOT] Forwarding to application...
+   [BOOT] Forwarding to application...
 
 
 
-mcc_platform_storage_init() - bd->size() = 16021192704
+   mcc_platform_storage_init() - bd->size() = 16021192704
 
-mcc_platform_storage_init() - BlockDevice init OK.
+   mcc_platform_storage_init() - BlockDevice init OK.
 
-Application ready. Build at: Oct 18 2018 14:29:26
+   Application ready. Build at: Oct 18 2018 14:29:26
 
-Mbed OS version 99.99.99
+   Mbed OS version 99.99.99
 
-Start simple mbed Cloud Client
+   Start simple mbed Cloud Client
 
-Using hardcoded Root of Trust, not suitable for production use.
+   Using hardcoded Root of Trust, not suitable for production use.
 
-Starting developer flow
+   Starting developer flow
 
-Developer credentials already exist, continuing..
+   Developer credentials already exist, continuing..
 
-mcc_platform_init_connection()
+   mcc_platform_init_connection()
 
-NSAPI_STATUS_CONNECTING
+   NSAPI_STATUS_CONNECTING
 
-NSAPI_STATUS_GLOBAL_UP
+   NSAPI_STATUS_GLOBAL_UP
 
-Network initialized, connecting...
+   Network initialized, connecting...
 
 
 
-Client registered
+   Client registered
 
-Endpoint Name: 016688bda0740000000000010010007a
+   Endpoint Name: 016688bda0740000000000010010007a
 
-Device Id: 016688bda0740000000000010010007a
-```
+   Device Id: 016688bda0740000000000010010007a
+   ```