Mbed OS Device Management example for various ST boards.
This example is known to work great on the following platforms:
- DISCO_L475E_IOT01A - onboard WiFI and onboard QSPI flash. Board specific example using onboard sensors is available here.
- DISCO_F413H - onboard WiFI and onboard QSPI flash.
- DISCO_F469NI - WizFi310 WiFI shield and onboard QSPI flash (see WiFi shield instructions).
- DISCO_F746NG - onboard Ethernet and using onboard QSPI flash.
- DISCO_F769NI - onboard Ethernet and using onboard QSPI flash.
- DISCO_L496AG - WizFi310 WiFI shield and onboard QSPI flash (see WiFi shield instructions).
- NUCLEO_F207ZG - onboard Ethernet and wired SD card (SD card wiring instructions).
- NUCLEO_F412ZG - WizFi310 WiFI shield and SD card shield (see WiFi shield instructions).
- NUCLEO_F429ZI - onboard Ethernet and wired SD card (SD card wiring instructions).
- NUCLEO_F746ZG - onboard Ethernet and wired SD card (SD card wiring instructions).
- NUCLEO_F767ZI - onboard Ethernet and wired SD card (SD card wiring instructions).
- NUCLEO_L476RG - WizFi310 WiFI shield and SD card shield (see WiFi shield instructions).
- NUCLEO_L496ZG - WizFi310 WiFI shield and SD card shield (see WiFi shield instructions).
- NUCLEO_L4R5ZI - WizFi310 WiFI shield and SD card shield (see WiFi shield instructions).
Follow the Quick-Start instructions: https://cloud.mbed.com/quick-start
This example showcases the following device functionality:
- Read ADC temperature and ADC vref, 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.
SD card wiring
The ST Nucleo family of boards don't have storage onboard and therefore you will need an SD card. A limitation on ST Nucleo 144 boards is that there's a conflict between Ethernet and SPI pins on Arduino D11. Due to this, the SD card must be wired to different SPI bus that doesn't conflict with other functionality. The image below provide instructions on how to wire an SD card to a non-conflicting SPI instance.
If you are not a first-time Pelion Device Management user your device's SD card may already have connect and update certificates on it. If this is the case, remove and manually format your micro SD card, flash the binary to the device and then re-insert your micro SD card.
WiFi shield setup/wiring
Some ST Nucleo and Discovery boards don't have IP connectivity option, but bundled with a WiFi shield, they can take benefit of full device management capabilities. See links to reference images below on how to wire WizFI310 WiFi shield and/or SD card shield:
- ST DISCO_F469NI + WizFi310 WiFi Shield
- ST DISCO_L496AG + WizFi310 WiFi Shield
- ST NUCLEO_F412ZG + WizFi310 WiFi Shield + SD card shield
- ST NUCLEO_L476RG + WizFi310 WiFi Shield + SD card shield
- ST NUCLEO_L496ZG + WizFi310 WiFi Shield + SD card shield
- ST NUCLEO_L4R5ZI + WizFi310 WiFi Shield + SD card shield
Use this example with Mbed CLI
1. Import the application into your desktop:
mbed import /teams/ST/code/pelion-example-common cd pelion-example-common
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 <TARGET_BOARD>
(supported toolchains : GCC_ARM / ARM / IAR)
Revision 13:433fcff306ad, committed 4 months ago
- Sun Dec 16 13:35:34 2018 +0000
- Commit message:
- Inline documentation to main application
Changed in this revision
|main.cpp||Show annotated file Show diff for this revision Revisions of this file|
--- a/main.cpp Sun Dec 16 13:31:22 2018 +0000 +++ b/main.cpp Sun Dec 16 13:35:34 2018 +0000 @@ -26,7 +26,7 @@ // This is great because things such as network operations are illegal in ISR, so updating a resource in a button's fall() function is not allowed EventQueue eventQueue; -// Default network interface object +// Default network interface object. Don't forget to change the WiFi SSID/password in mbed_app.json if you're using WiFi. NetworkInterface *net = NetworkInterface::get_default_instance(); // Default block device available on the target board