ST / Mbed OS 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

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

mbed_app.json@7:816e19453a7f, 2018-07-13 (annotated)

Committer:
MarceloSalazar
Date:
Fri Jul 13 08:24:42 2018 +0000
Revision:
7:816e19453a7f
Parent:
6:e0e1e1b93099
Child:
9:265744785d33
Add _RTE_ workaround for issue #7422 in 5.9.2

Who changed what in which revision?

UserRevisionLine numberNew contents of line
adustm 1:e86b1cffc402 1 {
adustm 1:e86b1cffc402 2 "macros": [
adustm 1:e86b1cffc402 3 "MBEDTLS_USER_CONFIG_FILE=\"mbedTLSConfig_mbedOS.h\"",
adustm 4:cf7342047b4d 4 "PAL_USER_DEFINED_CONFIGURATION=\"sotp_fs_config_MbedOS.h\"",
adustm 1:e86b1cffc402 5 "MBED_CLIENT_USER_CONFIG_FILE=\"mbed_cloud_client_user_config.h\"",
adustm 1:e86b1cffc402 6 "MBED_CLOUD_CLIENT_USER_CONFIG_FILE=\"mbed_cloud_client_user_config.h\"",
adustm 1:e86b1cffc402 7 "PAL_DTLS_PEER_MIN_TIMEOUT=5000",
adustm 5:8d7b1da4f6fa 8 "MBED_CONF_APP_MAIN_STACK_SIZE=6000",
adustm 4:cf7342047b4d 9 "ARM_UC_USE_PAL_BLOCKDEVICE=1",
MarceloSalazar 7:816e19453a7f 10 "MBED_CLOUD_CLIENT_UPDATE_STORAGE=ARM_UCP_FLASHIAP_BLOCKDEVICE",
MarceloSalazar 7:816e19453a7f 11 "_RTE_"
adustm 1:e86b1cffc402 12 ],
adustm 1:e86b1cffc402 13 "target_overrides": {
adustm 1:e86b1cffc402 14 "*": {
adustm 1:e86b1cffc402 15 "platform.stdio-baud-rate": 115200,
adustm 1:e86b1cffc402 16 "platform.stdio-convert-newlines": true,
adustm 4:cf7342047b4d 17 "update-client.storage-address" : "(1024*1024*64)",
adustm 4:cf7342047b4d 18 "update-client.storage-size" : "(1024*1024*2)",
adustm 4:cf7342047b4d 19 "update-client.storage-locations": "1",
adustm 1:e86b1cffc402 20 "mbed-trace.enable": null
adustm 4:cf7342047b4d 21 },
adustm 4:cf7342047b4d 22 "DISCO_L475VG_IOT01A": {
adustm 4:cf7342047b4d 23 "sotp-section-1-address" : "(0x08000000+((1024-32)*1024))",
adustm 4:cf7342047b4d 24 "sotp-section-1-size" : "(16*1024)",
adustm 4:cf7342047b4d 25 "sotp-section-2-address" : "(0x08000000+((1024-16)*1024))",
adustm 4:cf7342047b4d 26 "sotp-section-2-size" : "(16*1024)",
adustm 4:cf7342047b4d 27 "sotp-num-sections" : 2
adustm 6:e0e1e1b93099 28 },
adustm 6:e0e1e1b93099 29 "DISCO_F413ZH": {
adustm 6:e0e1e1b93099 30 "sotp-section-1-address" : "(0x08000000+((1536-256)*1024))",
adustm 6:e0e1e1b93099 31 "sotp-section-1-size" : "(128*1024)",
adustm 6:e0e1e1b93099 32 "sotp-section-2-address" : "(0x08000000+((1536-128)*1024))",
adustm 6:e0e1e1b93099 33 "sotp-section-2-size" : "(128*1024)",
adustm 6:e0e1e1b93099 34 "sotp-num-sections" : 2
adustm 1:e86b1cffc402 35 }
adustm 4:cf7342047b4d 36
adustm 1:e86b1cffc402 37 },
adustm 1:e86b1cffc402 38 "config": {
adustm 4:cf7342047b4d 39 "format-storage-layer-on-error": {
adustm 4:cf7342047b4d 40 "help": "Whether to format the storage layer when it cannot be read - always disable for production devices!",
adustm 4:cf7342047b4d 41 "value": 1
adustm 4:cf7342047b4d 42 },
adustm 1:e86b1cffc402 43 "developer-mode": {
adustm 1:e86b1cffc402 44 "help": "Enable Developer mode to skip Factory enrollment",
adustm 1:e86b1cffc402 45 "value": 1
adustm 1:e86b1cffc402 46 },
adustm 1:e86b1cffc402 47 "wifi-ssid": {
adustm 1:e86b1cffc402 48 "help": "WiFi SSID",
adustm 1:e86b1cffc402 49 "value": "\"SSID\""
adustm 1:e86b1cffc402 50 },
adustm 1:e86b1cffc402 51 "wifi-password": {
adustm 1:e86b1cffc402 52 "help": "WiFi Password",
adustm 1:e86b1cffc402 53 "value": "\"PASSWORD\""
adustm 1:e86b1cffc402 54 },
adustm 4:cf7342047b4d 55 "sotp-section-1-address": {
adustm 4:cf7342047b4d 56 "help": "Flash sector address for SOTP sector 1",
adustm 4:cf7342047b4d 57 "macro_name": "PAL_INTERNAL_FLASH_SECTION_1_ADDRESS",
adustm 4:cf7342047b4d 58 "value": null
adustm 1:e86b1cffc402 59 },
adustm 4:cf7342047b4d 60 "sotp-section-1-size": {
adustm 4:cf7342047b4d 61 "help": "Flash sector size for SOTP sector 1",
adustm 4:cf7342047b4d 62 "macro_name": "PAL_INTERNAL_FLASH_SECTION_1_SIZE",
adustm 4:cf7342047b4d 63 "value": null
adustm 1:e86b1cffc402 64 },
adustm 4:cf7342047b4d 65 "sotp-section-2-address": {
adustm 4:cf7342047b4d 66 "help": "Flash sector address for SOTP sector 2",
adustm 4:cf7342047b4d 67 "macro_name": "PAL_INTERNAL_FLASH_SECTION_2_ADDRESS",
adustm 4:cf7342047b4d 68 "value": null
adustm 1:e86b1cffc402 69 },
adustm 4:cf7342047b4d 70 "sotp-section-2-size": {
adustm 4:cf7342047b4d 71 "help": "Flash sector size for SOTP sector 2",
adustm 4:cf7342047b4d 72 "macro_name": "PAL_INTERNAL_FLASH_SECTION_2_SIZE",
adustm 4:cf7342047b4d 73 "value": null
adustm 1:e86b1cffc402 74 },
adustm 4:cf7342047b4d 75 "sotp-num-sections": {
adustm 4:cf7342047b4d 76 "help": "Number of SOTP sections",
adustm 4:cf7342047b4d 77 "macro_name": "PAL_INT_FLASH_NUM_SECTIONS",
adustm 4:cf7342047b4d 78 "value": null
adustm 1:e86b1cffc402 79 }
adustm 1:e86b1cffc402 80 }
adustm 1:e86b1cffc402 81 }