Merge branch 'development' of https://github.com/ARMmbed/mbed-os-5-docs into development

Author: iriark01

docs.json

@@ -1553,6 +1553,15 @@
         "source": "https://github.com/ARMmbed/mbed-os",
         "branch": "feature-hal-spec-sai"
     },
+    {
+        "title": "feature-hal-spec-spi doxygen",
+        "description": "The full mbed OS API documentation in doxygen format",
+        "slug": "feature-hal-spec-spi-doxy",
+        "hidden": true,
+        "type": "doxygen",
+        "source": "https://github.com/ARMmbed/mbed-os",
+        "branch": "feature-hal-spec-spi"
+    }, 
     {
         "title": "feature-hal-spec-watchdog doxygen",
         "description": "The full mbed OS API documentation in doxygen format",

docs/api/networkinterfaces/MeshInterface.md

@@ -43,7 +43,7 @@ See the example application [mbed-os-example-mesh-minimal](https://github.com/AR
 
 The application below demonstrates a simple light control application, where devices can control the LED status of all devices in the network. You can build the application for the unsecure 6LoWPAN-ND or Thread network.
 
-[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-example-mesh-minimal)](https://github.com/ARMmbed/mbed-os-example-mesh-minimal/blob/mbed-os-5.10.0/main.cpp)
+[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-example-mesh-minimal)](https://github.com/ARMmbed/mbed-os-example-mesh-minimal/blob/mbed-os-5.10.0/mesh_led_control_example.cpp)
 
 ### Related content
 

docs/introduction/introduction.md

@@ -76,14 +76,17 @@ This is the technical documentation for Mbed OS. We have three types of document
 Please see the following sections of our documentation for more information.
 
 - [APIs](../apis/index.html).
-- [Reference](../reference/index.html), which contains architectural information about our code.
+- [Quick start](../quick-start/index.html), a guide to creating your first application.
+- [Reference](../reference/index.html), architectural information about our code.
 - [Tools](../tools/index.html), reference material about the tools Mbed OS uses.
 - [Tutorials](../tutorials/index.html).
+- [Going to production](../evaluation-production/index.html), the process of connecting Mbed OS devices to Pelion Device Management for large-scale production.
+- [Contributing](../contributing/index.html), guidelines about contributing to our open-source project.
 - [Porting guides](../porting/index.html), for Partners and developers interested in porting targets to Mbed OS.
 
 ### Recently updated documentation
 
-* An updated [contributing guide](../contributing/index.html).
-* A revised [porting guide](../porting/index.html).
-* A [review of the full process of taking a project to production](./evaluation-production/index.html).
-* An updated [quick start](../quick-start/index.html) to demonstrate more Mbed OS capabilities.
+- An updated [contributing guide](../contributing/index.html).
+- A revised [porting guide](../porting/index.html).
+- A [review of the full process of taking a project to production](./evaluation-production/index.html).
+- An updated [quick start](../quick-start/index.html) to demonstrate more Mbed OS capabilities.

docs/porting/porting_full_process/demo_testing.md

@@ -92,7 +92,7 @@ Then, test connectivity and firmware update:
 
    - If your target uses WiFi, fill in the SSID and Password fields in `mbed_app.json`.
 
-   - Add NVStore descriptors (previously known as SOTP) for storage to `mbed-cloud-client-example/mbed_lib.json`. For example:
+   - Add [NVStore descriptors (previously known as SOTP)](https://cloud.mbed.com/docs/porting/porting-a-new-target-for-mbed-os.html) for storage to `mbed-cloud-client-example/mbed_lib.json`. For example:
 
       ```
       ...

docs/reference/technology/connectivity/NFC.md

@@ -18,7 +18,7 @@ NFC offers three modes:
 
 Mbed OS supports the card emulation mode, either through the use of a controller or NFC EEPROM.
 
-NFC support is available for the NXP PN512 transceiver. In terms of NFC EEPROMs, a driver for the ST M24SR EEPROM series is available - we also provide a [porting guide](https://os.mbed.com/contributing/connectivity/NFCEEPROMDriver.html) to add support for other NFC EEPROMs.
+NFC support is available for the NXP PN512 transceiver. In terms of NFC EEPROMs, a driver for the ST M24SR EEPROM series is available - we also provide a [porting guide](../porting/NFC-port.html) to add support for other NFC EEPROMs.
 
 We also provide APIs to decode and encode NDEF messages. A NDEF message is a standardized encoding that most NFC devices, such as Android and iOS smartphones, can understand.
 
@@ -40,7 +40,7 @@ NFC EEPROMs behave like NFC tags whose memory can either be addressed through a
 
 ### Getting started with NFC and example
 
-NFC examples are available on [GitHub](https://github.com/ARMmbed/mbed-os-example-nfc) and demonstrate how to create NFC tags that you can be read from and write to using a phone.
+NFC examples are available on [GitHub](https://github.com/ARMmbed/mbed-os/tree/master/docs/design-documents/nfc) and demonstrate how to create NFC tags that you can be read from and write to using a phone.
 
 <span class="images">![](https://s3-us-west-2.amazonaws.com/mbed-os-docs-images/explorenfc_nucleo.jpg)<span>An Explore-NFC board attached to a Nucleo board</span></span>
 

docs/reference/technology/mesh/thread_commissioning.md

@@ -18,7 +18,7 @@ A model network setup could look like this:
 
 #### Building the end node application
 
-By default, the Mbed Thread applications/examples use the static network link configuration defined in the [mesh-api configuration file](https://github.com/ARMmbed/mbed-os/blob/master/features/nanostack/FEATURE_NANOSTACK/mbed-mesh-api/mbed_lib.json). If you want to use the Thread commissioning, add the following lines to your `.json` file. You can use the [mesh-minimal](https://github.com/ARMmbed/mbed-os-example-mesh-minimal) application as an example.
+By default, the Mbed Thread applications/examples use the static network link configuration defined in the [mesh-api configuration file](https://github.com/ARMmbed/mbed-os/blob/master/features/nanostack/mbed-mesh-api/mbed_lib.json). If you want to use the Thread commissioning, add the following lines to your `.json` file. You can use the [mesh minimal](../apis/mesh-api.html#mesh-example) application as an example.
 
 - `"mbed-mesh-api.thread-use-static-link-config": false` under `"target_overrides":`
 - `"macros": ["MBEDTLS_USER_CONFIG_FILE=\"mbedtls_config.h\""]` in to the same level as `"config":` and `"target_overrides":`
@@ -35,14 +35,12 @@ Once the binary is generated, flash the binary to the end device, and run the ap
 
 You can use [a free online tool](http://www.qr-code-generator.com/) to generate a QR code.
 
-In the online tool, fill in the URL field. The following is an example: `v=1&eui=000b57fffe07a8be&cc=PV7TUCB0`. Fill in the correct values for your device, and ensure `v=1` is always present. The other required parameters are:
+In the online tool, fill in the URL field. The following is an example: `v=1&eui=000b57fffe07a8be&cc=ABCDEFGH`. Fill in the correct values for your device, and ensure `v=1` is always present. The other required parameters are:
 
 - `cc` is the PSKd, which is configured in the `.json` file (see the mesh-api configuration). *PSKd must be uppercase characters (0-9, A-Y excluding I,O,Q and Z)*
-- `eui` is equal to the RF MAC address by default.
+- `eui` is equal to the EUI64 address.
 
-To get the MAC address for your end device, connect the node to the Thread network with static configuration enabled. In other words, `"mbed-mesh-api.thread-use-static-link-config": true`, unless you have your own configuration for the MAC address.
-
-For example, in the **mesh-minimal** application, place this `printf("MAC address = %s\n", mesh.get_mac_address());` after `printf("connected. IP = %s\n", mesh.get_ip_address());`
+You can get the EUI64 address for your end device by using the `device_eui64_get` method in your application. Please see the [mesh minimal example](../apis/mesh-api.html#mesh-example) for details.
 
 There are four additional (optional) query parameters you can put into this field:
 

docs/reference/technology/mesh/thread_faq.md

@@ -32,12 +32,11 @@ Ad-hoc networks with devices from different manufacturers can be easily created
 
 An example application is [downloadable from the Android store](https://play.google.com/store/apps/details?id=org.threadgroup.commissioner).
 
-#### Are there any application examples? What are the Thread features supported/not supported by them?
+#### Are there any application examples?
 
-- Application examples supporting SED and REED types:
-  - [Mbed OS Client example](https://github.com/ARMmbed/mbed-os-example-client).
-  - [Mesh minimal example](https://github.com/ARMmbed/mbed-os-example-mesh-minimal).
+- [Mesh minimal example](../apis/mesh-api.html#mesh-example).
 - [Thread border router](https://github.com/ARMmbed/nanostack-border-router).
+- [Device Management client example](https://github.com/ARMmbed/mbed-cloud-client-example).
 
 #### How to debug and visualize the network?
 
@@ -50,7 +49,7 @@ Link quality and errors are easiest to debug using Wireshark.
 
 #### How to send/receive with UDP and TCP sockets. How to use multicast groups?
 
-The mesh minimal uses socket communication and multicasting. See more details in the [mesh minimal example](https://github.com/ARMmbed/mbed-os-example-mesh-minimal).
+The mesh minimal uses socket communication and multicasting. See more details in the [mesh minimal example](../apis/mesh-api.html#mesh-example).
 
 #### What if my ISP does not provide IPv6 service? Why do I need IPv6 internet service? Can I use a tunneling service?
 

docs/reference/technology/mesh/thread_intro.md

@@ -33,10 +33,10 @@ The key elements of Mbed OS are:
 
 Mbed Thread is implemented in the Nanostack library, which also supports the 6LoWPAN protocol. In Mbed OS, the Thread stack runs in its own RTOS thread using an internal event scheduler. Mbed OS provides the [Mesh C++ API](../apis/mesh-api.html) for building Thread applications.
 
-- To connect to the Thread network, use the [Thread interface API](https://github.com/ARMmbed/mbed-os/blob/master/features/nanostack/FEATURE_NANOSTACK/mbed-mesh-api/mbed-mesh-api/ThreadInterface.h).
+- To connect to the Thread network, use the [Mbed Mesh API](../apis/mesh-api.html) or [Thread interface API](https://github.com/ARMmbed/mbed-os/blob/master/features/nanostack/mbed-mesh-api/mbed-mesh-api/ThreadInterface.h).
 - For the socket communication over the Thread network, use the [Mbed sockets API](../apis/network-socket.html).
 
-Nanostack provides a set of C API headers with more functionalities. The [nanostack repository](https://github.com/ARMmbed/mbed-os/tree/master/features/nanostack/FEATURE_NANOSTACK/sal-stack-nanostack/nanostack) has the following header files():
+Nanostack provides a set of C API headers with more functionalities. The [nanostack repository](https://github.com/ARMmbed/mbed-os/tree/master/features/nanostack/sal-stack-nanostack/nanostack) has the following header files:
 
 - `thread_management_if.h` for initializing the stack and managing the network data.
 - `thread_commissioning_api.h` for implementing an on-mesh or a native Thread commissioner.