IMPROVEMENT: [IOTUC-685] Update instructions (ARMmbed#152)

Author: evedon

README.md

@@ -1,6 +1,4 @@
 # mbed-bootloader
- 
-[![Build Status](https://jenkins-internal.mbed.com/buildStatus/icon?job=ARMmbed/mbed-bootloader-internal/master)](https://jenkins-internal.mbed.com/job/ARMmbed/job/mbed-bootloader-internal/job/master/)
 
 Generic bootloader to be used in conjunction with [mbed-cloud-client](https://github.com/ARMmbed/mbed-cloud-client).
 
@@ -9,8 +7,18 @@ Generic bootloader to be used in conjunction with [mbed-cloud-client](https://gi
 1. Install `mbed-cli` https://github.com/ARMmbed/mbed-cli
 1. Run `mbed deploy` to pull in dependencies
 1. Compile by running `mbed compile -t GCC_ARM -m (K64F|NUCLEO_F429ZI|UBLOX_EVK_ODIN_W2) --profile=tiny.json`
-1. Use this [script](https://github.com/ARMmbed/mbed-cloud-client-example/blob/master/tools/combine_bootloader_with_app.py) to combine the bootloader with application `python tools/combine_bootloader_with_app.py -a {application.bin} -b {bootloader.bin} --app-offset {application-start-address} --header-offset {firmware_metadata_header_address} -o {combined.bin}`.
-1. Flash `{combined.bin}` to device by drag and drop.
+
+## Installation instructions
+
+An image that contains the bootloader and your application can then be flashed on your device.
+
+If you use Mbed CLI 1.8.x then two images are created when you compile the `example application` https://github.com/ARMmbed/mbed-cloud-client-example:
+* A full image `mbed-cloud-client-example-internal.bin` which combines the application with the bootloader and is used for the initial programming of the device
+* An update image `mbed-cloud-client-example-internal_update.bin` which contains only the application and is used for updating the device over the air
+
+For more details, see [Arm Mbed OS managed bootloader](https://os.mbed.com/docs/v5.10/tutorials/bootloader.html#arm-mbed-os-managed-bootloader).
+
+Flash `mbed-cloud-client-example-internal.bin` to your device by drag and drop.
 
 ## Metadata Header
 
@@ -34,7 +42,7 @@ If `application-jump-address` is not set, the `application-start-address` will b
 
 ### Firmware Candidate Storage
 
-1. `MBED_CLOUD_CLIENT_UPDATE_STORAGE`, This need to be set in the "macros" section of `mbed_app.json`. Choices are ARM_UCP_FLASHIAP_BLOCKDEVICE and ARM_UCP_FLASHIAP. This determines whether the firmware is stored on a blockdevice or internal flash. If blockdevice is used `ARM_UC_USE_PAL_BLOCKDEVICE=1` must also be set. 
+1. `MBED_CLOUD_CLIENT_UPDATE_STORAGE`, This need to be set in the "macros" section of `mbed_app.json`. Choices are ARM_UCP_FLASHIAP_BLOCKDEVICE and ARM_UCP_FLASHIAP. This determines whether the firmware is stored on a blockdevice or internal flash. If blockdevice is used `ARM_UC_USE_PAL_BLOCKDEVICE=1` must also be set.
 1. `update-client.storage-address`, The address in sd block device or internal flash where the firmware candidates are stored. **Must align to flash erase boundary**
 1. `update-client.storage-size`, total size on the block device or internal flash reserved for firmware storage. It will be rounded up to align with flash erase sector size automatically.
 1. `update-client.storage-locations`, The number of slots in the firmware storage.