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:
- 12:0a894bf1f5f2
- Parent:
- 9:ae1f6fe932dc
- Child:
- 13:49062a0d117e
--- a/mbed_app.json Thu May 10 16:02:35 2018 -0500 +++ b/mbed_app.json Fri May 18 21:28:25 2018 +0000 @@ -17,7 +17,22 @@ "update-client.storage-size" : "(1024*1024*2)", "update-client.storage-locations": "1", "mbed-trace.enable": null - } + }, + "K64F": { + "sotp-section-1-address" : "0xFE000", + "sotp-section-1-size" : "0x1000", + "sotp-section-2-address" : "0xFF000", + "sotp-section-2-size" : "0x1000", + "sotp-num-sections" : 2 + }, + "K66F": { + "sotp-section-1-address" : "0x1FE000", + "sotp-section-1-size" : "0x1000", + "sotp-section-2-address" : "0x1FF000", + "sotp-section-2-size" : "0x1000", + "sotp-num-sections" : 2 + } + }, "config": { "format-storage-layer-on-error": { @@ -48,6 +63,11 @@ "help": "Flash sector size for SOTP sector 2", "macro_name": "PAL_INTERNAL_FLASH_SECTION_2_SIZE", "value": null - } + }, + "sotp-num-sections": { + "help": "Number of SOTP sections", + "macro_name": "PAL_INT_FLASH_NUM_SECTIONS", + "value": null + } } }