dbroqua/kobol-wiki
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

update hardware and led pages

Browse source
This commit is contained in:
nurix87 2020-02-19 21:21:04 +07:00
parent 5990a5796b
commit 27c7668e4c
5 changed files with 28 additions and 167 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

41
docs/helios64/hardware.md
View file

@ -21,6 +21,8 @@ P9|eFuse Dis. Jumper|Not Populated|**TBD** eFuse Power Supply
P10|eMMC Dis. Jumper|2x1 Pin Male Header|Disable eMMC boot
P11|SPI Flash Dis. Jumper|2x1 Pin Male Header|Disable SPI Flash
P13|HS Select Jumper|2x1 Pin Male Header|USB-C HS Select (Close = Type C HS, Open = Console)
P14|ATX Priority Jumper|2x1 Pin Male Header|ATX Supply Priority
P15|ACDC Priority Jumper|2x1 Pin Male Header|ACDC(AC Adapter) Supply Priority
J1|USB3 Host|USB 3.0 Host| USB 3.0 Port Header
J3|SATA|SATA 3.0|Port 0 (SATA1)
J4|SATA|SATA 3.0|Port 1 (SATA2)
@ -113,28 +115,28 @@ Helios64 board exposes the SoC I2C Bus 1, on header **P1**. Below is the header
**Board only**
* Idle : 3.6 Watts
* Active : 5.6 Watts
* Idle : X.X Watts
* Active : X.X Watts
**Full Kit (with 4x HDDs)**
**Full Kit (with 5x HDDs)**
| State | AC calculated<br>power consumption | DC measured<br>power consumption | Remarks |
|---------------------|----------------------|----------------------|---------------------|
| Idle | 19.3 W | 16.8 W | |
| HDD Read Access | 27.4 W | 22.8 W | |
| HDD Write Access | 30.3 W | 25.2 W | |
| Standby | 8.0 W | 6.7 W | HDD in Standby mode |
| Suspend-to-Ram | 7.2 W | 6.0 W | HDD in Standby mode |
| Idle | X.X W | X.X W | |
| HDD Read Access | X.X W | X.X W | |
| HDD Write Access | X.X W | X.X W | |
| Standby | X.X W | X.X W | HDD in Standby mode |
| Suspend-to-Ram | X.X W | X.X W | HDD in Standby mode |
!!! note
Measures were done using a Current Clamp Meter on the Helios4 12V DC input. AC Power consumption is calculated based on a AC/DC conversion efficiency of 85%.
Measures were done using a Current Clamp Meter on the Helios64 12V DC input. AC Power consumption is calculated based on a AC/DC conversion efficiency of 85%.
* Meter tool : Extech 380942 - 30A True RMS AC/DC Mini Clamp
* AC/DC Adapter : yczx1268 (efficiency : 85%)
* AC/DC Adapter : (efficiency : YY%)
* AC Input Voltage: 220V
* HDD: 4x WD Red 2TB (WD20EFRX) configured as RAID10
* HDD: 5x YYY XX TB (HDDCODEXX) configured as RAIDXX
* Network : Connected at 1000Mb/s
* OS: ARMBIAN 5.73 stable Debian GNU/Linux 9 (stretch) 4.14.98-mvebu
* OS: ARMBIAN Z.Z stable Debian GNU/Linux 10 (buster) 5.4.xx-yyy
## HDD Recommendation List
@ -155,24 +157,11 @@ We recommend HDD which are designed for NAS (Network Attached Storage). Those NA
- ST1000VN002
- ST2000VN004
- ST3000VN007
- ST4000VN008
- ST6000VN0041
- ST8000VN0022
- ST10000VN0004
**HGST** : Deskstar NAS (4, 6 and 8TB)
- 0S04005
- 0S04007
- 0S04012
!!! note
We recommend to order from different shop to avoid having all the drives from the same factory batch. For instance, you should order 2x HDDs from one shop, then the 2 others from another shop.
## HDD / SSD Compability List
Please refer to [Synology DS416j Compatibility List](https://www.synology.com/en-global/compatibility?search_by=products&model=DS416j&category=hdds&p=1) that covers a large number of tested drives. The DS416j used the same SoC family than Helios4.
**To be updated.**
## References

BIN
docs/helios64/img/hardware/helios64_board_labeled.png
View file

Binary file not shown.
Side by side Swipe Overlay

Before

Width:  |  Height:  |  Size: 243 KiB

After

Width:  |  Height:  |  Size: 244 KiB

BIN
docs/helios64/img/install/io-port-connected.jpg Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 423 KiB

153
docs/helios64/led.md
View file

@ -2,147 +2,18 @@
## On-Board LEDs
The onboard LEDs location are shown in above figure
### Pinout Table
## LED indicators
![J18 Pinout](/helios4/img/led/gpio_pinout_j18.png)
LED Name|Color|Description
---|---|---
LED1|green|SYS power
LED2|green|Peripheral power
LED3|green|HDD power
LED4|blue|System ON
LED5|bule|HDD activity
LED6|green|System Status
LED7|red|System Error
LED8|orange|Battery Charge
| Pin | LED number | Remarks |
|-----|------------|---------|
| 1 | - | 3.3V supply |
| 2 | - | Not connected |
| 3 | LED1 | Active-low |
| 4 | LED2 | Active-low |
| 5 | LED3 | Active-low |
| 6 | LED4 | Active-low |
| 7 | LED5 | Active-low |
| 8 | LED6 | Active-low |
| 9 | LED7 | Active-low |
| 10 | - | GND |
!!! info
LED1 - LED7 is preconfigured for certain indicator under Linux, see [LED under Linux](#led-under-linux) section.
### Wiring Diagram
Since the signals to control the LEDs are active low, connect the pin to LED's cathode.
Below a wiring diagram example.
![Wiring Example](/helios4/img/led/led_expansion_wiring_diagram.png)
## LED under Linux
| LED | Name | Default Trigger | Remarks |
|------|----------------------|-----------------|---------|
| LED1 | helios4:green:status | heartbeat | Blinking periodically |
| LED2 | helios4:red:fault | none | See [Configuring Fault LED](#configuring-fault-led) |
| LED3 | helios4:green:ata1 | ata1 | Blinking on SATA1 activity |
| LED4 | helios4:green:ata2 | ata2 | Blinking on SATA2 activity |
| LED5 | helios4:green:ata3 | ata3 | Blinking on SATA3 activity |
| LED6 | helios4:green:ata4 | ata4 | Blinking on SATA4 activity |
| LED7 | helios4:green:usb | usb-host | Blinking on USB activity, any port |
!!! note
**ata** trigger requires additional patch to mainline kernel. The patch can be found [here](/helios4/files/led/libata_leds_trigger_mvebu.patch). **Armbian** builds are already patched, so no action is required.
The LEDs can be accessed under LEDs class in *sysfs*.
```
root@helios4:~/# ls -l /sys/class/leds/
lrwxrwxrwx 1 root root 0 Dec 4 06:57 helios4:green:ata1 -> ../../devices/platform/io-leds/leds/helios4:green:ata1
lrwxrwxrwx 1 root root 0 Dec 4 06:57 helios4:green:ata2 -> ../../devices/platform/io-leds/leds/helios4:green:ata2
lrwxrwxrwx 1 root root 0 Dec 4 06:57 helios4:green:ata3 -> ../../devices/platform/io-leds/leds/helios4:green:ata3
lrwxrwxrwx 1 root root 0 Dec 4 06:57 helios4:green:ata4 -> ../../devices/platform/io-leds/leds/helios4:green:ata4
lrwxrwxrwx 1 root root 0 Dec 4 06:57 helios4:green:status -> ../../devices/platform/system-leds/leds/helios4:green:status
lrwxrwxrwx 1 root root 0 Dec 4 06:57 helios4:green:usb -> ../../devices/platform/io-leds/leds/helios4:green:usb
lrwxrwxrwx 1 root root 0 Dec 4 06:57 helios4:red:fault -> ../../devices/platform/system-leds/leds/helios4:red:fault
```
### LEDs Trigger
- none
No automatic trigger. Manually control the LED by manipulating "brightness".
More info see [Configuring LED trigger](#configuring-led-trigger).
- heartbeat
LED "double" flashes at a load average based rate. The interval might change during heavy load.
If the LED no longer blinks, it means the system is locked-up or hung and has to be reset.
- ata*N*
LED blinks on any read/write activity at specific SATA port.
- usb-host
LED blinks on USB activity at any port.
- panic
This trigger allows LEDs to be configured to blink on a kernel panic.
- timer
This allows LEDs to be controlled by a programmable timer via *sysfs*. delay_on to set how long
the LED turned on and delay_off to set how long the LED turned off.
### Configuring LED trigger
To configure, simply set the trigger type. For example to set Status LED triggered by timer
```
echo timer | sudo tee -a /sys/class/leds/helios4\:green\:status/trigger
```
Some of the triggers may expose additional parameters that can be configured further.
On **none** trigger, to turn ON the LED set the brightness bigger than 0.
```
echo 1 | sudo tee -a /sys/class/leds/helios4\:green\:status/brightness
```
and to turn OFF the LED set the brightness to 0.
```
echo 0 | sudo tee -a /sys/class/leds/helios4\:green\:status/brightness
```
On **timer** trigger, it will exposed *delay_on* and *delay_off* with default value of 0.5 seconds for both.
To change the delay, set the respective parameter (value in milliseconds)
```
echo 1000 | sudo tee -a /sys/class/leds/helios4\:green\:status/delay_on
echo 200 | sudo tee -a /sys/class/leds/helios4\:green\:status/delay_off
```
!!! note
The changes is not retained across reboot. Use startup script or udev rules to make it permanent.
### Configuring Fault LED
While other LEDs are preconfigured, the fault LED remains unconfigured (trigger:**none**).
#### 1. As Kernel Panic Indicator
To configure the LED as Kernel panic indicator, set the trigger to **panic**. However this functionality might be redundant with Status LED, since if a kernel panic occurs and/or system hangs, the Status LED will no longer blink.
To trigger kernel panic to test the LED, run
```
echo c > /proc/sysrq-trigger
```
!!! warning
Triggering kernel panic can lead to data loss. Use with caution!
#### 2. As RAID Fault Indicator
To configure the LED as RAID fault indicator, please refer to [MDADM: Configure Fault LED](/helios4/mdadm/#configure-fault-led)
!!! note
On Armbian builds, this is the default setting for fault LED.

1
mkdocs.yml
View file

@ -77,6 +77,7 @@ nav:
- Hardware:
- Overview : 'helios64/hardware.md'
- LED : 'helios64/led.md'
- I2C : 'helios64/i2c.md'
- Helios4:
- Introduction: 'helios4/intro.md'
- Kit Assembly: 'helios4/kit.md'