This is a simple mbed client example demonstrating, registration of a device with mbed Device Connector and reading and writing values as well as deregistering on different Network Interfaces including Ethernet, WiFi, 6LoWPAN ND and Thread respectively.

Fork of mbed-os-example-client by mbed-os-examples

Revision:
7:9a1ee269650b
Parent:
6:8fff223f3f84
Child:
9:dcc4b552c03a
diff -r 8fff223f3f84 -r 9a1ee269650b README.md
--- a/README.md	Tue Aug 02 10:00:21 2016 +0100
+++ b/README.md	Tue Aug 02 12:30:18 2016 +0100
@@ -18,6 +18,17 @@
 * mbed 6LoWPAN shield (AT86RF212B/[AT86RF233](https://firefly-iot.com/product/firefly-arduino-shield-2-4ghz/)) for 6LoWPAN ND and Thread.
 * Ethernet cable and connection to the internet.
 
+## Requirements for non K64F board
+This example application is primarily designed for FRDM-K64F board but you can also use other mbed OS supported boards to run this example application , with some minor modifications for setup.
+* To get the application registering successfully on non K64F boards , you need Edit the `mbed_app.json` file to add `NULL_ENTROPY`  feature for mbedTLS:
+
+```
+""macros": ["MBEDTLS_USER_CONFIG_FILE=\"mbedtls_mbed_client_config.h\"",
+            "MBEDTLS_NO_DEFAULT_ENTROPY_SOURCES",
+            "MBEDTLS_TEST_NULL_ENTROPY"],
+```
+* On non K64F boards, there is no unregistration functionality and button press is simulated through timer ticks incrementing every 15 seconds.
+
 ## Required software
 
 * [ARM mbed account](https://developer.mbed.org/account/login/?next=/).