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

targets/TARGET_STM32L475xG_SRAM2/device/TOOLCHAIN_ARM_MICRO/stm32l475xx.sct@31:da14aa77f977, 2019-03-11 (annotated)

Committer:: screamer
Date:: Mon Mar 11 11:28:07 2019 +0000
Revision:: 31:da14aa77f977
Parent:: 30:15743b79c6cb

Revert back to Mbed OS 5.10.4 due to issues to fit in RAM2 on GCC_ARM

Who changed what in which revision?

User	Revision	Line number	New contents of line
screamer	28:0e774865873d	1	#! armcc -E
screamer	28:0e774865873d	2	; Scatter-Loading Description File
screamer	28:0e774865873d	3	;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
screamer	28:0e774865873d	4	; Copyright (c) 2015, STMicroelectronics
screamer	28:0e774865873d	5	; All rights reserved.
screamer	28:0e774865873d	6	;
screamer	28:0e774865873d	7	; Redistribution and use in source and binary forms, with or without
screamer	28:0e774865873d	8	; modification, are permitted provided that the following conditions are met:
screamer	28:0e774865873d	9	;
screamer	28:0e774865873d	10	; 1. Redistributions of source code must retain the above copyright notice,
screamer	28:0e774865873d	11	; this list of conditions and the following disclaimer.
screamer	28:0e774865873d	12	; 2. Redistributions in binary form must reproduce the above copyright notice,
screamer	28:0e774865873d	13	; this list of conditions and the following disclaimer in the documentation
screamer	28:0e774865873d	14	; and/or other materials provided with the distribution.
screamer	28:0e774865873d	15	; 3. Neither the name of STMicroelectronics nor the names of its contributors
screamer	28:0e774865873d	16	; may be used to endorse or promote products derived from this software
screamer	28:0e774865873d	17	; without specific prior written permission.
screamer	28:0e774865873d	18	;
screamer	28:0e774865873d	19	; THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
screamer	28:0e774865873d	20	; AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
screamer	28:0e774865873d	21	; IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
screamer	28:0e774865873d	22	; DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
screamer	28:0e774865873d	23	; FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
screamer	28:0e774865873d	24	; DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
screamer	28:0e774865873d	25	; SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
screamer	28:0e774865873d	26	; CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
screamer	28:0e774865873d	27	; OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
screamer	28:0e774865873d	28	; OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
screamer	28:0e774865873d	29	;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
screamer	28:0e774865873d	30
screamer	28:0e774865873d	31	#if !defined(MBED_APP_START)
screamer	28:0e774865873d	32	#define MBED_APP_START 0x08000000
screamer	28:0e774865873d	33	#endif
screamer	28:0e774865873d	34
screamer	28:0e774865873d	35	#if !defined(MBED_APP_SIZE)
screamer	28:0e774865873d	36	#define MBED_APP_SIZE 0x100000
screamer	28:0e774865873d	37	#endif
screamer	28:0e774865873d	38
screamer	28:0e774865873d	39	; 1MB FLASH (0x100000) + 128KB SRAM (0x20000)
screamer	28:0e774865873d	40	LR_IROM1 MBED_APP_START MBED_APP_SIZE { ; load region size_region
screamer	28:0e774865873d	41
screamer	28:0e774865873d	42	ER_IROM1 MBED_APP_START MBED_APP_SIZE { ; load address = execution address
screamer	28:0e774865873d	43	*.o (RESET, +First)
screamer	28:0e774865873d	44	*(InRoot$$Sections)
screamer	28:0e774865873d	45	.ANY (+RO)
screamer	28:0e774865873d	46	}
screamer	28:0e774865873d	47
screamer	31:da14aa77f977	48	RW_IRAM1 0x20000000 0x00018000 { ; RW data 96k L4-SRAM1
screamer	28:0e774865873d	49	.ANY (+RW +ZI)
screamer	28:0e774865873d	50	}
screamer	28:0e774865873d	51	; Total: 98 vectors = 392 bytes (0x188) to be reserved in RAM
screamer	28:0e774865873d	52	RW_IRAM2 (0x10000000+0x188) (0x08000-0x188) { ; RW data 32k L4-ECC-SRAM2 retained in standby
screamer	28:0e774865873d	53	.ANY (+RW +ZI)
screamer	28:0e774865873d	54	}
screamer	28:0e774865873d	55
screamer	28:0e774865873d	56	}
screamer	28:0e774865873d	57