Merge branch 'oob_test_mbed-os-5.4' into oob_update

Author: yogpan01

GW_Binary/gateway6LoWPANDynamic.bin

@@ -110,27 +110,17 @@ If your connection type is `MESH_THREAD` then you may want to use the THREAD_ROU
 
 6LoWPAN ND and Thread use IPv6 for connectivity. Therefore, you need to verify first that you have a working IPv6 connection. To do that, ping the Connector IPv6 address `2607:f0d0:2601:52::20` from your network.
 
-<span class="notes">**Note:** If you are using the [k64f-border-router](https://github.com/ARMmbed/k64f-border-router) (that can be used only as a 6LoWPAN BR and only with FRDM-K64F), you need to enable another security feature. By default, the `k64f-border-router` uses `PSK` as security.</span>
+#### Border router
 
-You can enable the security here on your mbed-os-example-client application, for example:
+There are two options for border router.
 
-```json
-    "target_overrides": {
-        "*": {
-            "mbed-mesh-api.6lowpan-nd-security-mode": "PSK",
-        }
-	}
-```
+##### Nanostack-border-router
 
-Alternatively, you can remove the link layer security from the `k64f-border-router`. To do that, change the [mbed_app.json](https://github.com/ARMmbed/k64f-border-router/blob/master/mbed_app.json) fetched from the `k64f-border-router` repository, for example: 
+ The [Nanostack-border-router](https://github.com/ARMmbed/nanostack-border-router-private) can be configured and built for the 6LoWPAN ND or Thread mode.  
 
-```json
-    "config": {
-            "security-mode": "NONE",
-        }
-```
+##### mbed gateway
 
-#### mbed gateway
+The mbed gateway is a binary release only.
 
 To connect the example application in 6LoWPAN ND or Thread mode to Connector, you need to set up an mbed 6LoWPAN gateway router as follows:
 
@@ -285,13 +275,12 @@ To build the example using mbed CLI:
     mbed import mbed-os-example-client
     ```
 
-3. Copy the relevant example configuration file from configs/xxx.json to mbed_app.json and
-   [Configure](#application-setup) the client application.
-
 4. To build the application, select the hardware board and build the toolchain using the command:
 
-    ```
-    mbed compile -m K64F -t GCC_ARM -c
+	Specify the config file in the build command, for example for 6LoWPAN
+
+	```
+    mbed compile -m K64F -t GCC_ARM -c --app-config configs/6lowpan_Atmel_RF.json
     ```
 
     mbed CLI builds a binary file under the project’s `BUILD/` directory.
@@ -409,4 +398,8 @@ This should resolve the issue:
 ```		
 cp configs/eth-wifi-mbedignore ./.mbedignore		
 ```		
- 		
+
+#### Linking problems?
+
+Due to re-structuring of mbed-client-c the CoAP library might exist twice in your directory tree, if you updated to the latest version of this repository. If moving from an older mbedOS version mbedOS 5.4 based release, please run `mbed deploy` to ensure all repos get updated.
+

GW_Binary/gateway6LoWPANStatic.bin

@@ -15,8 +15,8 @@
             "target.features_add": ["NANOSTACK", "THREAD_ROUTER", "COMMON_PAL"],
             "platform.stdio-baud-rate": 115200,
             "platform.stdio-convert-newlines": true,
-            "mbed-mesh-api.thread-config-channel": 12,
-            "mbed-mesh-api.thread-config-panid": "0xDEFA",
+            "mbed-mesh-api.thread-config-channel": 22,
+            "mbed-mesh-api.thread-config-panid": "0x0700",
             "mbed-trace.enable": 0
         }
     }

GW_Binary/gatewayThreadDynamic.bin

@@ -1,2 +1,2 @@
-https://github.com/ARMmbed/mbed-client/#d41459d8b514d72d525e761fb4e34031e09f76e7
+https://github.com/ARMmbed/mbed-client/#52e65b46dff7935024e91ed045eadaab298149b6
 

GW_Binary/gatewayThreadStatic.bin

@@ -1 +1 @@
-https://github.com/ARMmbed/mbed-os/#305f5c491e34d86098e9da91b322017549c189ff
+https://github.com/ARMmbed/mbed-os/#305f5c491e34d86098e9da91b322017549c189ff