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:
Mon Dec 10 20:14:17 2018 +0000
Revision:
0:ea30ba97a865
Initial revision

Who changed what in which revision?

UserRevisionLine numberNew contents of line
screamer 0:ea30ba97a865 1 // ----------------------------------------------------------------------------
screamer 0:ea30ba97a865 2 // Copyright 2016-2017 ARM Ltd.
screamer 0:ea30ba97a865 3 //
screamer 0:ea30ba97a865 4 // SPDX-License-Identifier: Apache-2.0
screamer 0:ea30ba97a865 5 //
screamer 0:ea30ba97a865 6 // Licensed under the Apache License, Version 2.0 (the "License");
screamer 0:ea30ba97a865 7 // you may not use this file except in compliance with the License.
screamer 0:ea30ba97a865 8 // You may obtain a copy of the License at
screamer 0:ea30ba97a865 9 //
screamer 0:ea30ba97a865 10 // http://www.apache.org/licenses/LICENSE-2.0
screamer 0:ea30ba97a865 11 //
screamer 0:ea30ba97a865 12 // Unless required by applicable law or agreed to in writing, software
screamer 0:ea30ba97a865 13 // distributed under the License is distributed on an "AS IS" BASIS,
screamer 0:ea30ba97a865 14 // WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
screamer 0:ea30ba97a865 15 // See the License for the specific language governing permissions and
screamer 0:ea30ba97a865 16 // limitations under the License.
screamer 0:ea30ba97a865 17 // ----------------------------------------------------------------------------
screamer 0:ea30ba97a865 18
screamer 0:ea30ba97a865 19 // This file is a template and it's intented to be copied to the application
screamer 0:ea30ba97a865 20 // Enable this configuration
screamer 0:ea30ba97a865 21
screamer 0:ea30ba97a865 22 #ifndef MBED_CLOUD_CLIENT_USER_CONFIG_H
screamer 0:ea30ba97a865 23 #define MBED_CLOUD_CLIENT_USER_CONFIG_H
screamer 0:ea30ba97a865 24
screamer 0:ea30ba97a865 25 #ifdef MBED_CONF_APP_ENDPOINT_TYPE
screamer 0:ea30ba97a865 26 #define MBED_CLOUD_CLIENT_ENDPOINT_TYPE MBED_CONF_APP_ENDPOINT_TYPE
screamer 0:ea30ba97a865 27 #else
screamer 0:ea30ba97a865 28 #define MBED_CLOUD_CLIENT_ENDPOINT_TYPE "default"
screamer 0:ea30ba97a865 29 #endif
screamer 0:ea30ba97a865 30
screamer 0:ea30ba97a865 31 // Enable either TCP or UDP, but no both
screamer 0:ea30ba97a865 32 #define MBED_CLOUD_CLIENT_TRANSPORT_MODE_TCP
screamer 0:ea30ba97a865 33 // MBED_CLOUD_CLIENT_TRANSPORT_MODE_UDP
screamer 0:ea30ba97a865 34
screamer 0:ea30ba97a865 35 #define MBED_CLOUD_CLIENT_LIFETIME 3600
screamer 0:ea30ba97a865 36
screamer 0:ea30ba97a865 37 #define MBED_CLOUD_CLIENT_SUPPORT_UPDATE
screamer 0:ea30ba97a865 38 #define SN_COAP_MAX_BLOCKWISE_PAYLOAD_SIZE 1024
screamer 0:ea30ba97a865 39
screamer 0:ea30ba97a865 40 // set flag to enable update support in mbed Cloud client
screamer 0:ea30ba97a865 41 #define MBED_CLOUD_CLIENT_SUPPORT_UPDATE
screamer 0:ea30ba97a865 42
screamer 0:ea30ba97a865 43 // set download buffer size in bytes (min. 1024 bytes)
screamer 0:ea30ba97a865 44
screamer 0:ea30ba97a865 45 // Use larger buffers in Linux //
screamer 0:ea30ba97a865 46 #ifdef __linux__
screamer 0:ea30ba97a865 47 #define MBED_CLOUD_CLIENT_UPDATE_BUFFER (2 * 1024 * 1024)
screamer 0:ea30ba97a865 48 #else
screamer 0:ea30ba97a865 49 #define MBED_CLOUD_CLIENT_UPDATE_BUFFER 2048
screamer 0:ea30ba97a865 50 #endif
screamer 0:ea30ba97a865 51
screamer 0:ea30ba97a865 52 // Developer flags for Update feature
screamer 0:ea30ba97a865 53 #if MBED_CONF_APP_DEVELOPER_MODE == 1
screamer 0:ea30ba97a865 54 #define MBED_CLOUD_DEV_UPDATE_CERT
screamer 0:ea30ba97a865 55 #define MBED_CLOUD_DEV_UPDATE_ID
screamer 0:ea30ba97a865 56 #endif // MBED_CONF_APP_DEVELOPER_MODE
screamer 0:ea30ba97a865 57
screamer 0:ea30ba97a865 58 #endif // MBED_CLOUD_CLIENT_USER_CONFIG_H
screamer 0:ea30ba97a865 59