Richard Kuo / Mbed OS NTOUEE-mbed-Client

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

Diff: README.md

Revision:
22:e39e09d79a63
Parent:
21:b88cdeb5b302
Child:
37:9a9428fc4b26
diff -r b88cdeb5b302 -r e39e09d79a63 README.md
--- a/README.md	Fri Oct 21 09:30:10 2016 +0100
+++ b/README.md	Mon Oct 24 12:00:08 2016 +0100
@@ -18,6 +18,19 @@
 * 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.
 
+## Supported Target hardware configurations
+
+ This example has been tested in following configuration
+ * K64F + NXP MCR20 15.4 shield (mesh `NANOSTACK_FULL` mode)
+ * NUCLEO_F429ZI + ATMEL AT233 15.4 shield (mesh `LOWPAN_ROUTER` mode)
+ * K64F (Ethernet)
+ * NUCLEO_F429ZI (Ethernet)
+ * UBLOX_EVK_ODIN_W2 (Ethernet)
+ * K64F + GROVE SEEED shield (Wifi)
+ * NUCLEO_F429ZI + GROVE SEEED shield (Wifi)
+
+Apart from this, this example can work on other mbed OS supported hardware boards which support any of the given network interface including Ethernet, WiFi, Mesh (6LoWPAN) or Thread, provided the configuration fulfills condition that the target hardware has TLS entropy implemented for it and the complete example configuration of mbed Client, selected network interface and mbed OS components fits into hardware's given memory size (Flash size and RAM size). 
+
 ## Requirements for non-K64F boards
 
 *   This example requires TLS functionality to be enabled on mbed TLS.