pelion-example-disco-iot01 - Mbed OS and Pelion Device Management example over…

ST » Code » pelion-example-disco-iot01

Mbed OS and Pelion Device Management example over WIFI for DISCO_L475VG_IOT01 board

Dependencies: X_NUCLEO_COMMON ST_INTERFACES

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 on the following platforms:

DISCO_L475E_IOT01A over WiFI and using onboard QSPI flash.

DISCO_L475E_IOT01A

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

Example functionality

This example showcases the following device functionality:

Read onboard temperature and humidity sensors, 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.
Uses all onboard sensors and reports them as Pelion LWM2M resources.

/media/uploads/screamer/pelion_st_humidity_reading.png?v=2

Use this example with Mbed CLI

1. Import the application into your desktop:

mbed import https://os.mbed.com/teams/ST/code/pelion-example-disco-iot01

cd pelion-example-disco-iot01

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 DISCO_L475VG_IOT01A

(supported toolchains : GCC_ARM / ARM / IAR)

5. You can connect on a virtual terminal/COM port to the platform using:

mbed sterm -b 115200

This should give you an output similar to:

[BOOT] Mbed Bootloader
[BOOT] ARM: 00000000000000000000
[BOOT] OEM: 00000000000000000000
[BOOT] Layout: 0 80096F4
[BOOT] Active firmware integrity check:
[BOOT] SHA256: 0660E360D432225D5251461998FD8617B017098C5F1F90D5FB607BF8C27ED530
[BOOT] Version: 1553615309
[BOOT] Slot 0 is empty
[BOOT] Active firmware up-to-date
[BOOT] Application's start address: 0x8010400
[BOOT] Application's jump address: 0x8011041
[BOOT] Application's stack address: 0x20018000
[BOOT] Forwarding to application...

Starting Simple Pelion Device Management Client example
You can hold the user button during boot to format the storage and change the device identity.

Sensors configuration:
Invalid new address!
HTS221  humidity & temperature    = 0xBC
LPS22HB pressure & temperature    = 0xB1
LIS3MDL magnetometer              = 0x3D
LSM6DSL accelerometer & gyroscope = 0x6A

Connecting to the network using Wifi...
Connected to the network successfully. IP address: 192.168.1.3
Initializing Pelion Device Management Client...
Initialized Pelion Client. Registering...
Registered to Pelion Device Management. Endpoint Name: 0169********************001002d5

ADC temp:     23.0037 C,  vref:      0.3661 V
HTS221 temp:   28.700 C,  humidity:   31.90 %
LPS22HB temp:  29.600 C,  pressure: 1032.01 mbar
LIS3MDL mag:    0.217 x,  -0.284 y,  -0.053 z [gauss]
LSM6DSL acc:    0.005 x,  -0.014 y,   1.029 z [g]
LSM6DSL gyro:   0.910 x,  -0.910 y,   1.120 z [dps]
VL53L0X dist:    1855 mm

bootloader/LICENSE@36:aaf44d2a6c33, 2020-03-13 (annotated)

Committer:: chris
Date:: Fri Mar 13 13:18:07 2020 +0000
Revision:: 36:aaf44d2a6c33
Parent:: 9:265744785d33

First revision

Who changed what in which revision?

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