repairing typo and update some figures
This commit is contained in:
nurix87
parent
4b24703948
commit
0299e8d4ea
11 changed files with 40 additions and 39 deletions
|
|
@ -1,29 +0,0 @@
|
|||
Helios64 supports at least **3 (TBD)** boot modes that can be chosen by using the jumper configuration.
|
||||
|
||||
The default Boot device order for Helios64 is the SPI Flash Memory, eMMC, then micro-SD Card.
|
||||
The SoC will access this order sequentially to find the bootloader in all possible storage medium.
|
||||
To change the boot order if the bootloader are present in all possible volatile storage, we can use the combination of P10 and P11 jumpers.
|
||||
(Please see above figure for the connector/interface list.)
|
||||
Following jumper are available in the Helios64 board to configure the boot modes:
|
||||
|
||||
- P11 jumper can be used disable SPI Flash, when this jumper is shorted/close it means disable boot from the SPI Flash, and the board will search the next boot device (which is eMMC).
|
||||
- P10 jumper is available to disable eMMC boot, when this jumper is closed Helios64 wil skip looking for bootloader from the eMMC and will continue with the micro-SD card,
|
||||
|
||||
So you can select to search for bootloader starting from the SPI Flash Storage, eMMC, untill micro-SD card.
|
||||
Following table may simplified boot ordering by jumper config by assuming the bootloaders are present in every storage device:
|
||||
|
||||
|
||||
|
||||
P11 State|P10 State|Boot Order|Notes
|
||||
-----|---------------|--------------|-------
|
||||
0|0|SPI Flash|-
|
||||
1|0|eMMC|-
|
||||
1|1|micro-SD Card|-
|
||||
|
||||
!!! note
|
||||
Please note, in case of bootloader is not present in the storage devices. The SoC will search to the next possible boot device.
|
||||
|
||||
|
||||
All the ready-to-use images we provide are for the **SD Card** boot mode.
|
||||
|
||||
Please refer to [U-boot](/helios4/uboot) section to know how to use the other modes.
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 13 KiB After Width: | Height: | Size: 13 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 106 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 13 KiB After Width: | Height: | Size: 11 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 174 KiB After Width: | Height: | Size: 154 KiB |
|
|
@ -1,4 +1,4 @@
|
|||
## **Step 1** - Download Helios4 OS image
|
||||
## **Step 1** - Download Helios64 OS image
|
||||
|
||||
Before we start, you will need to download the Armbian Image for Helios64 build.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,9 +1,36 @@
|
|||
## Boot Mode (P10 & P11)
|
||||
|
||||
|
||||
|
||||
Refer to [Boot Mode](/helios64/boot_mode)
|
||||
Helios64 supports at least **3 (TBD)** boot modes that can be chosen by using the jumper configuration.
|
||||
|
||||
The default Boot device order for Helios64 is the SPI Flash Memory, eMMC, then micro-SD Card.
|
||||
The SoC will access this order sequentially to find the bootloader in all possible storage medium.
|
||||
To change the boot order if the bootloader are present in all possible volatile storage, we can use the combination of P10 and P11 jumpers.
|
||||
(Please see above figure for the connector/interface list.)
|
||||
|
||||
|
||||
|
||||
Following jumper are available in the Helios64 board to configure the boot modes:
|
||||
|
||||
- P11 jumper can be used disable SPI Flash, when this jumper is shorted/close it means disable boot from the SPI Flash, and the board will search the next boot device (which is eMMC).
|
||||
- P10 jumper is available to disable eMMC boot, when this jumper is closed Helios64 wil skip looking for bootloader from the eMMC and will continue with the micro-SD card,
|
||||
|
||||
So you can select to search for bootloader starting from the SPI Flash Storage, eMMC, untill micro-SD card.
|
||||
Following table may simplified boot ordering by jumper config by assuming the bootloaders are present in every storage device:
|
||||
|
||||
P11 State|P10 State|Boot Order|Notes
|
||||
-----|---------------|--------------|-------
|
||||
0|0|SPI Flash|-
|
||||
1|0|eMMC|-
|
||||
1|1|micro-SD Card|-
|
||||
|
||||
!!! note
|
||||
Please note, in case of bootloader is not present in the storage devices. The SoC will search to the next possible boot device.
|
||||
|
||||
|
||||
All the ready-to-use images we provide are for the **SD Card** boot mode.
|
||||
|
||||
Please refer to [U-boot](/helios4/uboot) section to know how to use the other modes.
|
||||
|
||||
## HS Select (P13)
|
||||
|
||||
|
|
@ -16,6 +43,8 @@ When this jumper closed the High Speed USB (USB 2.0) connection to the SoC will
|
|||
|
||||
## Power Supply Priority Jumper (P14 & P15)
|
||||
|
||||
|
||||
|
||||
| P15 | P14 | Description |
|
||||
|-----|-----|-------------|
|
||||
| Open | Open | O-Ring Connection |
|
||||
|
|
@ -31,7 +60,9 @@ Production usage only.
|
|||
|
||||
## eFuse Power Enable (P9)
|
||||
|
||||
|
||||
|
||||
Short this jumper using tweezer to burn the efuse data on maskrom mode.
|
||||
|
||||
!!! warning
|
||||
Wrong efuse data can brick Helios64. Do NOT short this jumper on normal use!
|
||||
Wrong efuse data can brick Helios64. Do NOT short this jumper on normal use!
|
||||
|
|
|
|||
|
|
@ -18,7 +18,7 @@ The location of the M.2 socket is shown in below figure:
|
|||
|
||||
## Size
|
||||
|
||||
The maximum size of supported M.2 device is the 228 size.
|
||||
The maximum size of supported M.2 device is the 2280 size.
|
||||
|
||||
## Notes related to M.2 Card
|
||||
The M.2 devices installed in Helios64 is configured as sharing devices with SATA Port 1.
|
||||
|
|
|
|||
|
|
@ -19,7 +19,7 @@ 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:
|
||||
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
|
||||
There are three types of USB controller available on RK3399. Each type has two controller so total USB controllers is 6.
|
||||
|
||||
### Generic OHCI USB 1.1 Controller
|
||||
## Generic OHCI USB 1.1 Controller
|
||||
There are two controller of this type. This controller is Host only controller that is compatible with USB 1.1.
|
||||
Supported speed:
|
||||
|
||||
|
|
@ -12,7 +12,7 @@ Supported speed:
|
|||
|
||||
- Low Speed (1.5 Mbps)
|
||||
|
||||
### Generic EHCI USB 2.0 Controller
|
||||
## 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
|
||||
routed to [Generic OHCI USB 1.1 Controller](#generic-ohci-usb-11-controller).
|
||||
|
|
@ -21,7 +21,7 @@ Supported speed:
|
|||
- High Speed (480 Mbps)
|
||||
|
||||
|
||||
### Synopsys DesignWare USB 3.0 Dual-Role Device Controller
|
||||
## Synopsys DesignWare USB 3.0 Dual-Role Device Controller
|
||||
There are two controller of this type. This controller support On-The-Go /Dual Role which mean it can be configured as Host and also Device.
|
||||
Supported speed:
|
||||
|
||||
|
|
|
|||
|
|
@ -77,7 +77,6 @@ nav:
|
|||
- Hardware:
|
||||
- Overview : 'helios64/hardware.md'
|
||||
- Battery : 'helios64/battery.md'
|
||||
- Boot Mode : 'helios64/boot_mode.md'
|
||||
- Button : 'helios64/button.md'
|
||||
- Front Panel (P3): 'helios64/front-panel.md'
|
||||
- GPIO (P5): 'helios64/gpio.md'
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue