Simple Mbed Cloud Client application using features of K64 & K66
Connect to Mbed Cloud!
This example was customized a bit for FRDM-K66 and FRDM-K64F.
It depends on having an SD Card plugged in for storage of credentials. It could be changed later to use a SPI flash or other storage on a shield or wired in.
The app keeps track of how many times switch 2 (SW2) is pressed. The value can be retrieved via a GET request to Mbed Cloud.
Also, it will blink a pattern based on milisecond (ms) timing values that can be sent from Mbed Cloud. The pattern can be sent with a PUT request and the blinking sequence can be triggered by a POST request.
Diff: mbed_app.json
- Revision:
- 0:e13a8a944e25
- Child:
- 1:1ccf36276cd3
diff -r 000000000000 -r e13a8a944e25 mbed_app.json
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/mbed_app.json Tue Feb 13 10:07:23 2018 +0000
@@ -0,0 +1,36 @@
+{
+ "macros": [
+ "MBEDTLS_USER_CONFIG_FILE=\"mbedTLSConfig_mbedOS.h\"",
+ "MBED_CLIENT_USER_CONFIG_FILE=\"mbed_cloud_client_user_config.h\"",
+ "MBED_CLOUD_CLIENT_USER_CONFIG_FILE=\"mbed_cloud_client_user_config.h\"",
+ "PAL_DTLS_PEER_MIN_TIMEOUT=5000",
+ "MBED_CONF_APP_MAIN_STACK_SIZE=4608"
+ ],
+ "target_overrides": {
+ "*": {
+ "platform.stdio-baud-rate": 115200,
+ "platform.stdio-convert-newlines": true,
+ "mbed-client.event-loop-size": 1024,
+ "mbed-trace.enable": null
+ },
+ "K64F": {
+ "target.mbed_app_start": "0x00020400",
+ "update-client.application-details": "0x00020000",
+ "update-client.bootloader-details": "0x172e4"
+ }
+ },
+ "config": {
+ "developer-mode": {
+ "help": "Enable Developer mode to skip Factory enrollment",
+ "value": 1
+ },
+ "button-pinname": {
+ "help": "PinName for button.",
+ "value": "BUTTON1"
+ },
+ "led-pinname": {
+ "help": "PinName for led, which is attached to led blink resource.",
+ "value": "LED_RED"
+ }
+ }
+}