Pelion / Mbed workshop

1. © 2019 Arm Limited
Connect a device
to Pelion

2. © 2019 Arm Limited2
Download these slides!
http://bit.ly/Pelion2020

3. © 2019 Arm Limited
Pre-Req’s

4. © 2019 Arm Limited4
Before we get started please….
• You must have a laptop with a USB port that supports mass storage devices without
encryption.
• Windows – Install ST Link Drivers
https://www.st.com/en/development-tools/stsw-link009.html
• Serial Terminal – PuTTY / TeraTerm / CoolTerm
• Visit mbed.com and sign up for a new account
• make sure to confirm your email address!
• Download these slides – http://bit.ly/Pelion2020

5. © 2019 Arm Limited
Lab 1
Pelion Provisioning

6. © 2019 Arm Limited6
Get to know your IoT Discovery board - Highlights
Debugger USB Port
Use this USB port
Wi-Fi module
User Push Button
Reset Button
STM32L475 MCU
1MB Flash
128KB SRAM
On board Debugger
Board also Includes:
• 64Mb QSPI Flash
• Temperature / Humidity Sensor
• Temperature / Pressure Sensor
• Time of flight Sensor (Distance)
• Magnetometer
• Accelerometer
• Gyroscope
• BTLE Module
• Sub-GHz Radio
• And More!
https://os.mbed.com/platforms/ST-Discovery-L475E-IOT01A/
User LED1

7. © 2019 Arm Limited7
Pelion Client (1)
• Point your browser to: https://mbed.com/
• Click log in/Sign up – if you have credentials login, if you don’t sign up
• If you just signed up be sure to validate your email address!
• Now click “Try Pelion Device Management with Mbed”

8. © 2019 Arm Limited8
Pelion Client (2)
• Activate your Pelion Device Management accoint”

9. © 2019 Arm Limited9
Pelion Client (3)
• Scroll down and launch the Pelion DM portal.

10. © 2019 Arm Limited10
Pelion Client (4)
• Select “Log in with Mbed.com”
• When prompted accept the
license agreement

11. © 2019 Arm Limited11
Pelion Client (5)
• Open a new tab and navigate to:
• https://os.mbed.com/platforms/ST-Discovery-L475E-IOT01A/
• Click on “Add to your Mbed Compiler”

12. © 2019 Arm Limited12
Pelion Client (7)
• Navigate to:
• https://os.mbed.com/teams/ST/code/pelion-example-disco-iot01/
• Select “Import into Compiler”, this will launch the on-line compiler

13. © 2019 Arm Limited13
Pelion Client – Creating Device Certificate (8)
• Select “Import” using default settings.
• Click on the ”Pelion Device Management” Button
• Select “Manage Connect Certificates”

14. © 2019 Arm Limited14
Pelion Client - Creating Device Certificate (9)
• Authenticate your API key if prompted
• Click “Create”

15. © 2019 Arm Limited15
Pelion Client - Creating Device Certificate (10)
• Give your device certificate a name you will recognize
• Click ”OK”

16. © 2019 Arm Limited16
Pelion Client - Creating Device Certificate (11)
• Select your device certificate
• Click ”OK”

17. © 2019 Arm Limited17
Pelion Client - Creating Device Certificate (12)
• Click “Ok” to override the ‘mbed_cloud_dev_credentials.c”

18. © 2019 Arm Limited18
Pelion Client - Creating Update Certificate (12)
• Reselect “Pelion Device Management and select “Apply Update Certificate”
• Select “Create” then confirm when prompted

19. © 2019 Arm Limited19
Pelion Client - Creating Update Certificate (12)
• The System will create a private key for you, download and save the private key
file
• You will need this later to create the manifest needed to perform udates later
in this exercise.

20. © 2019 Arm Limited20
You have finished Lab 1

21. © 2019 Arm Limited
Lab 2
Connecting a new device

22. © 2019 Arm Limited22
Pelion Client – Configuring the client to your device (13)
• Double click on mbed_app.json to open the file
• Edit lines 9 & 10 to the SSID and password provided for your location
• SSID = ???
• Password = ???
• Be careful just to replace the text SSID & password

23. © 2019 Arm Limited23
Pelion Client – Configuring the client to your device (14)
• Insure that DISCO-L475VG-IOT01 is the selected target
• Open “main.cpp”, Find line 48 and comment it out
• Click “Compile”
• This compiles your code and creates a binary that combines your application
with a bootloader

24. © 2019 Arm Limited24
Pelion Client – Configuring the client to your device (15)
• MAC users click “Save File”
• Depending on browser you may just be able to drag the binary to the
DIS_L4IOT drive
• PC users can drag and drop the binary from your “Downloads” folder

25. © 2019 Arm Limited25
Pelion Client – Configuring the client to your device (16)
• Drag the downloaded file into the Mbed drive.
• Open your serial terminal - > set the COM port to the port your board is
connected to -> set baud rate to 115200 -> click “Connect”
• Once the devices has connected to Wi-Fi and successfully registered to Pelion
you will see your device ID printed to the serial terminal.

26. © 2019 Arm Limited26
Device Directory Return to your cloud portal tab, select “Device Directory”

27. © 2019 Arm Limited27
Device Directory (2) Deep dive to device
Troubleshooting:
If your device is not listed hold down the Blue Button on your board and
Push the Black Reset Button, continue to hold the Blue Button while your
board boots up. This erases any credentials from previous users and forces
the board to re-connect through the Pelion Bootstrap server.

28. © 2019 Arm Limited28
Device Directory (3)
ID
Status
Type

29. © 2019 Arm Limited29
Device Directory (4)

30. © 2019 Arm Limited30
Device Directory (5)
• Select the “button count” resource’s URI
• This will create a “subscription” to the resource
• Any time the resource changes it will be sent to the portal.

31. © 2019 Arm Limited31
Device Directory (6)
• Now we can see live data from the device
• Close the window when done

32. © 2019 Arm Limited32
Device Directory (7)
• Select the “LED State” resource
• Select Edit

33. © 2019 Arm Limited33
Device Directory (8)
• Select the “Put”, , set hhe value to 1 or 0 (1=LED on, 0 = LED off) then“Submit”,
• For further exploration after the lab look into the code to see how these
resources are defined
• We have now seen how data and execute commands can be sent to your
device

34. © 2019 Arm Limited34
You have finished Lab 2

35. © 2019 Arm Limited
Lab 3
FOTA

36. © 2019 Arm Limited36
FOTA (1)
• Open main.cpp and find line 48, uncomment it
• Under “Pelion Device Management select “Publish Firmware Update”
• This will compile your application but will not combine it with the bootloader
• Give your update a name and description, click “Publish”
• Select your saved private key and click “OK”
• This creates a FOTA manifest and uploads it and the compiled binary to your Pelion
account.
• Select “Open Device Management Portal”

37. © 2019 Arm Limited37
FOTA (2)
• This takes us directly to the “New update campaign” wizard, just click “Next”
• Select the manifest you just created and click “Next”
• Select the device you want to update and click “Next”
• Click on “Finish”
• Click “Start” to run the campaign
• Since this cannot be undone the system will ask you to verify that you want to proceed,
Click “Start”

38. © 2019 Arm Limited38
FOTA (3)
• On your serial terminal you can see the new image downloading.
• While downloading you can return to the button push resource and observe that the
device is fully operational while the new image is downloading.
• The download is designed to send data in small packets to insure that network and
device operation is not compromised.
• This is user configurable.
• After the download in complete and has been applied return to your Pelion portal and
note that the update is marked as successful.
• Return to your device in the Pelion Portal and observe that all of the additional sensors
are now present.
• Pelion has dynamically responded to the new device configuration

39. © 2019 Arm Limited39
FOTA (4)
• Explore the many live sensors exposed!

40. © 2019 Arm Limited40
Closing thoughts
• This is a very simplistic example.
• In a real system you would use the “filter” capability of Pelion to select ranges of
devices based on a variety of parameters.
• Fun things to try:
• Rollback protection: Try to reload the binary you created in Lab 1, it will upload, but on boot the bootloader will
detect the out of date firmware and reapply the update from serial flash.
• Flash Protection: Create a new campaign and after downloading wait for the message on your serial terminal
– “Updating active firmware using slot 0”
– Remove and reapply power, we have intentionally corrupted flash
– Look for the message “[ERR ] Active firmware integrity check failed”
▪ Active firmware is signed, if integrity is lost the bootloader will not run it
– Instead will apply the stored good code.

41. © 2019 Arm Limited41
You have finished Lab 3

42. 4242
Thank You!
Danke!
Merci!
谢谢!
ありがとう!
Gracias!
Kiitos!
감사합니다
धन्यवाद
© 2019 Arm Limited