doc: add iotdk getting_started doc,minor fix for other doc

Signed-off-by: Yuguo Zou <[email protected]>

Author: YuguoWH

doc/documents/getting_started/getting_started.rst

@@ -84,6 +84,7 @@ Use the following procedures to prepare your ARC board to run/debug the embARC a
 
    getting_started_with_em_starter_kit.rst
    getting_started_with_hs_development_kit.rst
+   getting_started_with_iot_development_kit.rst
 
 See the following procedures to check peripherals and board settings. The peripherals are not required for all the embARC OSP examples.
 

doc/documents/getting_started/getting_started_with_iot_development_kit.rst

@@ -0,0 +1,57 @@
+.. _getting_started_with_iot_development_kit:
+
+Getting Started with IoT Development Kit
+========================================
+
+Supported Hardware
+##################
+
+The DesignWare® ARC® IoT Development Kit (IoTDK) is a versatile platform that includes the necessary hardware and software to accelerate software development and debugging of sensor fusion, voice recognition and face detection designs. RTOS & bare metal applications can be developed using the embARC Open Software Platform (OSP). I/O functionality can be extended using Digilent® Peripheral Modules (Pmods™), as well as Arduino Shields and mikrobus modules.
+
+For further information, see :ref:`board_iotdk`
+
+Setting Up IoTDK
+################
+
+#. Switch DIP switches to the OFF position (closest to the edge of the board).
+
+#. Connect your PC and IoTDK board with USB cable to micro USB port next to 5V DC power connector on board.
+
+#. (Optional) Connect 5V DC power connector with 5V AC/DC adapter.
+
+#. You can use any terminal emulation program to view UART output from the IoTDK. The USB connection provides both the debug channel and RS232 transport. Use PuTTY application on Windows as an example.
+
+   * Determine which COM port the IoTDK is using.
+
+      * Open the **Windows Control Panel** and select **Device Manager** in a Windows environment.
+      * Expand **Ports (COM and LPT)** in the list. Select **USB Serial Port (COM x)** and note the COM port number for the ARC board.
+
+   * Configure serial terminal connection.
+
+      * Launch PuTTY. Select **Serial** under **Connection type** and enter the appropriate COM port string under **Serial line**.
+      * Choose 115200 baud, 8 bits, 1 stop bit, no parity (115200-8-N-1) in settings.
+      * You can optionally save your settings so they can be easily retrieved every time PuTTY is launched.
+      * Click Open to open the console.
+
+#. Test serial output with IoTDK.
+
+      * Press the reset button on the IoTDK board to reset the board and run the uboot.
+      * Confirm that you can see the message printed to the console as shown below.
+
+      .. code-block:: console
+
+         U-Boot 2018.03-rc3-00028-g161e5eeaa4a4-dirty (Mar 05 2018 - 12:56:14 +0300)
+
+         DRAM:  128 KiB
+         MMC:   Synopsys Mobile storage: 0
+         Loading Environment from FAT... Card did not respond to voltage select!
+         ** Bad device mmc 0 **
+         Failed (-5)
+         In:    serial0@80014000
+         Out:   serial0@80014000
+         Err:   serial0@80014000
+         =>
+
+
+#. (Optional) Connect peripheral modules to the IoTDK as per :ref:`peripheral_preparation`.
+

doc/documents/getting_started/peripheral_preparation.rst

@@ -32,7 +32,7 @@ Now your code should be like this:
 
 .. note:: Notice that **UR** means Upper Layer of Pmod interface and **LR** means Lower Layer of Pmod
 
-3. If you are using HSDK, go to mux.c and find ``io_mux_init()`` function, you will see it calls ``creg_hsdc_set_gpio_mux()`` with paramater array ``gpio_mux_config`` as MUX options.
+3. If you are using HSDK, go to mux.c and find ``io_mux_init()`` function, you will find it calls ``creg_hsdc_set_gpio_mux()`` with paramater array ``gpio_mux_config`` as MUX options.
 By default all pins are set to GPIO, other MUX options are defined in ``PINMUX_TYPE`` in ``embarc_osp/device/inc/dev_pinmux.h``
 
 .. note:: To learn what interface your board has, please go to :ref:`board_bsp`
@@ -64,4 +64,4 @@ Driver code at ``embarc_osp/device/peripheral/adc/ad7991``.
 
 `ESP01\/ESP01S <http://wiki.ai-thinker.com/esp8266/docs>`_ : Primary IC type is ESP8266, use **UART** interface for data changing and controlling.
 Driver code at ``embarc_osp/device/peripheral/wifi/slip_esp``.
-	The ESP01/ESP01S module is not originally a PMOD module, however it is PMOD campatible, which means you could wire it to PMOD interface on board. You need to connect GCC(embARC) to GCC(ESP) , 3.3V(embARC) to VCC, RXD(embARC) to TXD(ESP), and TXD(embARC) to RXD(ESP), respectively. Please take reference from datasheet of `ESP01\/ESP01S <http://wiki.ai-thinker.com/esp8266/docs>`_ and UART (type 4A) part of `Digilent Pmod Spec <https://www.digilentinc.com/Pmods/Digilent-Pmod_%20Interface_Specification.pdf>`_ for pin layout.
+	The ESP01/ESP01S module is not originally a PMOD module, however it is PMOD campatible, meaning that you could wire it to PMOD interface on board. You need to connect GCC(embARC) to GCC(ESP) , 3.3V(embARC) to VCC, RXD(embARC) to TXD(ESP), and TXD(embARC) to RXD(ESP), respectively. Please take reference from datasheet of `ESP01\/ESP01S <http://wiki.ai-thinker.com/esp8266/docs>`_ and UART (type 4A) part of `Digilent Pmod Spec <https://www.digilentinc.com/Pmods/Digilent-Pmod_%20Interface_Specification.pdf>`_ for pin layout.

example/freertos/iot/coap/coap_server/README.rst

@@ -30,7 +30,7 @@ Detailed Description
 Buidling and Running
 ********************
 
- This example outputs to the console. It is supported by all platform. You might need to change mux configurations or connect wires in order to use peripheral modules, see :ref:`peripheral_preparation`.
+ This example outputs to the console. It is supported by all platform. You might need to change MUX configurations or connect wires in order to use peripheral modules, see :ref:`peripheral_preparation`.
  The commands to run this example are as follows:
 
 .. code-block:: console