pelion-example-rhombio-l476dmw1k - Mbed OS and Pelion Device Management example over…

rhomb.io » Code » pelion-example-rhombio-l476dmw1k

rhomb.io / Mbed OS pelion-example-rhombio-l476dmw1k

Mbed OS and Pelion Device Management example over WIFI for RHOMBIO_L476DMW1K IoT kit

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:

RHOMBIO_L476DMW1K over WiFI and using onboard QSPI flash.

/media/uploads/galonso/rhombio_l476dmw1k_kit_assembled.png

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

Example functionality

This example showcases the following device functionality:

Read onboard MCU ADC temperature and MCU ADC voltage reference, 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.
External sensors can be easily added to the kit and then sensor readings reported as Pelion LWM2M resources.

/media/uploads/galonso/temperature_-_sensor_value_-_pelion_device_management_portal.png

Use this example with Mbed CLI

1. Import the application into your desktop:

mbed import https://os.mbed.com/teams/Rhombio/code/pelion-example-rhombio-l476dmw1k

cd pelion-example-rhombio-l476dmw1k

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 RHOMBIO_L476DMW1K -f

(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: 0000000000000000000000000000000000000000
[BOOT] OEM: 0000000000000000000000000000000000000000
[BOOT] Layout: 0 800D24C
[BOOT] Active firmware integrity check:
[BOOT] SHA256: 9036E19F1414720659B2C2FAC8855F621AF533BA211D930119720E7A2BD60BF2
[BOOT] Version: 1558516039
[BOOT] Slot 0 is empty
[BOOT] Active firmware up-to-date
[BOOT] Application's start address: 0x8010400
[BOOT] Application's jump address: 0x8010889
[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.

Connecting to the network using Wifi...
Connected to the network successfully. IP address: 192.168.1.201
Initializing Pelion Device Management Client...
Initialized Pelion Client. Registering...
Registered to Pelion Device Management. Endpoint Name: 016a***********************10006d
                                                             
ADC temp: 23.1746 C,  vref: 0.3665 V         
                                                             
ADC temp: 23.2234 C,  vref: 0.3663 V

bootloader/LICENSE@0:9ff56a0e4c0d, 2019-05-21 (annotated)

Committer:: galonso@rhomb.io
Date:: Tue May 21 18:15:26 2019 +0200
Revision:: 0:9ff56a0e4c0d

first commit

Who changed what in which revision?

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