Dispatch images to dedicated page folders
|
@ -1,49 +0,0 @@
|
|||
|
||||
There are two types of batteries on Helios64 board:
|
||||
|
||||
- Li-Ion
|
||||
|
||||
- Coin-type Battery (CR 1225)
|
||||
|
||||
## Li-Ion Battery
|
||||
|
||||
The Li-Ion battery is actually installed in to Helios64 casing, but the battery is connected to the board in following connector:
|
||||
|
||||

|
||||
|
||||
The actual cell of the this Li-Ion battery is the panasonic NCR18650BD, we use 2 cell in 2S1P configuration.
|
||||
So the Li-Ion battery is rated at 2980mAh, 8.4Volt.
|
||||
The time estimation to fully charge this battery is 8.5 Hours.
|
||||
|
||||
### Pinout of the BATT Header
|
||||
|
||||

|
||||
|
||||
|Pin |Name
|
||||
|----|----------
|
||||
| 1 |Thermistor
|
||||
| 2 |Battery +
|
||||
| 3 |Battery +
|
||||
| 4 |GND
|
||||
| 5 |Battery -
|
||||
| 6 |Battery -
|
||||
|
||||
|
||||
## Coin Cell Battery
|
||||
|
||||
The Location of coin-type battery is shown by this figure:
|
||||

|
||||
|
||||
The battery type is CR1225, this device has diameter of 12.5mm and 2.5mm thickness.
|
||||
In above figure the positive (+) polarity is heading downward to the CPU heatsink side.
|
||||
This battery is used only for keep the RTC (Real Time Clock) running.
|
||||
|
||||
|
||||
## Notes related to battery
|
||||
|
||||
!!! note
|
||||
To be confirmed whether RTC is still running with Li-Ion battery only.
|
||||
|
||||
The Li-Ion battery is not designed to make Helios64 as portable device that can be used without AC power line, but designed as backup power to perform graceful shutdown or hibernate in case of loss of AC power line.
|
||||
Therefore it is normal if Helios64 turned on for a while when you press power button without AC power line.
|
||||
|
|
@ -1,13 +1,13 @@
|
|||
## Front Panel Pinout
|
||||
|
||||
Helios64 provides 24 front panel pinout on header P3.
|
||||
User can connect the front panel PCB into the P3 in the Helios64 board by using provided ribbon cable.
|
||||
User can connect the front panel PCB into the P3 in the Helios64 board by using provided ribbon cable.
|
||||
The ribbon cable are provided when you buy the Full Bundle of the Helios64 board.
|
||||
Below Graphics and Table describe the layout of the front panel header.
|
||||
|
||||

|
||||
|
||||
This header are actually located at:
|
||||
This header are actually located at:
|
||||

|
||||
|
||||
| PIN | Port | Remarks |
|
||||
|
@ -17,26 +17,26 @@ This header are actually located at:
|
|||
| 3 | GND | Ground |
|
||||
| 4 | GND | Ground |
|
||||
| 5 | RST Switch | |
|
||||
| 6 | PWR Switch | |
|
||||
| 7 | USR1 Switch | |
|
||||
| 8 | USR2 Switch | |
|
||||
| 9 | Network Activity LED - HS | |
|
||||
| 6 | PWR Switch | |
|
||||
| 7 | USR1 Switch | |
|
||||
| 8 | USR2 Switch | |
|
||||
| 9 | Network Activity LED - HS | |
|
||||
| 10 | USB Activity LED - HS | |
|
||||
| 11 | 3V3 | 3.3 Volt Supply |
|
||||
| 12 | SYS Green LED - HS | |
|
||||
| 13 | SYS Red LED - HS | |
|
||||
| 14 | SATA 0 Activity - HS | |
|
||||
| 15 | SATA 0 Error - HS | |
|
||||
| 16 | SATA 1 Activity - HS | |
|
||||
| 17 | SATA 1 Error - HS | |
|
||||
| 18 | SATA 2 Activity - HS | |
|
||||
| 19 | SATA 2 Error - HS | |
|
||||
| 20 | SATA 3 Activity - HS | |
|
||||
| 21 | SATA 3 Error - HS | |
|
||||
| 13 | SYS Red LED - HS | |
|
||||
| 14 | SATA 0 Activity - HS | |
|
||||
| 15 | SATA 0 Error - HS | |
|
||||
| 16 | SATA 1 Activity - HS | |
|
||||
| 17 | SATA 1 Error - HS | |
|
||||
| 18 | SATA 2 Activity - HS | |
|
||||
| 19 | SATA 2 Error - HS | |
|
||||
| 20 | SATA 3 Activity - HS | |
|
||||
| 21 | SATA 3 Error - HS | |
|
||||
| 22 | SATA 4 Activity - HS | |
|
||||
| 23 | SATA 4 Error - HS | |
|
||||
| 23 | SATA 4 Error - HS | |
|
||||
| 24 | GND | Ground |
|
||||
|
||||
|
||||
## Wiring Diagram
|
||||
|
||||
This Figures describe the PCB layout from the left hand side (RHS) and right hand side (LHS) view respectively.
|
||||
|
@ -57,7 +57,7 @@ The front panel USB 3.0 port can be directly connected to the Front USB 3.0 Port
|
|||
---TBU---
|
||||
|
||||
The connection between P3 from the Helios64 board to P1 on the front panel PCB board is illustrated in below figure:
|
||||

|
||||

|
||||
|
||||
|
||||
|
||||
|
|
|
@ -5,7 +5,7 @@ Those GPIOs are provided via an 16-bit IO Expander [PCA9655E](http://www.onsemi.
|
|||
|
||||
Unlike Helios4 whereas some pin of IO expander is used for system usage, on Helios64 all 16 GPIOs can be used for user application.
|
||||
|
||||

|
||||

|
||||
|
||||
## Pinout Table
|
||||
|
||||
|
@ -16,18 +16,18 @@ Unlike Helios4 whereas some pin of IO expander is used for system usage, on Heli
|
|||
| 3 | - | GND |
|
||||
| 4 | EXP_P0_0 | |
|
||||
| 5 | EXP_P0_1 | |
|
||||
| 6 | EXP_P0_2 | |
|
||||
| 7 | EXP_P0_3 | |
|
||||
| 8 | EXP_P0_4 | |
|
||||
| 9 | EXP_P0_5 | |
|
||||
| 6 | EXP_P0_2 | |
|
||||
| 7 | EXP_P0_3 | |
|
||||
| 8 | EXP_P0_4 | |
|
||||
| 9 | EXP_P0_5 | |
|
||||
| 10 | EXP_P0_6 | |
|
||||
| 11 | EXP_P0_7 | |
|
||||
| 12 | EXP_P1_0 | |
|
||||
| 13 | EXP_P1_1 | |
|
||||
| 14 | EXP_P1_2 | |
|
||||
| 15 | EXP_P1_3 | |
|
||||
| 16 | EXP_P1_4 | |
|
||||
| 17 | EXP_P1_5 | |
|
||||
| 18 | EXP_P1_6 | |
|
||||
| 19 | EXP_P1_7 | |
|
||||
| 20 | - | GND |
|
||||
| 13 | EXP_P1_1 | |
|
||||
| 14 | EXP_P1_2 | |
|
||||
| 15 | EXP_P1_3 | |
|
||||
| 16 | EXP_P1_4 | |
|
||||
| 17 | EXP_P1_5 | |
|
||||
| 18 | EXP_P1_6 | |
|
||||
| 19 | EXP_P1_7 | |
|
||||
| 20 | - | GND |
|
||||
|
|
|
@ -67,8 +67,8 @@ Above bus number and also including bus number 1,3,5 are reserved for system use
|
|||
Helios64 exposed Bus number 7 and 8 of the I2C in **P2** and **P1** pinout, respectively.
|
||||
This I2C bus can be connected to the external devices.
|
||||
|
||||
As described on below figure of [I2C](/helios64/img/hardware/i2c_pinout.png) (pin header number *3* and *4*), user can access the device at bus number 7.
|
||||
For the [UEXT](/helios64/img/hardware/UEXT_pinout.png) (pin header number *5* and *6*), user can access the device at bus number 8.
|
||||
As described on below figure of I2C (pin header number *3* and *4*), user can access the device at bus number 7.
|
||||
For the UEXT (pin header number *5* and *6*), user can access the device at bus number 8.
|
||||
|
||||
All the I2C bus in the board are using voltage level of 3.3V, please notice Helios64 is integrated with level translator and pull up resistor.
|
||||
|
||||
|
@ -76,7 +76,7 @@ All the I2C bus in the board are using voltage level of 3.3V, please notice Heli
|
|||
|
||||
Helios64 board exposes the SoC I2C Bus 1, on header **P1**. Below is the header pin-out.
|
||||
|
||||

|
||||

|
||||
|
||||
This I2C device working with 3 pin bus (SDA, SCK, and GND), and also in band addressing.
|
||||
We can use a 7 bit addressing to distinguish every device, but some address is reserved for the internal communication of the Helios64 board.
|
||||
|
@ -86,9 +86,9 @@ We can use a 7 bit addressing to distinguish every device, but some address is r
|
|||
The I2C header bus also can be found at UEXT connector (can be found at **P2** header at the the board [overview](/helios64/hardware/overview) page) on the header number 5 and 6.
|
||||
Below is the detail description of the UEXT connector:
|
||||
|
||||

|
||||

|
||||
|
||||
Pin No | Description
|
||||
Pin No | Description
|
||||
--------|-------------
|
||||
1|3.3V
|
||||
2|GND
|
||||
|
@ -107,7 +107,7 @@ Pin No | Description
|
|||
|
||||
Below table describe the external bus of I2C under Linux,
|
||||
|
||||
Bus number | Device Block | Description |
|
||||
Bus number | Device Block | Description |
|
||||
-----------|--------------|--------------|
|
||||
7 | /dev/i2c-7 | |
|
||||
8 | /dev/i2c-8 | |
|
||||
|
|
Before Width: | Height: | Size: 188 KiB After Width: | Height: | Size: 188 KiB |
Before Width: | Height: | Size: 14 KiB After Width: | Height: | Size: 14 KiB |
Before Width: | Height: | Size: 13 KiB |
Before Width: | Height: | Size: 6.1 KiB After Width: | Height: | Size: 6.1 KiB |
Before Width: | Height: | Size: 60 KiB After Width: | Height: | Size: 60 KiB |
Before Width: | Height: | Size: 13 KiB After Width: | Height: | Size: 13 KiB |
Before Width: | Height: | Size: 82 KiB After Width: | Height: | Size: 82 KiB |
Before Width: | Height: | Size: 25 KiB After Width: | Height: | Size: 25 KiB |
Before Width: | Height: | Size: 39 KiB After Width: | Height: | Size: 39 KiB |
11
docs/helios64/rtc.md
Normal file
|
@ -0,0 +1,11 @@
|
|||
## RTC Introduction
|
||||
|
||||
|
||||
## Coin Cell Battery
|
||||
|
||||
The Location of coin-type battery is shown by this figure:
|
||||

|
||||
|
||||
The battery type is CR1225, this device has diameter of 12.5mm and 2.5mm thickness.
|
||||
In above figure the positive (+) polarity is heading downward to the CPU heatsink side.
|
||||
This battery is used only for keep the RTC (Real Time Clock) running.
|
|
@ -15,11 +15,11 @@ You can find the P2 header from the connector/interface list at [hardware overvi
|
|||
|
||||
Please find this location of UEXT header:
|
||||
|
||||

|
||||

|
||||
|
||||
The pinout of the above P2 header is decribed by following figures:
|
||||
|
||||

|
||||

|
||||
|
||||
Below is the detailed description of UEXT header pinout:
|
||||
|
||||
|
|
29
docs/helios64/ups.md
Normal file
|
@ -0,0 +1,29 @@
|
|||
|
||||
## UPS Introduction
|
||||
|
||||
## Li-Ion Battery
|
||||
|
||||
The Li-Ion battery is actually installed in to Helios64 casing, but the battery is connected to the board in following connector:
|
||||
|
||||

|
||||
|
||||
The actual cell of the this Li-Ion battery is the panasonic NCR18650BD, we use 2 cell in 2S1P configuration.
|
||||
So the Li-Ion battery is rated at 2980mAh, 8.4Volt.
|
||||
The time estimation to fully charge this battery is 8.5 Hours.
|
||||
|
||||
### Pinout of the BATT Header
|
||||
|
||||

|
||||
|
||||
|Pin |Name
|
||||
|----|----------
|
||||
| 1 |Thermistor
|
||||
| 2 |Battery +
|
||||
| 3 |Battery +
|
||||
| 4 |GND
|
||||
| 5 |Battery -
|
||||
| 6 |Battery -
|
||||
|
||||
## Notes related to battery
|
||||
|
||||
The Li-Ion battery is not designed to make Helios64 as portable device that can be used without AC power line, but designed as backup power to perform graceful shutdown or hibernate in case of loss of AC power line. Therefore it is normal if Helios64 turned on for a while when you press power button without AC power line.
|
|
@ -13,8 +13,8 @@ Supported speed:
|
|||
- Low Speed (1.5 Mbps)
|
||||
|
||||
## Generic EHCI USB 2.0 Controller
|
||||
There are two controller of this type. This controller is Host only controller that is compatible with USB 2.0. The controller shared port with
|
||||
[Generic OHCI USB 1.1 Controller](#generic-ohci-usb-11-controller) therefore any USB 1.1 device connected to the port, will be automatically
|
||||
There are two controller of this type. This controller is Host only controller that is compatible with USB 2.0. The controller shared port with
|
||||
[Generic OHCI USB 1.1 Controller](#generic-ohci-usb-11-controller) therefore any USB 1.1 device connected to the port, will be automatically
|
||||
routed to [Generic OHCI USB 1.1 Controller](#generic-ohci-usb-11-controller).
|
||||
Supported speed:
|
||||
|
||||
|
@ -62,7 +62,7 @@ Each of external USB port is protected by Power Distribution switch with followi
|
|||
To simplify the cabling, Helios64 is designed to maximize USB Type-C usage.
|
||||
|
||||
Helios64 employ High Speed multiplexer on USB 2.0 signal, by default the USB 2.0 signal is routed to USB Serial console.
|
||||
The multiplexer can be override using [Jumper](/helios64/hardware/#jumpers)
|
||||
The multiplexer can be override using [jumper P13](/helios64/jumper/#hs-select-p13).
|
||||
|
||||

|
||||
|
||||
|
@ -75,7 +75,7 @@ On Windows PC using [USB Device Tree Viewer](https://www.uwe-sieber.de/usbtreevi
|
|||
|
||||
In this case, Helios64 is connected to a USB 3.1 Gen 1 Hub port 1.
|
||||
|
||||
USB Serial Converter (FTDI FT232 USB Serial) connected under port 1 of the USB 2.0 side of the Hub and
|
||||
USB Serial Converter (FTDI FT232 USB Serial) connected under port 1 of the USB 2.0 side of the Hub and
|
||||
RK3399 USB 3.0 (configured as USB Mass Storage Device) connected under port 1 of the USB 3.0 side of the Hub.
|
||||
|
||||
On Linux PC using [USBview](http://www.kroah.com/linux-usb/) to visualize the USB tree,
|
||||
|
@ -84,13 +84,13 @@ On Linux PC using [USBview](http://www.kroah.com/linux-usb/) to visualize the US
|
|||
|
||||
In this case, Helios64 is connected to a USB 3.1 Gen 1 Hub port 1.
|
||||
|
||||
FTDI FT232 USB Serial connected under port 1 of the USB 2.0 side of the Hub and
|
||||
FTDI FT232 USB Serial connected under port 1 of the USB 2.0 side of the Hub and
|
||||
RK3399 USB 3.0 (configured as USB Mass Storage Device) connected under port 1 of the USB 3.0 side of the Hub.
|
||||
|
||||
|
||||
!!! info
|
||||
Every USB hub connected to USB 3.0 port or higher will create a sibling device, USB Hub 2.0, from host point of view.
|
||||
|
||||
|
||||
USB 2.0 device connected port 1 of the USB 3.0 Hub, it will appear on USB 2.0 Hub port 1.
|
||||
If USB 3.0 Device connected to same physical port it will appear on USB 3.0 Hub port 1.
|
||||
|
||||
|
@ -114,7 +114,7 @@ Using USB Type-C to DisplayPort cable or USB Type-C to HDMI dongle, Helios64 can
|
|||
|
||||
!!! note
|
||||
- DisplayPort Alternate Mode is NOT supported on U-Boot.
|
||||
|
||||
|
||||
- USB Type-C to HDMI cable might not work if it employ HDMI Alternate Mode
|
||||
|
||||
|
||||
|
@ -201,8 +201,8 @@ Device Descriptor:
|
|||
bDescriptorType 1
|
||||
bcdUSB 3.00
|
||||
bDeviceClass 0 (Defined at Interface level)
|
||||
bDeviceSubClass 0
|
||||
bDeviceProtocol 0
|
||||
bDeviceSubClass 0
|
||||
bDeviceProtocol 0
|
||||
bMaxPacketSize0 9
|
||||
idVendor 0x0525 Netchip Technology, Inc.
|
||||
idProduct 0xa4a5 Pocketbook Pro 903
|
||||
|
@ -223,7 +223,7 @@ OTG Descriptor:
|
|||
wTotalLength 47
|
||||
bNumInterfaces 1
|
||||
bConfigurationValue 1
|
||||
iConfiguration 0
|
||||
iConfiguration 0
|
||||
bmAttributes 0xe0
|
||||
Self Powered
|
||||
Remote Wakeup
|
||||
|
@ -297,16 +297,16 @@ lsblk output:
|
|||
```
|
||||
$ lsblk
|
||||
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
|
||||
sdc 8:32 0 111,8G 0 disk
|
||||
└─sdc1 8:33 0 111,8G 0 part
|
||||
sdd 8:48 0 111,8G 0 disk
|
||||
└─sdd1 8:49 0 111,8G 0 part
|
||||
sde 8:64 0 111,8G 0 disk
|
||||
└─sde1 8:65 0 111,8G 0 part
|
||||
sdf 8:80 0 111,8G 0 disk
|
||||
└─sdf1 8:81 0 111,8G 0 part
|
||||
sdg 8:96 0 111,8G 0 disk
|
||||
└─sdg1 8:97 0 111,8G 0 part
|
||||
sdc 8:32 0 111,8G 0 disk
|
||||
└─sdc1 8:33 0 111,8G 0 part
|
||||
sdd 8:48 0 111,8G 0 disk
|
||||
└─sdd1 8:49 0 111,8G 0 part
|
||||
sde 8:64 0 111,8G 0 disk
|
||||
└─sde1 8:65 0 111,8G 0 part
|
||||
sdf 8:80 0 111,8G 0 disk
|
||||
└─sdf1 8:81 0 111,8G 0 part
|
||||
sdg 8:96 0 111,8G 0 disk
|
||||
└─sdg1 8:97 0 111,8G 0 part
|
||||
|
||||
$ lsblk -S
|
||||
NAME HCTL TYPE VENDOR MODEL REV TRAN
|
||||
|
@ -360,8 +360,8 @@ Device Descriptor:
|
|||
bDescriptorType 1
|
||||
bcdUSB 3.00
|
||||
bDeviceClass 0 (Defined at Interface level)
|
||||
bDeviceSubClass 0
|
||||
bDeviceProtocol 0
|
||||
bDeviceSubClass 0
|
||||
bDeviceProtocol 0
|
||||
bMaxPacketSize0 9
|
||||
idVendor 0x0525 Netchip Technology, Inc.
|
||||
idProduct 0xa4a5 Pocketbook Pro 903
|
||||
|
@ -382,7 +382,7 @@ OTG Descriptor:
|
|||
wTotalLength 47
|
||||
bNumInterfaces 1
|
||||
bConfigurationValue 1
|
||||
iConfiguration 0
|
||||
iConfiguration 0
|
||||
bmAttributes 0xe0
|
||||
Self Powered
|
||||
Remote Wakeup
|
||||
|
@ -455,8 +455,8 @@ lsblk output
|
|||
```
|
||||
$ lsblk
|
||||
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
|
||||
sdc 8:32 0 335,2G 0 disk
|
||||
└─sdc1 8:33 0 335,2G 0 part
|
||||
sdc 8:32 0 335,2G 0 disk
|
||||
└─sdc1 8:33 0 335,2G 0 part
|
||||
|
||||
$ lsblk -S
|
||||
NAME HCTL TYPE VENDOR MODEL REV TRAN
|
||||
|
|
|
@ -81,10 +81,11 @@ nav:
|
|||
- LED : 'helios64/led.md'
|
||||
- M.2 : 'helios64/m2.md'
|
||||
- PWM Fan : 'helios64/fan.md'
|
||||
- RTC : 'helios64/rtc.md'
|
||||
- SATA : 'helios64/sata.md'
|
||||
- SPI : 'helios64/spi.md'
|
||||
- UEXT : 'helios64/uext.md'
|
||||
- UPS Battery : 'helios64/battery.md'
|
||||
- UPS Battery : 'helios64/ups.md'
|
||||
- USB : 'helios64/usb.md'
|
||||
- Helios4:
|
||||
- Introduction: 'helios4/intro.md'
|
||||
|
|