George Djabarov / Mbed OS mbed-os-example-mesh-minimal
Revision:
17:ee2610e1cb78
Parent:
13:4a0466077538
Child:
19:f55c7983f8ab
--- a/README.md	Fri Sep 30 16:00:10 2016 +0100
+++ b/README.md	Sun Oct 02 13:45:09 2016 +0100
@@ -67,6 +67,14 @@
 
         mbed compile -m K64F -t GCC_ARM
 
+**NOTE:** Please make sure that the _mbed_app.json_ is also updated to reflect the usage of a particular RF driver. For example,
+
+```json
+      "radio-type":{
+            "help": "options are ATMEL, MCR20",
+            "value": "ATMEL"
+        },
+```
 ## Important note (Multi-platform support)
 
 mbed OS provides you with total control of the device. However, some defaults are always loaded if you do not provide proper information regarding them. This becomes evident when you switch among platforms. On some platforms, a particular pin might be reserved for a particular functionality (depending upon the MCU) which thus cannot be used generally. If the Ardurino form factor is not available, or the required peripherial is on a different pin, the pins values can be set manually. For example, you can add *"atmel-rf.spi-rst": "D4"* to your `mbed_app.json` file. This will set the SPI_RST pin to D4 of the GPIO.
@@ -75,7 +83,7 @@
 {
     "target_overrides": {
         "*": {
-            "target.features_add": ["IPV6", "COMMON_PAL"],
+            "target.features_add": ["NANOSTACK", "LOWPAN_ROUTER", "COMMON_PAL"],
             "atmel-rf.spi-rst": "D4"
         }
     }