Mbed OS Device Management example for various ST boards.

DEPRECATED

This example application is not maintained and not recommended. It uses an old version of Mbed OS, Pelion DM and Arm toolchain. It doesn't work with Mbed Studio.

Please use: https://os.mbed.com/teams/mbed-os-examples/code/mbed-os-example-pelion/

This example is known to work great on the following platforms:

  • DISCO_L475E_IOT01A - onboard WiFI and onboard QSPI flash. Board specific example using onboard sensors is available here.
  • DISCO_F413H - onboard WiFI and onboard QSPI flash.
  • DISCO_F469NI - WizFi310 WiFI shield and onboard QSPI flash (see WiFi shield instructions).
  • DISCO_F746NG - onboard Ethernet and using onboard QSPI flash.
  • DISCO_F769NI - onboard Ethernet and using onboard QSPI flash.
  • DISCO_L496AG - WizFi310 WiFI shield and onboard QSPI flash (see WiFi shield instructions).
  • NUCLEO_F207ZG - onboard Ethernet and wired SD card (SD card wiring instructions).
  • NUCLEO_F412ZG - WizFi310 WiFI shield and SD card shield (see WiFi shield instructions).
  • NUCLEO_F429ZI - onboard Ethernet and wired SD card (SD card wiring instructions).
  • NUCLEO_F746ZG - onboard Ethernet and wired SD card (SD card wiring instructions).
  • NUCLEO_F767ZI - onboard Ethernet and wired SD card (SD card wiring instructions).
  • NUCLEO_L476RG - WizFi310 WiFI shield and SD card shield (see WiFi shield instructions).
  • NUCLEO_L496ZG - WizFi310 WiFI shield and SD card shield (see WiFi shield instructions).
  • NUCLEO_L4R5ZI - WizFi310 WiFI shield and SD card shield (see WiFi shield instructions).

Follow the Quick-Start instructions: https://cloud.mbed.com/quick-start

DISCO_L475E_IOT01A DISCO_F413H DISCO_F746NG NUCLEO_F429ZI, NUCLEO_F767ZI, NUCLEO_F746ZG,NUCLEO_F207ZG

Example functionality

This example showcases the following device functionality:

  • Read ADC temperature and ADC vref, and report them as Pelion LWM2M resources (see image below).
  • On user button click, increment Pelion LWM2M button resource.
  • Allow the user to change the state of the board LED from Pelion LWM2M led_state resource and PUT request.

/media/uploads/screamer/pelion_st_adc_reading.png

SD card wiring

The ST Nucleo family of boards don't have storage onboard and therefore you will need an SD card. A limitation on ST Nucleo 144 boards is that there's a conflict between Ethernet and SPI pins on Arduino D11. Due to this, the SD card must be wired to different SPI bus that doesn't conflict with other functionality. The image below provide instructions on how to wire an SD card to a non-conflicting SPI instance.

/media/uploads/screamer/st_nucleo_144_sd.jpeg?v=4

If you are not a first-time Pelion Device Management user your device's SD card may already have connect and update certificates on it. If this is the case, remove and manually format your micro SD card, flash the binary to the device and then re-insert your micro SD card.

WiFi shield setup/wiring

Some ST Nucleo and Discovery boards don't have IP connectivity option, but bundled with a WiFi shield, they can take benefit of full device management capabilities. See links to reference images below on how to wire WizFI310 WiFi shield and/or SD card shield:

Use this example with Mbed CLI

1. Import the application into your desktop:

mbed import /teams/ST/code/pelion-example-common

cd pelion-example-common

2. Install the CLOUD_SDK_API_KEY

mbed config -G CLOUD_SDK_API_KEY <PELION_DM_API_KEY>

For instructions on how to generate your API key, please see the documentation.

3. Initialize firmware credentials (done once per repository). You can use the following command:

mbed dm init -d "<your company name in Pelion DM>" --model-name "<product model identifier>" -q --force

If above command do not work for your Mbed CLI, please consider upgrading Mbed CLI to version 1.8.x or above.

4. Compile and program:

mbed compile -t <toolchain> -m <TARGET_BOARD>

(supported toolchains : GCC_ARM / ARM / IAR)

Committer:
screamer
Date:
Tue Feb 19 22:34:59 2019 +0000
Revision:
19:7e760f65ed78
Parent:
3:108c0af2b7c8
Updated to Mbed OS 5.11.4 and SMCC 2.1.1.2. Added support for DISCO_F769NI, NUCLEO_F412ZG and NUCLEO_L4R5ZI

Who changed what in which revision?

UserRevisionLine numberNew contents of line
screamer 3:108c0af2b7c8 1 /*
screamer 3:108c0af2b7c8 2 * Copyright (c) 2017 ARM Limited. All rights reserved.
screamer 3:108c0af2b7c8 3 * SPDX-License-Identifier: Apache-2.0
screamer 3:108c0af2b7c8 4 * Licensed under the Apache License, Version 2.0 (the License); you may
screamer 3:108c0af2b7c8 5 * not use this file except in compliance with the License.
screamer 3:108c0af2b7c8 6 * You may obtain a copy of the License at
screamer 3:108c0af2b7c8 7 *
screamer 3:108c0af2b7c8 8 * http://www.apache.org/licenses/LICENSE-2.0
screamer 3:108c0af2b7c8 9 *
screamer 3:108c0af2b7c8 10 * Unless required by applicable law or agreed to in writing, software
screamer 3:108c0af2b7c8 11 * distributed under the License is distributed on an AS IS BASIS, WITHOUT
screamer 3:108c0af2b7c8 12 * WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
screamer 3:108c0af2b7c8 13 * See the License for the specific language governing permissions and
screamer 3:108c0af2b7c8 14 * limitations under the License.
screamer 3:108c0af2b7c8 15 */
screamer 3:108c0af2b7c8 16 #ifndef __MBED_CLOUD_DEV_CREDENTIALS_H__
screamer 3:108c0af2b7c8 17 #define __MBED_CLOUD_DEV_CREDENTIALS_H__
screamer 3:108c0af2b7c8 18
screamer 19:7e760f65ed78 19 #if MBED_CONF_DEVICE_MANAGEMENT_DEVELOPER_MODE == 1
screamer 3:108c0af2b7c8 20 #error "Replace mbed_cloud_dev_credentials.c with your own developer cert."
screamer 3:108c0af2b7c8 21 #endif
screamer 3:108c0af2b7c8 22
screamer 3:108c0af2b7c8 23 #include <inttypes.h>
screamer 3:108c0af2b7c8 24
screamer 3:108c0af2b7c8 25 const char MBED_CLOUD_DEV_BOOTSTRAP_ENDPOINT_NAME[] = "";
screamer 3:108c0af2b7c8 26 const char MBED_CLOUD_DEV_ACCOUNT_ID[] = "";
screamer 3:108c0af2b7c8 27 const char MBED_CLOUD_DEV_BOOTSTRAP_SERVER_URI[] = "";
screamer 3:108c0af2b7c8 28
screamer 3:108c0af2b7c8 29 const uint8_t MBED_CLOUD_DEV_BOOTSTRAP_DEVICE_CERTIFICATE[] =
screamer 3:108c0af2b7c8 30 { 0x0 };
screamer 3:108c0af2b7c8 31
screamer 3:108c0af2b7c8 32 const uint8_t MBED_CLOUD_DEV_BOOTSTRAP_SERVER_ROOT_CA_CERTIFICATE[] =
screamer 3:108c0af2b7c8 33 { 0x0 };
screamer 3:108c0af2b7c8 34
screamer 3:108c0af2b7c8 35 const uint8_t MBED_CLOUD_DEV_BOOTSTRAP_DEVICE_PRIVATE_KEY[] =
screamer 3:108c0af2b7c8 36 { 0x0 };
screamer 3:108c0af2b7c8 37
screamer 3:108c0af2b7c8 38 const char MBED_CLOUD_DEV_MANUFACTURER[] = "dev_manufacturer";
screamer 3:108c0af2b7c8 39
screamer 3:108c0af2b7c8 40 const char MBED_CLOUD_DEV_MODEL_NUMBER[] = "dev_model_num";
screamer 3:108c0af2b7c8 41
screamer 3:108c0af2b7c8 42 const char MBED_CLOUD_DEV_SERIAL_NUMBER[] = "0";
screamer 3:108c0af2b7c8 43
screamer 3:108c0af2b7c8 44 const char MBED_CLOUD_DEV_DEVICE_TYPE[] = "dev_device_type";
screamer 3:108c0af2b7c8 45
screamer 3:108c0af2b7c8 46 const char MBED_CLOUD_DEV_HARDWARE_VERSION[] = "dev_hardware_version";
screamer 3:108c0af2b7c8 47
screamer 3:108c0af2b7c8 48 const uint32_t MBED_CLOUD_DEV_MEMORY_TOTAL_KB = 0;
screamer 3:108c0af2b7c8 49 const uint32_t MBED_CLOUD_DEV_BOOTSTRAP_DEVICE_CERTIFICATE_SIZE = sizeof(MBED_CLOUD_DEV_BOOTSTRAP_DEVICE_CERTIFICATE);
screamer 3:108c0af2b7c8 50 const uint32_t MBED_CLOUD_DEV_BOOTSTRAP_SERVER_ROOT_CA_CERTIFICATE_SIZE = sizeof(MBED_CLOUD_DEV_BOOTSTRAP_SERVER_ROOT_CA_CERTIFICATE);
screamer 3:108c0af2b7c8 51 const uint32_t MBED_CLOUD_DEV_BOOTSTRAP_DEVICE_PRIVATE_KEY_SIZE = sizeof(MBED_CLOUD_DEV_BOOTSTRAP_DEVICE_PRIVATE_KEY);
screamer 3:108c0af2b7c8 52
screamer 3:108c0af2b7c8 53 #endif //__MBED_CLOUD_DEV_CREDENTIALS_H__