ST / Mbed OS pelion-example-common

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)

bootloader/LICENSE@25:d8a84856bd96, 2019-03-27 (annotated)

Committer:
screamer
Date:
Wed Mar 27 18:17:34 2019 +0000
Revision:
25:d8a84856bd96
Parent:
0:ea30ba97a865 
Improve inline documentation

Who changed what in which revision?

UserRevisionLine numberNew contents of line
screamer 0:ea30ba97a865 1 Permissive Binary License
screamer 0:ea30ba97a865 2
screamer 0:ea30ba97a865 3 Version 1.0, September 2015
screamer 0:ea30ba97a865 4
screamer 0:ea30ba97a865 5 Redistribution. Redistribution and use in binary form, without
screamer 0:ea30ba97a865 6 modification, are permitted provided that the following conditions are
screamer 0:ea30ba97a865 7 met:
screamer 0:ea30ba97a865 8
screamer 0:ea30ba97a865 9 1) Redistributions must reproduce the above copyright notice and the
screamer 0:ea30ba97a865 10 following disclaimer in the documentation and/or other materials
screamer 0:ea30ba97a865 11 provided with the distribution.
screamer 0:ea30ba97a865 12
screamer 0:ea30ba97a865 13 2) Unless to the extent explicitly permitted by law, no reverse
screamer 0:ea30ba97a865 14 engineering, decompilation, or disassembly of this software is
screamer 0:ea30ba97a865 15 permitted.
screamer 0:ea30ba97a865 16
screamer 0:ea30ba97a865 17 3) Redistribution as part of a software development kit must include the
screamer 0:ea30ba97a865 18 accompanying file named "DEPENDENCIES" and any dependencies listed in
screamer 0:ea30ba97a865 19 that file.
screamer 0:ea30ba97a865 20
screamer 0:ea30ba97a865 21 4) Neither the name of the copyright holder nor the names of its
screamer 0:ea30ba97a865 22 contributors may be used to endorse or promote products derived from
screamer 0:ea30ba97a865 23 this software without specific prior written permission.
screamer 0:ea30ba97a865 24
screamer 0:ea30ba97a865 25 Limited patent license. The copyright holders (and contributors) grant a
screamer 0:ea30ba97a865 26 worldwide, non-exclusive, no-charge, royalty-free patent license to
screamer 0:ea30ba97a865 27 make, have made, use, offer to sell, sell, import, and otherwise
screamer 0:ea30ba97a865 28 transfer this software, where such license applies only to those patent
screamer 0:ea30ba97a865 29 claims licensable by the copyright holders (and contributors) that are
screamer 0:ea30ba97a865 30 necessarily infringed by this software. This patent license shall not
screamer 0:ea30ba97a865 31 apply to any combinations that include this software. No hardware is
screamer 0:ea30ba97a865 32 licensed hereunder.
screamer 0:ea30ba97a865 33
screamer 0:ea30ba97a865 34 If you institute patent litigation against any entity (including a
screamer 0:ea30ba97a865 35 cross-claim or counterclaim in a lawsuit) alleging that the software
screamer 0:ea30ba97a865 36 itself infringes your patent(s), then your rights granted under this
screamer 0:ea30ba97a865 37 license shall terminate as of the date such litigation is filed.
screamer 0:ea30ba97a865 38
screamer 0:ea30ba97a865 39 DISCLAIMER. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND
screamer 0:ea30ba97a865 40 CONTRIBUTORS "AS IS." ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT
screamer 0:ea30ba97a865 41 NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
screamer 0:ea30ba97a865 42 FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
screamer 0:ea30ba97a865 43 HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
screamer 0:ea30ba97a865 44 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED
screamer 0:ea30ba97a865 45 TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
screamer 0:ea30ba97a865 46 PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
screamer 0:ea30ba97a865 47 LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
screamer 0:ea30ba97a865 48 NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
screamer 0:ea30ba97a865 49 SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.