updating hardware, uext, and m2 pages

docs/helios64/front-panel.md

@@ -7,6 +7,9 @@ Below Graphics and Table describe the layout of the front panel header.
 
 ![P3 Pinout](/helios64/img/front-panel/fp-header.png)
 
+This header are actually located at: 
+![P3 Location](/helios64/img/front-panel/fp-header-zoom.jpg)
+
 ### Front Panel Pinout Table
 
 | PIN | Port | Remarks |

docs/helios64/hardware.md

@@ -1,10 +1,10 @@
 ## Block Diagram
 
 ### Helios64 Board
-![!Block Diagram](/helios64/img/hardware/helios64-block-diagram.png)
+![!Block Diagram](/helios64/img/hardware/helios64_block_diagram.png)
 
 ### RK3399 System-On-Chip
-![!Block Diagram](/helios64/img/hardware/RK3399_block_diagram.png)
+![!Block Diagram](/helios64/img/hardware/rk3399_block_diagram.png)
 
 This block diagram is cited from the RK3399 website documentation. [1](http://opensource.rock-chips.com/wiki_File:RK3399_Block_Diagram.png)
 

docs/helios64/i2c.md

@@ -3,11 +3,23 @@
 Helios64 support I2C bus for the low-speed communication between devices like microcontrollers, EEPROMs, A/D and D/A converters, I/O interface and other similar peripherals in embedded systems.
 In order to communicate with each I2C slave device you will need an address and communication scenario.
 
-Helios64 board exposes the SoC I2C Bus 1, on header **P1**. Below is the header pin-out.
+Please take caution of the reserved address when you use the I2C interface, below is the reseved address list:
 
-### I2C bus on Helios64 / RK3399K
+Slave Address |	R/W Bit |	Description
+--------------|---------|-------------------
+000 0000 |	0  |	General call address
+000 0000 |	1  |	START byte(1)
+000 0001 |	X  |	CBUS address(2)
+000 0010 |	X  |	Reserved for different bus format (3)
+000 0011 |	X  |	Reserved for future purposes
+000 01XX |	X  |	Hs-mode master code
+111 10XX |	X  |	10-bit slave addressing
+111 11XX |	X  |	Reserved for future purposes
 
-The I2C controller on RK3399K support following features:
+
+### I2C bus on Helios64 / RK3399
+
+The I2C controller on RK3399 support following features:
 
 - 9 on-chip I2C controllers
 - Multi-master I2C operation
@@ -62,6 +74,8 @@ All the I2C bus in the board are using voltage level of 3.3V, please notice Heli
 
 #### I2C at P1 Header
 
+Helios64 board exposes the SoC I2C Bus 1, on header **P1**. Below is the header pin-out.
+
 ![I2C Pinout](/helios64/img/hardware/i2c_pinout.png)
 
 This I2C device working with 3 pin bus (SDA, SCK, and GND), and also in band addressing.
@@ -87,20 +101,6 @@ Pin No  | Description
 9|SCK (SPI)
 10|SSEL (SPI)
 
-Please take caution of the reserved address when you use the I2C interface, below is the reseved address list:
-
-Slave Address |	R/W Bit |	Description
---------------|---------|-------------------
-000 0000 |	0  |	General call address
-000 0000 |	1  |	START byte(1)
-000 0001 |	X  |	CBUS address(2)
-000 0010 |	X  |	Reserved for different bus format (3)
-000 0011 |	X  |	Reserved for future purposes
-000 01XX |	X  |	Hs-mode master code
-111 10XX |	X  |	10-bit slave addressing
-111 11XX |	X  |	Reserved for future purposes
-
-
 ### Usage under Linux
 
 #### External bus block device under linux
@@ -109,8 +109,8 @@ Below table describe the external bus of I2C under Linux,
 
 Bus number | Device Block | Description  | 
 -----------|--------------|--------------|
- 7         | /dev/i2c-0   |              |
+ 7         | /dev/i2c-7   |              |
- 8         | /dev/i2c-1   |              |
+ 8         | /dev/i2c-8   |              |
 
 
 #### Checking the I2C Communication under linux

docs/helios64/m2.md

@@ -1,42 +1,29 @@
 ## M2 Connector (P2)
 M.2, formerly known as the Next Generation Form Factor (NGFF), is a specification for internally mounted computer expansion cards and associated connectors. M.2 replaces the mSATA standard, which uses the PCI Express Mini Card physical card layout and connectors.
 
+Supported bus in the Helios64 M.2 interface is SATA and USB 2.0.
+
+!!! Warning!
+       PCIe SSD is not supported.
+
 ---TBU---
 
-### Pinout Table
+## Location
-Helios64 provides UEXT on header P2 which following the UEXT standard, containing UEXT, SPI, and I2C connector.
-You can find the P2 header from the connector/interface list at [hardware overview](/helios64/hardware) page.
 
-![P5 Pinout](/helios64/img/hardware/UEXT_pinout.png)
+Helios64 support M.2 device on header P2 which is located next to SATA 1 connector.
+You can refer to the connector/interface list at [hardware overview](/helios64/hardware) page.
+The location of the M.2 socket is shown in below figure:
 
-Below is the detailed description of UEXT header pinout:
+![M2 Pinout](/helios64/img/m2/m2-zoom-w-symbol.jpg)
 
-| PIN | Port | Remarks |
+## Size
-|-----|------|-------------|
-|1 |3.3V|
-|2 |GND|
-|3 |TXD (UART)|
-|4 |RXD (UART)|
-|5 |SCL (I2C)|
-|6 |SDA (I2C)|
-|7 |MISO (SPI)|
-|8 |MOSI (SPI)|
-|9 |SCK (SPI)|
-|10 |SSEL (SPI)|
 
-!!! Warning
+The maximum size of supported M.2 device is the 228 size. 
-       Please note the UEXT connector at Helios64 board doesn't provide the plastic covering, so be carefull with the header polarity!
-Make sure your device is correctly oriented before connecting!
 
-### SPI and I2C
+## Notes related to M.2 Card
+The M.2 devices installed in Helios64 is configured as sharing devices with SATA Port 1.
+Therefore if you install M.2 module, you will not be able to access the SATA Port 1.
 
----linked to SPI and I2C pages, TBU---
+The USB bus is connected to the EHCI Host 0.
 
-### Exception
+The M.2 socket in the Helios64 board does NOT support the USB modem, because the USB modem require the SIM Card connection and another signal. (The GSM Pin is NOT connected in the Helios64 board) 
-
-We have connected the UART bus from the RK3399K to the serial console in the USB-C, so there is no dedicated line of UART in the UEXT connector.
-The UART bus in this UEXT header is the parallel ones with the serial console.
-Therefore if you connect some module which might ***require dedicated serial UART line*** to the RK3399K, this module ***will not be detected***.
-
-!!! Notes
-       Please note also, that GSM modules in UEXT format also will not work due to similar reason.

docs/helios64/uext.md

@@ -50,4 +50,4 @@ The UART bus in this UEXT header is the parallel ones with the serial console.
 Therefore if you connect some module which might ***require dedicated serial UART line*** to the RK3399K, this module ***will not be detected***.
 
 !!! Notes
-       Please note also, that GSM modules in UEXT format also will not work due to similar reason.
+       Please note also, that GPS modules in UEXT format also will not work due to similar reason.