When your device is listed on the Devices page, it is connected and available. Select Device directory from the menu on the left. Log in to Device Management Portal for your region: To verify the connection with Device Management Portal:

When the client has successfully connected, the terminal shows: Client registered Obtain your device's Device ID either from device console logs or from Device Management Portal.Press the Reset button to restart the device.You should see the LED blink rapidly wait for it to stop.Ĭonnecting and performing a firmware update on your device Checking the device connection and obtaining the Device ID Drag and drop mbed-cloud-client-example.bin to the device.Connect the device to your computer over USB.To compile the example application: mbed compileįor more information about Mbed CLI parameters, please see the Mbed OS documentation site. Therefore, you need to skip running this command as your environment should be already initialized.Ĭompiling and flashing Device Management Client Note: When you create a firmware update image for a deployed device, you must use the same update-related configuration and credentials (update private key, public key certificate, update_default_resources.c and configuration files) you used in the original device firmware image. Upgrade to manifest-tool version 2.2.0 or higher:.The AGGRESSIVE configurations are suitable for very small deployments (ĭownload a developer certificate from Device Management Portal.Ĭopy the mbed_cloud_dev_credentials.c file to the root folder of the example application.Ĭreate update-related configuration and credentials using the manifest-tool python package: (2) Wi-SUN configuration is available in mesh_wisun.json and uses custom target names: NUCLEO_F429ZI, NUCLEO_F429ZI_AGGRESSIVE, MIMXRT1050_EVK, MIMXRT1050_EVK_AGGRESSIVE.This configuration uses only an internal flash storage and does not require an SD card. (1) RAM-optimized Wi-Fi configuration is available in configs/wifi_esp8266_minimal.json.SD card / Internal flash (1) / ATECC608A secure element The default stack configuration is in the mbed_app.json file. You can use this tutorial with the following boards. This is an advanced Device Management Client example ( mbed-cloud-client-example), written using Device Management Client 4.7.0 and Mbed OS 6.5.0. Command-line tutorial for the advanced Device Management Client example with an Mbed OS device Command-line tutorial for the advanced Device Management Client example with an Mbed OS device

Github mac command line tutorial