PINE64 - User contributions [en]

NAS Case

2022-03-15T08:09:27Z

AlephNull: Note SDcard or eMMC as mandatory, add recommendation for fan and heatsink. Add my recommendation for positive pressure configuration and rationale.

The PINE64 NAS Case is intended for either a Network Attached Storage (NAS) or Desktop application, but it can also be used in a number of other server capacities. It is built from precision-cut and powder-coated aluminum.

An exploded view of the NAS Case, illustrating how all the components come together, can be found [http://files.pine64.org/doc/rockpro64/ROCKPro64%20NAS%20Case%20Exploded%20View%20Diagram.pdf here]. Please refer back to this PDF document during assembly to verify correct orientation of individual components.
[[file:NASCaseMain.png|400px|thumb|right|Front View of the PINE64 NAS Case for the ROCKPro64]]

==What does the NAS Case house?==
[[File:NAS_Case_internals.jpg|200px|thumb|left|Internal Layout of the NAS Case]]

The NAS Case can house the following components:
*A ROCKPro64 Single Board Computer (SBC) with a tall, mid-size or slim/ no heatsink
*A PCIe to dual SATA adapter or a different low-profile PCIe card, e.g. an NVMe adapter
*Either two 3.5” OR two 2.5” HDDs / SSDs; combination of any two sized drives is accepted
*A 80mm fan with a Ph 2-Pin connector
*Up to three SMA antennas, two of which can be attached to the WiFi/ BT module

==What comes in the box?==
When you purchase the NAS Case from the PINE store the following items are shipped to you:
*The NAS Case itself, which consists of a top and a bottom half as well as an internal HDD SSD mount.
*Two SATA cables
*A custom power cable capable of powering two 2.5” or 3.5” HDDs /SSDs
*The required screws, fittings and a LED relay

==What other bare-minimum things do I need for a NAS build?==
[[File:PCIetoSATA.png|200px|thumb|right|You will need the PCIe to SATA adapter from the PINE64 store to connect your disks to your ROCKPro64 board. [https://forum.pine64.org/showthread.php?tid=6932 '''WARNING''': this adapter does not] [https://forum.pine64.org/showthread.php?tid=6511 work well with two HDD!]]]
To assemble a functional NAS in the NAS Case you will require a number of additional parts.
With the exception of HDDs/SSDs, everything you need for a complete build can be purchased from the PINE store:
*A ROCKPro64 2GB or 4GB board
*A 12V 5A power supply
*A PCIe to dual SATA adapter: [https://forum.pine64.org/showthread.php?tid=6932 '''WARNING''', the SATA adapter from PINE64 store is low-quality and] [https://forum.pine64.org/showthread.php?tid=6511 will not function well with two SATA HDD].
*One or two 2.5”/ 3.5” HDDs (not sold in the PINE store).
*A class 10 micro SD card and/or eMMC module.

You can purchase all the aforementioned items in the [https://www.pine64.org/?post_type=product PINE64 store]

==What other things should I consider buying for a NAS build in the NAS Case?==
There are a few other things which you may wish to consider purchasing for your NAS. These peripherals, while not necessary from an operational standpoint, may contribute to the longevity and stability of your NAS’ operation OR expand it with additional functionality:
* An eMMC to USB 2.0 adapter
* A tall heatsink (N.B. Any of the three available heatsinks will fit in the NAS Case)
* An 80mm fan
* The WiFi / BT module

(The fan and heatsink are highly recommended)

==Which software should I use?==
[[File:OMVGUI.png|200px|thumb|right|The OMV WebGUI is easy to understand but also very robust. It offers easy installation of plugins, system administration and overview of available services]]
If you are intending to build a home or small company NAS, then we strongly recommend you use [[ROCKPro64_Software_Release#OpenMediaVault|Open Media Vault (OMV)]]. OMV is an open source NAS solution that makes setting up user accounts, network shares and services a breeze. It also simplifies installing additional features (called plugins), such as: PLEX media server; Remote Desktop; Encryption; RSync; etc.

Its worth noting that Nextcloud, or other similar Cloud storage solutions, can also be easily installed alongside the OMV OS Image.

Administration and monitoring of OMV is done via an advanced WebGUI, which also allows for updating and upgrading the ROCKPro64.
To learn more about OMV please visit [https://www.openmediavault.org/ their website].

To download the latest OMV build OR one of the numerous available Linux Distribution OS Images please visit the [[ROCKPro64_Software_Release|ROCKPro64 OS download section]].

==Step-by-Step Assembly Instructions==

If you prefer a video tutorial or just want an overview of the process before you start [http://www.youtube.com/watch?v=_UeeklKo0Og check out this instructional video].

===Step 1. Preparation of the NAS Case for Installation===
Remove the top of the NAS Case. It is held together by two screws on either side with the exception of the bottom (left, right, top and back). Once done, the top of the case should lift right off without any resistance.

The next step is to remove the HDD/SSD holding bracket, which is screwed into the bottom of the case. Flip the bottom over and undo the screws which hold the bracket in place.

You should now be left with a bare case ready for installation of the necessary components.

===Step 2. Installing the ROCKPro64 into the NAS Case===
[[File:ROCKPro64inNASCase.jpg|300px|thumb|right|Correct Placement of the ROCKPro64 in the empty case, with Ethernet; Power; and HDMI at the back of the NAS Case]]
[[File:FrontIO.png|300px|thumb|left|Front IO with IR and LED relay installed]]
Make sure nothing is plugged into your ROCKPro64 - including a micro SD card.
If you intend to use a heatsink with your board then please install it now before proceeding. If you bought the heatsink from the Pine64 store it comes with thermal paste and/or a thermal pad. You can use one or the other (not both!). The thermal pad is easier to apply but the thermal paste should be better at cooling if properly applied.

Place your ROCKPro64 into the case with USB 2.0 and 3.0/C ports facing the front of the case. It should fit snugly and align with the port cut-outs in the case. Do not attempt at installing the board at an angle; insert it while holding it level and lowering it into the case.

Secure the board with 4x screws included in the see-through bag. Make sure that the board is held firmly in the case but do not overtighten the screws.

In the see-through bag you will also find a small semi-opaque plastic cylinder. This is the LED light lead and it should be installed from the outside of the case into the hole right over the reset (RST) switch. Simply press it into the hole until it sits tight.

If you wish to install an IRx receiver into your case then you should also place it into the IR socket at this stage. It should align with the cutout right above the power (PWR) switch.

===Step 3 PCIe to SATA adapter and Cabling===
[[File:DC_Location.jpg|200px|thumb|left|DC header on the ROCKPro64 for the power cable]]
[[File:PCIeFittedSATAsockets.png|200px|thumb|right|PCIe to SATA installed. Note the SATA connection orientation]]
With the board in place it's time to set up the PCIe to SATA adapter and do the cabling necessary to attach HDDs / SSDs.

Place the SATA Adapter into the PCIe slot on the ROCKPro64 board so that the holding bracket of the adapter faces the back of the case. In the back of the case there is a cutout for the PCIe adapter; some
variants of the PCIe dual SATA adapter can be configured for eSATA if need be, and the eSATA ports are accessible in the back of the case. By default, the internal SATA connectors are active on the adapter.

Secure the PCIe dual SATA Adapter with a single screw at the top of the bracket, in the back of the NAS Case.

This is the right time to plug in the SATA and custom power cable. The SATA cables plug into the ports on the top or front of the adapter while the power cable plugs into DC header located on the board - just below the power jack, to the left of the Ethernet port (when viewed from front).

Have the cables hang outside the case or to the side for now so that they do not get in the way until they are needed.

===Step 4. Installing HDDs / SSDs into the Holding Bracket===
[[File:Bracket_Orientation.png|300px|thumb|left|Bracket Orientation in the NAS Case]]
The next step is to install HDDs/ SSDs into their holding bracket; 2.5” drives need to be installed at the very bottom of the bracket while 3.5” drives are at the top of the the bracket.

For 2.5” drives make sure that the drives are oriented up and their SATA and power ports face the front of the NAS Case.

For 3.5” HDDs, make sure they are oriented up and their SATA and power ports face the right side of the NAS Case (towards the fan mounting location).

Each drive you mount in the holding bracket requires 4x screws which come supplied in the see-through bag. Make sure the drives are held in place firmly but do not over-tighten the screws.

Once the holding bracket is assembled and you have your drives mounted, please set it aside and proceed to the next step.

===Step 5. Installing Extras (eMMC; WiFi BT module + SMA Antennas; 80mm Fan)===
[[File:80mmfan.png|200px|thumb|right|The 80mm fan is a worthwhile addition to the NAS Case build]]
If you have additional peripherals, such as an eMMC or WiFi/BT module as well as the 80mm fan, then now is the right time to install them. If you have '''none of the above''', please '''proceed to step 6''' of this guide.

The eMMC and WiFi/BT modules are fitted into their respective placements on the ROCKPro64 board - please consult the diagram for their correct installation.

If you intend to use external u.FL to SMA antennas in the NAS Case then this is also the time to install them into the case. In the back section of the case at the very top you will find three cut-outs where the SMA antennas can be fitted. Don’t plug the u.FL leads antenna leads into the WiFi/BT module just yet - instead wait until after the disk holding bracket is installed into the case (step 6).

The fan should be mounted on the right-hand side of the case. We suggest that the fan is oriented for negative pressure, blowing air out of the case rather than taking air in. ([[User:AlephNull]] disagrees and recommends a positive pressure configuration both to allow a filter to be placed over the intake to prevent dust ingress and because the cage on the outlet side of the fan helps keep the wiring for 3.5" disks away from the fan blades). For best cable management results, have the fan power lead face the front of the case so that it can easily be routed to its header located next to GPIO pins on the ROCKPro64.
The fan should be secured using 4x long screws (that fasten into bolts) which can be found in the see-through bag supplied with the NAS Case.
Plug in the fan at this stage of the installation and route the cable at the bottom of the front of the case.

===Step 6. Installing the HDD / SSD Bracket and Routing Cables===
[[File:NASCAsewithdrives.jpg|300px|thumb|right|Complete assembly of the NAS Case]]
[[File:TopViewAssembly.png|300px|thumb|right|Top view of a complete NAS Case Assembly]]
Installing the HDD/SSD bracket into the case and wiring it up is the last step before closing up the case.

Place the bracket with the disks installed (from step 4) into the case. The bracket should line up with the guiding bolts and screw holes at the bottom of the case. The section of the bracket that holds 3.5” HDDs needs to face the left side of the case (when viewed from front) and should overhang the ROCKPro64 board slightly. The 3.5” SATA and power ports should face the right side of the case - where the fan mounts, while 2.5” SATA and power ports should face the front of the case.

With the bracket aligned, flip the bottom of the case over while holding the bracket in place. Screw it into place using 4x Phillips head screws that came included with the NAS Case.

The last thing remaining before the NAS Case can be screwed shut is routing SATA and power cables:
For 3.5” HDDs we suggest routing power and SATA cables underneath the drives, where 2.5” HDDs/SSDs would otherwise reside.

For 2.5” disks you have plenty of routing options as there is much space available. The most obvious route is straight over the disks, where the 3.5” HDDs would reside.

===Step 7. Closing the NAS Case and Powering On your NAS===

Almost there. All that's left to do is to screw together the NAS Case. Screw in the top front screws first followed by screws on either side of the case. Do the back screws last. There, you are done.

To power on your new NAS Case and HDDs all you need to do is to plug in power and Ethernet (This is obviously assuming that you are intending to use it as a NAS or a headless server).

==IO accessibility when the NAS Case is assembled==

When the NAS Case is assembled and screwed shut these ROCKPro64 IO ports remain accessible:
* Micro SD slot
* USB 2.0
* USB 3.0 and USB type C
* Power and Reset switches
* The headphone and microphone jack
* Gigabit Ethernet port
* HDMI

[[Category:ROCKPro64]]

PINE H64

2022-02-22T08:56:33Z

AlephNull: Document the console interface.

[[File:Pineh64.png|400px|thumb|right|The PINE H64 Model B]]

The '''PINE H64 Model B''' is a Single Board Computer by ''PINE64''. It is powered by an Allwinner “H6” Quad-Core ARM Cortex A53 64-Bit Processor with a MALI T-722 GPU. The PINE H64 is equipped with up to 3GB of LPDDR3 PC-1600 system memory and 128Mbit of SPI boot Flash. There is also an optional eMMC module (up to 128GB) and a microSD slot for booting. The board is equipped with an onboard 802.11n Wifi/BT chipset, one USB 3.0 host port, two USB 2.0 host ports, Gigabit Ethernet, a PI-2 GPIO bus, an Euler GPIO bus as well as many other peripheral device interfaces such as UART, SPI, and I2C.

== PINE H64 Models ==

There are two types of PINE H64 models, the Model A and the Model B. The current page is about the Model B. For the Model A see [[PINE H64 Model A]].

== Software Releases==

The following releases are for the PINE H64 Model B

=== Linux ===

==== Armbian ====
[[File:armbian.png|right|100px]]

* Armbian provides a mainline kernel build images for Debian Buster, Debian Bullseye and Ubuntu Focal.
* Two image varieties are offered: server (no desktop environment) or light desktop use (XFCE).
* To find out more about Armbian and available options, including download links and torrents for disk images, please visit their [https://www.armbian.com/pine-h64-b/ page for the H64 model B]

==== AOSC ====
[[File:aosc.png|right|100px]]

===== AOSC Community Build Image with Mate Desktop [microSD Boot] [20190708] =====
* To learn more about AOSC, please visit the official [https://aosc.io/ AOSC website]
* Known issue: no audio sound output.
* DD image (for 8GB microSD card and above)
** [https://files.pine64.org/os/pine-h64/model-B/AOSC/sun50i-h6-pine-h64_sunxi64-mate_2019-07-08.img.xz Direct download from pine64.org]
*** MD5 (GZip file): 7A6EC6A088BA75E4F4BEF884EA93EE6C
*** File Size: 3.47GB
* Login with
** username: aosc
** password: anthon

===== AOSC Community Build Image with Mate Desktop [eMMC Boot] [20180709] =====
* To learn more about AOSC, please visit the official [https://aosc.io/ AOSC website]
* Known issue: no audio sound output.
* DD image (for 8GB microSD card and above)
** [https://files.pine64.org/os/pine-h64/model-B/AOSC/sun50i-h6-pine-h64_sunxi64-mate_2019-07-09_mmc2.img.xz Direct download from pine64.org]
*** MD5 (GZip file): FFEA20480A305A644D2C4CB52DC43046
*** File Size: 3.49GB
* Login with
** username: aosc
** password: anthon

===== AOSC Community Build Image with Mate Desktop [microSD Boot] [20190218] =====
* To learn more about AOSC, please visit the official [https://aosc.io/ AOSC website]
* Known issue: no audio sound output.
* DD image (for 8GB microSD card and above)
** [https://files.pine64.org/os/pine-h64/model-B/AOSC/sun50i-h6-pine-h64_sunxi64-mate_2019-02-18.img.xz Direct download from pine64.org]
*** MD5 (GZip file): 0274E1011BA58A45CB2B2104CEBD23AA
*** File Size: 2.63GB
* Login with
** username: aosc
** password: anthon

===== AOSC Community Build Image with Mate Desktop [eMMC Boot] [20180216] =====
* To learn more about AOSC, please visit the official [https://aosc.io/ AOSC website]
* Known issue: no audio sound output.
* DD image (for 8GB microSD card and above)
** [https://files.pine64.org/os/pine-h64/model-B/AOSC/sun50i-h6-pine-h64_sunxi64-mate_2019-02-16_mmc2.img.xz Direct download from pine64.org]
*** MD5 (GZip file): 34F3F6813EF00FAF49B1C2A1562EE39D
*** File Size: 2.63GB
* Login with
** username: aosc
** password: anthon

==== Manjaro ARM ====
[[File:Manjaro.png|right|100px]]

* Installing and using from Manjaro x64 repositories:
::In your Desktop Environment use the Package Manager and search for '''manjaro-arm-tools''' and install.
::Or in the Terminal use '''sudo pacman -S manjaro-arm-tools''' to install the package.
::Then in the Terminal use '''sudo buildarmimg -d pine-h64 -e <your-favourite-de>''', but change <your favorite DE> to one from the list of supported DE's:
:::* minimal
:::* lxqt
:::* kde-plasma
:::* mate
:::* xfce
:::* i3
:::* sway
:::* gnome (experimental)
:::* plasma-mobile (experimental)
:::* phosh (experimental)
:::* cubocore (not complete yet)
:::* server (not complete yet, unmaintained)
* To find out more about Manjaro-Arm-Tools and available options please visit their [https://gitlab.manjaro.org/manjaro-arm/applications/manjaro-arm-tools site]

==== DietPi ====
[[File:dietpi.png|right|100px]]

* DietPi is a '''lightweight''', yet '''easy to setup''' and '''feature-rich''' Linux distribution, based on '''Debian'''.
* To find out more about DietPi, please visit the [https://dietpi.com/docs/ official documentation].
* Discuss the PINE H64 build on the [https://forum.pine64.org/showthread.php?tid=12531 PINE64 forum thread].
* DD image (for 4 GiB micro SD card and above)
** [https://dietpi.com/downloads/images/DietPi_PINEH64-ARMv8-Bullseye.7z Direct download from dietpi.com]
* Login with
** Username: '''root'''
** Password: '''dietpi'''

==== LibreELEC (KODI) =====
[[File:libreelec.jpg|right|100px]]

===== Nightly Build Image [microSD and eMMC Boot] =====
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]
** [https://test.libreelec.tv/ Pine A64+ build direct download from Libreelec nightly build site and look for LibreELEC-H6.arm-9.80-nightly-xxxxxxxx-xxxxxxx-pine-h64-model-b.img.gz]
** FEATURES:
*** mainline kernel & U-Boot
*** latest Kodi
*** HDMI CEC
*** multi channel HDMI audio (correct audio output must be selected)
*** IR receiver

=== BSD ===

==== FreeBSD ====
[[File:FreeBSD.jpeg|right|100px]]

===== FreeBSD aarch64 Images [microSD Boot] =====
* To learn more about FreeBSD, please visit [https://www.FreeBSD.org/ FreeBSD main page].
* See general information about [https://wiki.freebsd.org/arm/Allwinner FreeBSD on Allwinner ARM] and specific details about [https://wiki.freebsd.org/arm/Allwinner/H6 creating a microSD card for the PINE H64]

==== NetBSD ====
[[File:netbsd.png|right|100px]]

===== NetBSD Community Build Image [microSD Boot] =====
* To learn more about NetBSD please visit [https://www.netbsd.org/ NetBSD main page]
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]
** [https://www.invisible.ca/arm/ Direct download latest release build from NetBSD by select PINE H64]
** size: 345MB
* Console and SSH default login:
** username: root
** password: [none]
* Instructions concerning enabling SSH can be found [https://www.netbsd.org/docs/guide/en/chap-boot.html#chap-boot-ssh here]

=== Android ===

==== Android 9.0 ====
[[File:android_9.png|right|100px]]

===== Stock Android 9.0 microSD Card to eMMC 20190523 =====
* DD image to microSD card, install eMMC module, plug in microSD card into slot and boot.
** After power ON the box for 2-3 second, it will start writing the new image to the eMMC with progress bar. Once finished upload to eMMC, take out microSD card and reboot.
* Highly recommend using [https://etcher.io/ Etcher]
* Support 4K HDR playeback
* non rooted version
* PINE64 IR mapping not yet implemented
* Please allow 10-15 minutes boot up time on first time for initialization
* DD images:
** Using 8GB or above microSD Card
*** [https://files.pine64.org/os/pine-h64/model-B/Android/PINE_H64B_dd_20190523_stock_android_9.0-sd2emmc.img.gz Direct download from pine64.org]
**** MD5 (GZip file): 3B18BA6C82BF3E0020D0B54E9520755E
**** File Size: 1.21GB

===== Stock Android 9.0 microSD and eMMC Boot 20190523 =====
* Support 4K HDR playeback
* Highly recommend using [https://etcher.io/ Etcher]
* non rooted version
* PINE64 IR mapping not yet implemented
* Please allow 20-25 minutes boot up time on first time for initialization
* DD images:
** For 8GB microSD Card or eMMC module
*** [https://files.pine64.org/os/pine-h64/model-B/Android/PINE_H64B_dd_20190523_stock_android_9.0-8GB.img.gz Direct download from pine64.org]
**** MD5 (GZip file): D2244B9FDD5100A4687C16C4A8034884
**** File Size: 1.05GB
** Using 16GB microSD Card or eMMC module
*** [https://files.pine64.org/os/pine-h64/model-B/Android/PINE_H64B_dd_20190523_stock_android_9.0-16GB.img.gz Direct download from pine64.org]
**** MD5 (GZip file): 9AC957ED7B71BA37A363098F6F15C32C
**** File Size: 1.30GB
** Using 32GB microSD Card oe eMMC module
*** [https://files.pine64.org/os/pine-h64/model-B/Android/PINE_H64B_dd_20190523_stock_android_9.0-32GB.img.gz Direct download from pine64.org]
**** MD5 (GZip file): 18BE1EDA248EDDAF35B80195954097A8
**** File Size: 1.28GB
** Using 64GB or above microSD Card
*** [https://files.pine64.org/os/pine-h64/model-B/Android/PINE_H64B_dd_20190523_stock_android_9.0-64GB.img.gz Direct download from pine64.org]
**** MD5 (GZip file): 49EEEBFDEC0337A47879EBE9439F4937
**** File Size: 1.02GB

===== Stock Android 9.0 Phoenix Card image 20190523 =====
* Only use Phoenixcard method as last resort option
*** [https://files.pine64.org/os/pine-h64/android/PhoenixCard4_1_3.zip Phoenixcard ver 4.1.3 utility direct download from pine64.org]
* Select "Start up" as option for SD Card boot
* Select "Product" as option for "SD Card to eMMC" method
* non rooted version
* PINE64 IR mapping not yet implemented
* Please allow 10-15 minutes boot up time on first time for initialization
* This process may not everytime build up successfully
** Using 4GB or above microSD Card
*** [https://files.pine64.org/os/pine-h64/model-B/Android/PINE_H64B_20190523_stock_android_9.0-PhoenixCard.img.gz Direct download from pine64.org]
**** MD5 (Gzip file): B0202A03C189897DEAFCC178B5829BEF
**** File Size: 389MB

==== Android 7.x ====
[[File:android_7.png|right|100px]]

===== Stock Android 7.0 microSD Card Boot 20190115 =====
* Support 4K HDR playeback
* Highly recommend using [https://etcher.io/ Etcher]
* Please allow 10-15 minutes boot up time on first time for initialization
* DD images:
** For 8GB microSD Card
*** [https://files.pine64.org/os/pine-h64/model-B/Android/android-ver7.0-pine-h64b-20190115-sdboot-8G.img.gz Direct download from pine64.org]
**** MD5 (GZip file): 12110D73CA7ADE749C948D63499B2AE3
**** File Size: 417MB
** Using 16GB or above microSD Card
*** [https://files.pine64.org/os/pine-h64/model-B/Android/android-ver7.0-pine-h64b-20190115-sdboot-16G.img.gz Direct download from pine64.org]
**** MD5 (GZip file): FE6DB577CE6D54D3DDF25FD6CB9A8839
**** File Size: 426MB
** Using 32GB or above microSD Card
*** [https://files.pine64.org/os/pine-h64/model-B/Android/android-ver7.0-pine-h64b-20190115-sdboot-32G.img.gz Direct download from pine64.org]
**** MD5 (GZip file): 8E37374D87FFDB5BC6D08635A168A152
**** File Size: 444MB
** Using 64GB or above microSD Card
*** [https://files.pine64.org/os/pine-h64/model-B/Android/android-ver7.0-pine-h64b-20190115-sdboot-64G.img.gz Direct download from pine64.org]
**** MD5 (GZip file): BA29EBCE85A71C408F6AB9FD3EA23885
**** File Size: 482MB

===== Stock Android 7.0 microSD Card to eMMC 20190115 =====
* DD image to microSD card, install eMMC module, plug in muicroSD vard into slot and boot.
** After power ON the box for 2-3 second, it will start writing the new image to the eMMC with progress bar. Once finished upload to eMMC, take out microSD card and reboot.
* Highly recommend using [https://etcher.io/ Etcher]
* Support 4K HDR playeback
* Please allow 10-15 minutes boot up time on first time for initialization
* DD images:
** Using 4GB or above microSD Card
*** [https://files.pine64.org/os/pine-h64/model-B/Android/android-ver7.0-pine-h64b-20190115-sd2emmc.img.gz Direct download from pine64.org]
**** MD5 (GZip file): 61133A2967BDD2806F6AD2E144DD06AB
**** File Size: 414MB

===== Stock Android 7.0 Phoenix Card image 20190115 =====
* Only use Phoenixcard method as last resort option
*** [https://files.pine64.org/os/pine-h64/android/PhoenixCard4_1_3.zip Phoenixcard ver 4.1.3 utility direct download from pine64.org]
* Select "Start up" as option for SD Card boot
* Select "Product" as option for "SD Card to eMMC" method
* Please allow 10-15 minutes boot up time on first time for initialization
* This process may not everytime build up successfully
** Using 4GB or above microSD Card
*** [https://files.pine64.org/os/pine-h64/model-B/Android/android-ver7.0-pine-h64b-20190115-phoenixcard.img Direct download from pine64.org]
**** MD5 (IMG file): 679E5F1A0F772B9F750E4139C8B025F0
**** File Size: 822MB

== SoC and Memory Specification ==
* Based on Allwinner H6
[[File:Allwinner_H64.png]]

=== CPU Architecture ===
* [https://www.arm.com/products/processors/cortex-a/cortex-a53-processor.php Quad-core ARM Cortex-A53 Processor@1488Mhz]
* A power-efficient ARM v8 architecture
* 64 and 32bit execution states for scalable high performance
* Trustzone technology supported
* Support NEON Advanced SIMD (Single Instruction Multiple Data) instruction for acceleration of media and signal processing function
* Support Large Physical Address Extensions(LPAE)
* VFPv4 Floating Point Unit
* 32KB L1 Instruction cache and 32KB L1 Data cache
* 512KB L2 cache

=== GPU Architecture ===
* [https://developer.arm.com/products/graphics-and-multimedia/mali-gpus/mali-t720-gpu ARM Mali T-720MP2 Dual-core GPU]
* Supports OpenGL ES 3.1/3.0/2.0/1.1, OpenCL 1.2/1.1
* Supports ATSC (Adaptive Scalable Texture Compression)
* Supports FAST(4x)FSAA, IO Coherency
* Floating point operation greater than 70 GFLOPS

=== System Memory ===
* RAM Memory Variants: 1GB, 2GB, and 3GB LPDDR3.
* Storage Memory: PINE H64 boards have built-in 128Mb SPI Flash memory, use '''bootable eMMC module''', '''bootable microSD Cards''' or USB attached storage.

== Board Features ==

=== Video ===
* Digital Video 4KP60 (Type A - full)

=== Audio ===
* 3.5mm stereo earphone/microphone plug

=== Network ===
* 10/100/1000Mbps Ethernet
* WiFi 802.11 b/g/n/ac with Bluetooth 4.0/4.1

=== Storage ===
* microSD - bootable, support SDHC and SDXC, storage up to 256GB
* USB - 1 USB3.0 Host port and 2 USB2.0 Host port

=== Expansion Ports ===
* RTC - Real Time Clock Battery Connector
* Wifi/BT Module Header - SDIO 3.0 and UART
* 2x20 pins "Pi2" GPIO Header
* 3x3 pins "EXT" Header giving console, power switch and reset switch access

=== Console ===
* The console UART is available on the 6-pin header connector between the HDMI and headphone jacks. The pins are on the front row, closer to the board's edge: TX, RX, GND, from left (HDMI) to right (headphone).
* The default standard is 8,n,1 at 115200bps.

== Pine H64 Model B Board Information, Schematics and Certifications ==
* Board Dimensions: 85mm x 56mm x 18.8mm
* Input Power: DC 5V @ 3A, 3.5mm OD/ 1.35mm ID DC jack connector

* [https://files.pine64.org/doc/Pine%20H64/Pine%20H64%20model%20B%20Port%20Assignment%20rev2.0.pdf PINE H64 Model B Pi-2 Bus and EXP Bus Connector Pin Assignment]

* PINE H64 Board Schematic:
** [https://files.pine64.org/doc/Pine%20H64/PINE-H6-model-B-20181212-schematic.pdf PINE H64 Model B 1GB/2GB/3GB Rev 1.2 Board Schematic]

* PINE H64 Model B Certification:
** Disclaimer: Please note that PINE64 SBC is not a "final" product and in general certification is not necessary. However, PINE64 still submits the SBC for FCC, CE, and ROHS certifications and obtain the certificates to prove that the SBC board can pass the testing. Please note, a final commercial product needs to perform its own testing and obtain its own certificate.
** [https://files.pine64.org/doc/cert/PINE-H64B%20FCC%20S19041102001001%20Certificate.pdf PINE-H64 Model-B FCC Certificate]
** [https://files.pine64.org/doc/cert/PINE-H64B%20CE-EMC%20S19041102001001%20Certificate.pdf PINE-H64 Model-B CE Certificate]]

== Datasheets for Components and Peripherals ==
* Allwinner H6 SoC information:
** [https://files.pine64.org/doc/datasheet/pine-h64/Allwinner-H6-Brief_V1.0.pdf Allwinner H6 SoC Brief Introduction]
** [https://files.pine64.org/doc/datasheet/pine-h64/Allwinner_H6%20V200_Datasheet_V1.1.pdf Allwinner H6 SoC Data Sheet V1.1 (Official Released Version)]
** [https://files.pine64.org/doc/datasheet/pine-h64/Allwinner_H6%20V200_User_Manual_V1.1.pdf Allwinner H6 SoC User Manual V1.0 (Official Release Version)]
* X-Powers AXP805 PMU (Power Management Unit) information:
** [https://files.pine64.org/doc/datasheet/pine-h64/AXP805_Datasheet_V1.0_en.pdf X-Powers AXP805 Data Sheet V1.0 (Official Release Version)]
* LPDDR3 (178 Balls) SDRAM:
** [https://files.pine64.org/doc/rock64/H9CCNNNCLTMLAR(Rev1.2).pdf Hynix LPDDR3 Datasheet V1.2]
** [https://files.pine64.org/doc/rock64/K4E8E324EB-EGCF000_DRAM_178F_11x11.5_Ver.1.00.00.pdf Samsung LPDDR3 Datasheet V1.00.00]
** [https://files.pine64.org/doc/rock64/SPECTEK_178B_32GB_V91M_MOBILE_LPDDR3.pdf Spectek LPDDR3 Datasheet]
* eMMC information:
** [https://files.pine64.org/doc/rock64/PINE64_eMMC_Module_20170719.pdf PINE64 eMMC module schematic]
** [https://files.pine64.org/doc/rock64/usb%20emmc%20module%20adapter%20v2.pdf PINE64 USB adapter for eMMC module V2 schematic]
** [https://files.pine64.org/doc/rock64/USB%20adapter%20for%20eMMC%20module%20PCB.tar PINE64 USB adapter for eMMC module PCB in JPEG]
** [https://files.pine64.org/doc/datasheet/pine64/E-00517%20FORESEE_eMMC_NCEMAM8B-16G%20SPEC.pdf 16GB Foresee eMMC Datasheet]
** [https://files.pine64.org/doc/datasheet/pine64/SDINADF4-16-128GB-H%20data%20sheet%20v1.13.pdf 32GB/64GB/128GB SanDisk eMMC Datasheet]
* SPI NOR Flash information:
** [https://files.pine64.org/doc/datasheet/pine64/w25q128jv%20spi%20revc%2011162016.pdf WinBond 128Mb SPI Flash Datasheet]
** [https://files.pine64.org/doc/datasheet/pine64/GD25Q128C-Rev2.5.pdf GigaDevice 128Mb SPI Flash Datasheet]
* Ethernet PHY information:
** [https://files.pine64.org/doc/datasheet/pine64/rtl8211e(g)-vb(vl)-cg_datasheet_1.6.pdf Realtek RTL8211 10/100/1000M Ethernet Transceiver for PINE H64 Board]
* Wifi/BT module information:
** [https://files.pine64.org/doc/datasheet/pine64/RTL8723BS.pdf Realtek RTL8723BS WiFi with BT SDIO]
* Remote control button mapping
** [https://files.pine64.org/doc/Pine%20A64%20Schematic/remote-wit-logo.jpg Official Remote Control for the PINE H64 Button Mapping]

= Mali-T720 driver =

Here is a good DRM powerpoint presentation by Free Electron: https://free-electrons.com/pub/conferences/2017/kr/ripard-drm/ripard-drm.pdf

Here is the DRM video presentation by Free Electron: https://www.youtube.com/watch?v=LbDOCJcDRoo

== 32-bit Wayland MALI Driver: ==
** [https://files.pine64.org/doc/MALI/MALI%20EULA.pdf MALI EULA document]
** [https://files.pine64.org/SDK/PINE-H64/mali-t720-r18p0-01rel0-um-016-linux-opengles-release-wayland-server-gbm-composer-arm32-glibc.tar.bz2 MALI-T720 32-bit server binary driver and binary download]
*** MD5: F2186A4CAE505A76E0758735886FE682
*** File Size: 3.4MB
** [https://files.pine64.org/SDK/PINE-H64/mali-t720-r18p0-01rel0-um-016-linux-opengles-release-wayland-client-gbm-composer-arm32-glibc.tar.bz2 MALI-T720 32-bit client binary driver and binary download]
*** MD5: F316A78AFABE87E69C8F816D18F15D68
*** File Size: 3.4MB

== 64-bit Wayland MALI Driver: ==
** [https://files.pine64.org/doc/MALI/MALI%20EULA.pdf MALI EULA document]
** [https://files.pine64.org/SDK/PINE-H64/mali-t720-r18p0-01rel0-um-018-linux-opengles-release-wayland-server-gbm-composer-arm64-glibc.tar.bz2 MALI-T720 64-bit server binary driver and binary download]
*** MD5: 13CC8DCB7CF068D80DFC16281E95E9D7
*** File Size: 5.0MB
** [https://files.pine64.org/SDK/PINE-H64/mali-t720-r18p0-01rel0-um-018-linux-opengles-release-wayland-client-gbm-composer-arm64-glibc.tar.bz2 MALI-T720 64-bit client binary driver and binary download]
*** MD5: 951BAD6ED66D4CB904CFE0D65F2855E8
*** File Size: 5.0MB

= Linux BSP SDK =

== Linux BSP Kernel 4.9 ==
* [https://files.pine64.org/SDK/PINE-H64/PINE%20H64B%20BSP%204.9%20lichee.tar.xz Direct Download from pine64.org]
** MD5 (TAR-XZ file): 06B675B1C217D4CC6A21FF320DA250C1
** File Size: 5.04GB

= Android SDK =

== Android Pie 9.0 SDK version 1.0 ==
* [https://files.pine64.org/SDK/PINE-H64/PINE%20H64B%20android%209.0.tar.xz Direct Download from pine64.org]
** MD5 (TAR-XZ file): 734B4DBB03CAF82A4E955F7E83DE0C65
** File Size: 29.14GB

== Other Resources ==

[[Category:Pine H64]] [[Category:Allwinner H6]]

PINE H64

2022-02-22T08:44:11Z

AlephNull: Add reference to FreeBSD supporting the PINE H64

[[File:Pineh64.png|400px|thumb|right|The PINE H64 Model B]]

The '''PINE H64 Model B''' is a Single Board Computer by ''PINE64''. It is powered by an Allwinner “H6” Quad-Core ARM Cortex A53 64-Bit Processor with a MALI T-722 GPU. The PINE H64 is equipped with up to 3GB of LPDDR3 PC-1600 system memory and 128Mbit of SPI boot Flash. There is also an optional eMMC module (up to 128GB) and a microSD slot for booting. The board is equipped with an onboard 802.11n Wifi/BT chipset, one USB 3.0 host port, two USB 2.0 host ports, Gigabit Ethernet, a PI-2 GPIO bus, an Euler GPIO bus as well as many other peripheral device interfaces such as UART, SPI, and I2C.

== PINE H64 Models ==

There are two types of PINE H64 models, the Model A and the Model B. The current page is about the Model B. For the Model A see [[PINE H64 Model A]].

== Software Releases==

The following releases are for the PINE H64 Model B

=== Linux ===

==== Armbian ====
[[File:armbian.png|right|100px]]

* Armbian provides a mainline kernel build images for Debian Buster, Debian Bullseye and Ubuntu Focal.
* Two image varieties are offered: server (no desktop environment) or light desktop use (XFCE).
* To find out more about Armbian and available options, including download links and torrents for disk images, please visit their [https://www.armbian.com/pine-h64-b/ page for the H64 model B]

==== AOSC ====
[[File:aosc.png|right|100px]]

===== AOSC Community Build Image with Mate Desktop [microSD Boot] [20190708] =====
* To learn more about AOSC, please visit the official [https://aosc.io/ AOSC website]
* Known issue: no audio sound output.
* DD image (for 8GB microSD card and above)
** [https://files.pine64.org/os/pine-h64/model-B/AOSC/sun50i-h6-pine-h64_sunxi64-mate_2019-07-08.img.xz Direct download from pine64.org]
*** MD5 (GZip file): 7A6EC6A088BA75E4F4BEF884EA93EE6C
*** File Size: 3.47GB
* Login with
** username: aosc
** password: anthon

===== AOSC Community Build Image with Mate Desktop [eMMC Boot] [20180709] =====
* To learn more about AOSC, please visit the official [https://aosc.io/ AOSC website]
* Known issue: no audio sound output.
* DD image (for 8GB microSD card and above)
** [https://files.pine64.org/os/pine-h64/model-B/AOSC/sun50i-h6-pine-h64_sunxi64-mate_2019-07-09_mmc2.img.xz Direct download from pine64.org]
*** MD5 (GZip file): FFEA20480A305A644D2C4CB52DC43046
*** File Size: 3.49GB
* Login with
** username: aosc
** password: anthon

===== AOSC Community Build Image with Mate Desktop [microSD Boot] [20190218] =====
* To learn more about AOSC, please visit the official [https://aosc.io/ AOSC website]
* Known issue: no audio sound output.
* DD image (for 8GB microSD card and above)
** [https://files.pine64.org/os/pine-h64/model-B/AOSC/sun50i-h6-pine-h64_sunxi64-mate_2019-02-18.img.xz Direct download from pine64.org]
*** MD5 (GZip file): 0274E1011BA58A45CB2B2104CEBD23AA
*** File Size: 2.63GB
* Login with
** username: aosc
** password: anthon

===== AOSC Community Build Image with Mate Desktop [eMMC Boot] [20180216] =====
* To learn more about AOSC, please visit the official [https://aosc.io/ AOSC website]
* Known issue: no audio sound output.
* DD image (for 8GB microSD card and above)
** [https://files.pine64.org/os/pine-h64/model-B/AOSC/sun50i-h6-pine-h64_sunxi64-mate_2019-02-16_mmc2.img.xz Direct download from pine64.org]
*** MD5 (GZip file): 34F3F6813EF00FAF49B1C2A1562EE39D
*** File Size: 2.63GB
* Login with
** username: aosc
** password: anthon

==== Manjaro ARM ====
[[File:Manjaro.png|right|100px]]

* Installing and using from Manjaro x64 repositories:
::In your Desktop Environment use the Package Manager and search for '''manjaro-arm-tools''' and install.
::Or in the Terminal use '''sudo pacman -S manjaro-arm-tools''' to install the package.
::Then in the Terminal use '''sudo buildarmimg -d pine-h64 -e <your-favourite-de>''', but change <your favorite DE> to one from the list of supported DE's:
:::* minimal
:::* lxqt
:::* kde-plasma
:::* mate
:::* xfce
:::* i3
:::* sway
:::* gnome (experimental)
:::* plasma-mobile (experimental)
:::* phosh (experimental)
:::* cubocore (not complete yet)
:::* server (not complete yet, unmaintained)
* To find out more about Manjaro-Arm-Tools and available options please visit their [https://gitlab.manjaro.org/manjaro-arm/applications/manjaro-arm-tools site]

==== DietPi ====
[[File:dietpi.png|right|100px]]

* DietPi is a '''lightweight''', yet '''easy to setup''' and '''feature-rich''' Linux distribution, based on '''Debian'''.
* To find out more about DietPi, please visit the [https://dietpi.com/docs/ official documentation].
* Discuss the PINE H64 build on the [https://forum.pine64.org/showthread.php?tid=12531 PINE64 forum thread].
* DD image (for 4 GiB micro SD card and above)
** [https://dietpi.com/downloads/images/DietPi_PINEH64-ARMv8-Bullseye.7z Direct download from dietpi.com]
* Login with
** Username: '''root'''
** Password: '''dietpi'''

==== LibreELEC (KODI) =====
[[File:libreelec.jpg|right|100px]]

===== Nightly Build Image [microSD and eMMC Boot] =====
* DD image to microSD card and boot. Highly recommend using [https://etcher.io/ Etcher]
** [https://test.libreelec.tv/ Pine A64+ build direct download from Libreelec nightly build site and look for LibreELEC-H6.arm-9.80-nightly-xxxxxxxx-xxxxxxx-pine-h64-model-b.img.gz]
** FEATURES:
*** mainline kernel & U-Boot
*** latest Kodi
*** HDMI CEC
*** multi channel HDMI audio (correct audio output must be selected)
*** IR receiver

=== BSD ===

==== FreeBSD ====
[[File:FreeBSD.jpeg|right|100px]]

===== FreeBSD aarch64 Images [microSD Boot] =====
* To learn more about FreeBSD, please visit [https://www.FreeBSD.org/ FreeBSD main page].
* See general information about [https://wiki.freebsd.org/arm/Allwinner FreeBSD on Allwinner ARM] and specific details about [https://wiki.freebsd.org/arm/Allwinner/H6 creating a microSD card for the PINE H64]

==== NetBSD ====
[[File:netbsd.png|right|100px]]

===== NetBSD Community Build Image [microSD Boot] =====
* To learn more about NetBSD please visit [https://www.netbsd.org/ NetBSD main page]
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]
** [https://www.invisible.ca/arm/ Direct download latest release build from NetBSD by select PINE H64]
** size: 345MB
* Console and SSH default login:
** username: root
** password: [none]
* Instructions concerning enabling SSH can be found [https://www.netbsd.org/docs/guide/en/chap-boot.html#chap-boot-ssh here]

=== Android ===

==== Android 9.0 ====
[[File:android_9.png|right|100px]]

===== Stock Android 9.0 microSD Card to eMMC 20190523 =====
* DD image to microSD card, install eMMC module, plug in microSD card into slot and boot.
** After power ON the box for 2-3 second, it will start writing the new image to the eMMC with progress bar. Once finished upload to eMMC, take out microSD card and reboot.
* Highly recommend using [https://etcher.io/ Etcher]
* Support 4K HDR playeback
* non rooted version
* PINE64 IR mapping not yet implemented
* Please allow 10-15 minutes boot up time on first time for initialization
* DD images:
** Using 8GB or above microSD Card
*** [https://files.pine64.org/os/pine-h64/model-B/Android/PINE_H64B_dd_20190523_stock_android_9.0-sd2emmc.img.gz Direct download from pine64.org]
**** MD5 (GZip file): 3B18BA6C82BF3E0020D0B54E9520755E
**** File Size: 1.21GB

===== Stock Android 9.0 microSD and eMMC Boot 20190523 =====
* Support 4K HDR playeback
* Highly recommend using [https://etcher.io/ Etcher]
* non rooted version
* PINE64 IR mapping not yet implemented
* Please allow 20-25 minutes boot up time on first time for initialization
* DD images:
** For 8GB microSD Card or eMMC module
*** [https://files.pine64.org/os/pine-h64/model-B/Android/PINE_H64B_dd_20190523_stock_android_9.0-8GB.img.gz Direct download from pine64.org]
**** MD5 (GZip file): D2244B9FDD5100A4687C16C4A8034884
**** File Size: 1.05GB
** Using 16GB microSD Card or eMMC module
*** [https://files.pine64.org/os/pine-h64/model-B/Android/PINE_H64B_dd_20190523_stock_android_9.0-16GB.img.gz Direct download from pine64.org]
**** MD5 (GZip file): 9AC957ED7B71BA37A363098F6F15C32C
**** File Size: 1.30GB
** Using 32GB microSD Card oe eMMC module
*** [https://files.pine64.org/os/pine-h64/model-B/Android/PINE_H64B_dd_20190523_stock_android_9.0-32GB.img.gz Direct download from pine64.org]
**** MD5 (GZip file): 18BE1EDA248EDDAF35B80195954097A8
**** File Size: 1.28GB
** Using 64GB or above microSD Card
*** [https://files.pine64.org/os/pine-h64/model-B/Android/PINE_H64B_dd_20190523_stock_android_9.0-64GB.img.gz Direct download from pine64.org]
**** MD5 (GZip file): 49EEEBFDEC0337A47879EBE9439F4937
**** File Size: 1.02GB

===== Stock Android 9.0 Phoenix Card image 20190523 =====
* Only use Phoenixcard method as last resort option
*** [https://files.pine64.org/os/pine-h64/android/PhoenixCard4_1_3.zip Phoenixcard ver 4.1.3 utility direct download from pine64.org]
* Select "Start up" as option for SD Card boot
* Select "Product" as option for "SD Card to eMMC" method
* non rooted version
* PINE64 IR mapping not yet implemented
* Please allow 10-15 minutes boot up time on first time for initialization
* This process may not everytime build up successfully
** Using 4GB or above microSD Card
*** [https://files.pine64.org/os/pine-h64/model-B/Android/PINE_H64B_20190523_stock_android_9.0-PhoenixCard.img.gz Direct download from pine64.org]
**** MD5 (Gzip file): B0202A03C189897DEAFCC178B5829BEF
**** File Size: 389MB

==== Android 7.x ====
[[File:android_7.png|right|100px]]

===== Stock Android 7.0 microSD Card Boot 20190115 =====
* Support 4K HDR playeback
* Highly recommend using [https://etcher.io/ Etcher]
* Please allow 10-15 minutes boot up time on first time for initialization
* DD images:
** For 8GB microSD Card
*** [https://files.pine64.org/os/pine-h64/model-B/Android/android-ver7.0-pine-h64b-20190115-sdboot-8G.img.gz Direct download from pine64.org]
**** MD5 (GZip file): 12110D73CA7ADE749C948D63499B2AE3
**** File Size: 417MB
** Using 16GB or above microSD Card
*** [https://files.pine64.org/os/pine-h64/model-B/Android/android-ver7.0-pine-h64b-20190115-sdboot-16G.img.gz Direct download from pine64.org]
**** MD5 (GZip file): FE6DB577CE6D54D3DDF25FD6CB9A8839
**** File Size: 426MB
** Using 32GB or above microSD Card
*** [https://files.pine64.org/os/pine-h64/model-B/Android/android-ver7.0-pine-h64b-20190115-sdboot-32G.img.gz Direct download from pine64.org]
**** MD5 (GZip file): 8E37374D87FFDB5BC6D08635A168A152
**** File Size: 444MB
** Using 64GB or above microSD Card
*** [https://files.pine64.org/os/pine-h64/model-B/Android/android-ver7.0-pine-h64b-20190115-sdboot-64G.img.gz Direct download from pine64.org]
**** MD5 (GZip file): BA29EBCE85A71C408F6AB9FD3EA23885
**** File Size: 482MB

===== Stock Android 7.0 microSD Card to eMMC 20190115 =====
* DD image to microSD card, install eMMC module, plug in muicroSD vard into slot and boot.
** After power ON the box for 2-3 second, it will start writing the new image to the eMMC with progress bar. Once finished upload to eMMC, take out microSD card and reboot.
* Highly recommend using [https://etcher.io/ Etcher]
* Support 4K HDR playeback
* Please allow 10-15 minutes boot up time on first time for initialization
* DD images:
** Using 4GB or above microSD Card
*** [https://files.pine64.org/os/pine-h64/model-B/Android/android-ver7.0-pine-h64b-20190115-sd2emmc.img.gz Direct download from pine64.org]
**** MD5 (GZip file): 61133A2967BDD2806F6AD2E144DD06AB
**** File Size: 414MB

===== Stock Android 7.0 Phoenix Card image 20190115 =====
* Only use Phoenixcard method as last resort option
*** [https://files.pine64.org/os/pine-h64/android/PhoenixCard4_1_3.zip Phoenixcard ver 4.1.3 utility direct download from pine64.org]
* Select "Start up" as option for SD Card boot
* Select "Product" as option for "SD Card to eMMC" method
* Please allow 10-15 minutes boot up time on first time for initialization
* This process may not everytime build up successfully
** Using 4GB or above microSD Card
*** [https://files.pine64.org/os/pine-h64/model-B/Android/android-ver7.0-pine-h64b-20190115-phoenixcard.img Direct download from pine64.org]
**** MD5 (IMG file): 679E5F1A0F772B9F750E4139C8B025F0
**** File Size: 822MB

== SoC and Memory Specification ==
* Based on Allwinner H6
[[File:Allwinner_H64.png]]

=== CPU Architecture ===
* [https://www.arm.com/products/processors/cortex-a/cortex-a53-processor.php Quad-core ARM Cortex-A53 Processor@1488Mhz]
* A power-efficient ARM v8 architecture
* 64 and 32bit execution states for scalable high performance
* Trustzone technology supported
* Support NEON Advanced SIMD (Single Instruction Multiple Data) instruction for acceleration of media and signal processing function
* Support Large Physical Address Extensions(LPAE)
* VFPv4 Floating Point Unit
* 32KB L1 Instruction cache and 32KB L1 Data cache
* 512KB L2 cache

=== GPU Architecture ===
* [https://developer.arm.com/products/graphics-and-multimedia/mali-gpus/mali-t720-gpu ARM Mali T-720MP2 Dual-core GPU]
* Supports OpenGL ES 3.1/3.0/2.0/1.1, OpenCL 1.2/1.1
* Supports ATSC (Adaptive Scalable Texture Compression)
* Supports FAST(4x)FSAA, IO Coherency
* Floating point operation greater than 70 GFLOPS

=== System Memory ===
* RAM Memory Variants: 1GB, 2GB, and 3GB LPDDR3.
* Storage Memory: PINE H64 boards have built-in 128Mb SPI Flash memory, use '''bootable eMMC module''', '''bootable microSD Cards''' or USB attached storage.

== Board Features ==

=== Video ===
* Digital Video 4KP60 (Type A - full)

=== Audio ===
* 3.5mm stereo earphone/microphone plug

=== Network ===
* 10/100/1000Mbps Ethernet
* WiFi 802.11 b/g/n/ac with Bluetooth 4.0/4.1

=== Storage ===
* microSD - bootable, support SDHC and SDXC, storage up to 256GB
* USB - 1 USB3.0 Host port and 2 USB2.0 Host port

=== Expansion Ports ===
* RTC - Real Time Clock Battery Connector
* Wifi/BT Module Header - SDIO 3.0 and UART
* 2x20 pins "Pi2" GPIO Header

== Pine H64 Model B Board Information, Schematics and Certifications ==
* Board Dimensions: 85mm x 56mm x 18.8mm
* Input Power: DC 5V @ 3A, 3.5mm OD/ 1.35mm ID DC jack connector

* [https://files.pine64.org/doc/Pine%20H64/Pine%20H64%20model%20B%20Port%20Assignment%20rev2.0.pdf PINE H64 Model B Pi-2 Bus Connector Pin Assignment]

* PINE H64 Board Schematic:
** [https://files.pine64.org/doc/Pine%20H64/PINE-H6-model-B-20181212-schematic.pdf PINE H64 Model B 1GB/2GB/3GB Rev 1.2 Board Schematic]

* PINE H64 Model B Certification:
** Disclaimer: Please note that PINE64 SBC is not a "final" product and in general certification is not necessary. However, PINE64 still submits the SBC for FCC, CE, and ROHS certifications and obtain the certificates to prove that the SBC board can pass the testing. Please note, a final commercial product needs to perform its own testing and obtain its own certificate.
** [https://files.pine64.org/doc/cert/PINE-H64B%20FCC%20S19041102001001%20Certificate.pdf PINE-H64 Model-B FCC Certificate]
** [https://files.pine64.org/doc/cert/PINE-H64B%20CE-EMC%20S19041102001001%20Certificate.pdf PINE-H64 Model-B CE Certificate]]

== Datasheets for Components and Peripherals ==
* Allwinner H6 SoC information:
** [https://files.pine64.org/doc/datasheet/pine-h64/Allwinner-H6-Brief_V1.0.pdf Allwinner H6 SoC Brief Introduction]
** [https://files.pine64.org/doc/datasheet/pine-h64/Allwinner_H6%20V200_Datasheet_V1.1.pdf Allwinner H6 SoC Data Sheet V1.1 (Official Released Version)]
** [https://files.pine64.org/doc/datasheet/pine-h64/Allwinner_H6%20V200_User_Manual_V1.1.pdf Allwinner H6 SoC User Manual V1.0 (Official Release Version)]
* X-Powers AXP805 PMU (Power Management Unit) information:
** [https://files.pine64.org/doc/datasheet/pine-h64/AXP805_Datasheet_V1.0_en.pdf X-Powers AXP805 Data Sheet V1.0 (Official Release Version)]
* LPDDR3 (178 Balls) SDRAM:
** [https://files.pine64.org/doc/rock64/H9CCNNNCLTMLAR(Rev1.2).pdf Hynix LPDDR3 Datasheet V1.2]
** [https://files.pine64.org/doc/rock64/K4E8E324EB-EGCF000_DRAM_178F_11x11.5_Ver.1.00.00.pdf Samsung LPDDR3 Datasheet V1.00.00]
** [https://files.pine64.org/doc/rock64/SPECTEK_178B_32GB_V91M_MOBILE_LPDDR3.pdf Spectek LPDDR3 Datasheet]
* eMMC information:
** [https://files.pine64.org/doc/rock64/PINE64_eMMC_Module_20170719.pdf PINE64 eMMC module schematic]
** [https://files.pine64.org/doc/rock64/usb%20emmc%20module%20adapter%20v2.pdf PINE64 USB adapter for eMMC module V2 schematic]
** [https://files.pine64.org/doc/rock64/USB%20adapter%20for%20eMMC%20module%20PCB.tar PINE64 USB adapter for eMMC module PCB in JPEG]
** [https://files.pine64.org/doc/datasheet/pine64/E-00517%20FORESEE_eMMC_NCEMAM8B-16G%20SPEC.pdf 16GB Foresee eMMC Datasheet]
** [https://files.pine64.org/doc/datasheet/pine64/SDINADF4-16-128GB-H%20data%20sheet%20v1.13.pdf 32GB/64GB/128GB SanDisk eMMC Datasheet]
* SPI NOR Flash information:
** [https://files.pine64.org/doc/datasheet/pine64/w25q128jv%20spi%20revc%2011162016.pdf WinBond 128Mb SPI Flash Datasheet]
** [https://files.pine64.org/doc/datasheet/pine64/GD25Q128C-Rev2.5.pdf GigaDevice 128Mb SPI Flash Datasheet]
* Ethernet PHY information:
** [https://files.pine64.org/doc/datasheet/pine64/rtl8211e(g)-vb(vl)-cg_datasheet_1.6.pdf Realtek RTL8211 10/100/1000M Ethernet Transceiver for PINE H64 Board]
* Wifi/BT module information:
** [https://files.pine64.org/doc/datasheet/pine64/RTL8723BS.pdf Realtek RTL8723BS WiFi with BT SDIO]
* Remote control button mapping
** [https://files.pine64.org/doc/Pine%20A64%20Schematic/remote-wit-logo.jpg Official Remote Control for the PINE H64 Button Mapping]

= Mali-T720 driver =

Here is a good DRM powerpoint presentation by Free Electron: https://free-electrons.com/pub/conferences/2017/kr/ripard-drm/ripard-drm.pdf

Here is the DRM video presentation by Free Electron: https://www.youtube.com/watch?v=LbDOCJcDRoo

== 32-bit Wayland MALI Driver: ==
** [https://files.pine64.org/doc/MALI/MALI%20EULA.pdf MALI EULA document]
** [https://files.pine64.org/SDK/PINE-H64/mali-t720-r18p0-01rel0-um-016-linux-opengles-release-wayland-server-gbm-composer-arm32-glibc.tar.bz2 MALI-T720 32-bit server binary driver and binary download]
*** MD5: F2186A4CAE505A76E0758735886FE682
*** File Size: 3.4MB
** [https://files.pine64.org/SDK/PINE-H64/mali-t720-r18p0-01rel0-um-016-linux-opengles-release-wayland-client-gbm-composer-arm32-glibc.tar.bz2 MALI-T720 32-bit client binary driver and binary download]
*** MD5: F316A78AFABE87E69C8F816D18F15D68
*** File Size: 3.4MB

== 64-bit Wayland MALI Driver: ==
** [https://files.pine64.org/doc/MALI/MALI%20EULA.pdf MALI EULA document]
** [https://files.pine64.org/SDK/PINE-H64/mali-t720-r18p0-01rel0-um-018-linux-opengles-release-wayland-server-gbm-composer-arm64-glibc.tar.bz2 MALI-T720 64-bit server binary driver and binary download]
*** MD5: 13CC8DCB7CF068D80DFC16281E95E9D7
*** File Size: 5.0MB
** [https://files.pine64.org/SDK/PINE-H64/mali-t720-r18p0-01rel0-um-018-linux-opengles-release-wayland-client-gbm-composer-arm64-glibc.tar.bz2 MALI-T720 64-bit client binary driver and binary download]
*** MD5: 951BAD6ED66D4CB904CFE0D65F2855E8
*** File Size: 5.0MB

= Linux BSP SDK =

== Linux BSP Kernel 4.9 ==
* [https://files.pine64.org/SDK/PINE-H64/PINE%20H64B%20BSP%204.9%20lichee.tar.xz Direct Download from pine64.org]
** MD5 (TAR-XZ file): 06B675B1C217D4CC6A21FF320DA250C1
** File Size: 5.04GB

= Android SDK =

== Android Pie 9.0 SDK version 1.0 ==
* [https://files.pine64.org/SDK/PINE-H64/PINE%20H64B%20android%209.0.tar.xz Direct Download from pine64.org]
** MD5 (TAR-XZ file): 734B4DBB03CAF82A4E955F7E83DE0C65
** File Size: 29.14GB

== Other Resources ==

[[Category:Pine H64]] [[Category:Allwinner H6]]

File:FreeBSD.jpeg

2022-02-22T08:41:46Z

AlephNull: Official FreeBSD Mark in vertical orientation.

== Summary ==
Official FreeBSD Mark in vertical orientation.

ROCK64 Premium Aluminum Casing

2022-02-22T08:13:31Z

AlephNull: Note that the case is mostly compatible with the PINE H64 as well as the ROCK64

[[File:Rock64-Al-Case1-1.jpg|thumb|The case, fully assembled with a ROCK64 inside of it]]

The '''ROCK64 Premium Aluminum Casing''' is an aluminum case for the [[ROCK64]] single-board computer sold by Pine64 through their [https://pine64.com/product/model-b-premium-aluminum-casing/?v=0446c16e2e66 official store]. It includes an integrated heat spreader with an included thermal pad that allows the SoC to sink its generated heat into the metal case.

== Installation ==

Make sure the LED light guide and rubber plug are taken out of the case. Drop your ROCK64 into the bottom half of the case with the ports in the correct place. Tighten it with the four included round top screws, using a Phillips #00 screw driver.

Install the light guide and the rubber plug by pushing them in from the outside.

Ideally, clean the SoC of any possible residue with some isopropyl alcohol. Next, remove the plastic foil protecting the thermal pad on the top half of the case, and slot the top half into place, making sure that the HDMI and audio jack ports fall into their respective place in the side section (see [[#HDMI and Audio Jack Clearance Issues]] if they don't.)

Once the top half is firmly in place, screw in the four flat top screws with a Phillips #00 screw driver.

== Performance ==

The built in heat spreader does do its job at sinking heat into the case. [[User:CounterPillow]] finds that during a lengthy kernel compilation at 22°C ambient temperature, the average SoC temperature measured around 60°C. The case during such sustained loads becomes warm to the touch, which means it is working as a heat sink.

== Tips and Tricks ==

=== HDMI and Audio Jack Clearance Issues ===

Some cases may not allow the ROCK64 IO to snugly fit into its predestined cutout holes on its long side. If this is the case for you, try loosening the screws on the HDMI, power and audio jack port side, and only tightening the screws on the GPIO side to still make good ground contact. The HDMI and audio jacks should then fit into their holes snugly. If you wish to try, you can also try adjusting the screws holding in the posts on the bottom of the case.

=== Plastic Pegs for PWR and RST Buttons ===

[[File:Button peg cad.png|thumb|FreeCAD displaying the peg. Bottom part goes inside the case.]]

If you are tired of using a pen or a toothpick to push the buttons, there are [[Media:Button.zip|3d-printable plastic pegs you can download]] and print yourself. Recommended material is PLA, excellent results can be obtained using a 0.25mm nozzle, though slightly larger sizes should work fine as well.

To use the pegs, open your case and remove the ROCK64 from within. Be sure to pull out the light guide and rubber plug to remove it, or else it will catch on them. Once it is removed, turn your bottom half of the case such that the holes for PWR and RST are pointing towards the floor, and drop the pegs into the holes from inside the case, so that the lip prevents them from falling through. Hold them in position with your finger, turn the case the right side up again, and reinstall your ROCK64.

[[File:ROCK64 Aluminum Casing Plastic Peg Mod Photo.jpeg|thumb|left|Plastic Pegs in their place]]

You should now have buttons that can be pressed from outside the case without any utensils.

If you do not own a 3d printer, contact [[User:CounterPillow]]. He may mail you some for free in an envelope.

=== Remove the black anodised layer from the heat pad ===

Anodising has a significantly poorer thermal conductivity than aluminium, therefore grinding off the anodising before fitting the blue thermal pad should result in a lower CPU temperature.

=== Using the case with the PINE H64 ===

Whilst the case is sold as a ROCK64 accessory, all the connectors and mounting screws on the [[PINE H64]] are in the same spots. The only difficulty is that the H6 CPU is closer to the "Pi2" connector and extends beyond the edge of the heat spreader by about 5mm. [[User:AlephNull]] used a piece of copper shim on top of the H6 (with a smear of thermal paste) to spread the heat back to the thermal pad. In this configuration, the CPU stabilised at about 76°C running 4 copies of a CPU stress test. Whilst a lower temperature might be nice, this is still well below the 125°C limit.

[[Category:Rock64]]

ROCK64 Premium Aluminum Casing

2022-02-22T07:42:28Z

AlephNull: /* Tips and Tricks */ Suggest grinding off the anodising.

PineCone

2021-07-24T10:30:35Z

AlephNull: /* Pinenut-01S Module information and schematics */ Clarify firmware behaviour.

{{Note|Page under construction, information subject to change.}}
[[File:Pine64_BL602_EVB_photo-3-small.jpg|thumb|PineCone BL602 EVB (Evaluation Board)]]

== BL602 Specifications ==
* '''CPU:''' 32-bit RV32IMAFC RISC-V “SiFive E24 Core”
** [https://www.sifive.com/cores/e24 SiFive E24 Core information]
* '''Memory:'''
** 128KB ROM
** 276KB SRAM
** 1Kb eFuse
** 2MB Embedded Flash
* '''Security:'''
** Secure boot
** Secure debug
** AES 128/192/256
** SHA-1/224/256
** TRNG (True Random Number Generator)
** PKA (Public Key Accelerator)
* '''Wireless:'''
** Wi-Fi 802.11 b/g/n
** Bluetooth® Low Energy 5.0
** Wi-Fi Fast connection with BLE assistance
** Wi-Fi and BLE coexistence
** Wi-Fi Security WPS/WEP/WPA/WPA2/WPA3
** STA, SoftAP and sniffer modes
** Multi-Cloud connectivity
** 2.4 GHz RF transceiver
** Integrated RF balun, PA/LNA
* '''Package Type:'''
** 32 pin QFN 4mm x 4mm
* JTAG support (See below for BL602 impact)

[[File:BL602_Block_Diagram.jpg|600px]]

== JTAG ==
{| class="wikitable floatright"
|+ Default JTAG pins
|-
| GPIO Pin || JTAG Pin
|-
| GPIO17 || TDI
|-
| GPIO11 || TDO
|-
| GPIO12 || TMS
|-
| GPIO14 || TCK
|-
|}

BL602 multiplexes four GPIO pins to provide the familiar JTAG lines. See the accompanying table for the default pin mappings.

These are the default JTAG pins in use after a cold boot. However, many pieces of software, including the demo that's installed by default on new PineCones, remap these pins to other functions. You cannot use the default wiring for JTAG while such software is running. This issue is especially prevalent on the PineCone because three of the default JTAG pins are connected to the onboard RGB LED. Nothing about the LED itself interferes with JTAG, but any program that uses the LED will necessarily remap some of the default JTAG pins to be GPIO.

The MaskROM download mode that the BL602 enters when you tie GPIO8 high does '''not''' remap the default JTAG pins, and so you can and should use that mode while checking basic functionality of your JTAG adapter.

Note that, just as software can remap the default JTAG pins to be something else, it can also remap other pins to be JTAG. Control over this is quite granular, with 5-6 candidate pins for each individual JTAG signal that can be mapped independently of one another. LEE Lup Yuen has written some [https://lupyuen.github.io/articles/openocd#free-the-led-from-jtag-port sample code] showing how to remap the JTAG pins so that your software can use the LED without giving up support for debugging.

== Pine64 USB JTAG Adapter information and schematics ==
* [https://files.pine64.org/doc/Pinenut/PINE64%20USB%20JTAG%20Adapter%20Schematic-20201215.pdf PINE64 USB JTAG Adapter schematic 20202018 1.0]
* [[:File:PINE64_USB_JTAG_Adapter_Schematic_ver_1.0a-20210109.pdf|PINE64 USB JTAG Adapter schematic 20210109 1.0a]]

== PineCone BL602 EVB information and schematics ==
* Approximate dimensions: 26mm x 43mm
* Board layout:
[[File:PADI-II_EVB.png]]
* [https://files.pine64.org/doc/Pinenut/Pine64%20BL602%20EVB%20Schematic%20ver%201.1.pdf PineCone BL602 EVB schematic ver 1.1]
** Note: In PineCone revision 1.1 ("BL62B_EVB V1.1" silkscreened on back of board), CC1 and CC2 share one 5.1KΩ resistor. This means the board will fail to power when you use an e-marked USB-C cable like the one that comes with Apple chargers. See [https://medium.com/@leung.benson/how-to-design-a-proper-usb-c-power-sink-hint-not-the-way-raspberry-pi-4-did-it-f470d7a5910 this article] for details of why this happens. The next schematic design will give each line its own 5.1KΩ resistor as per the USB-C specification.
* The board uses a CH340 Serial/USB adapter. This chip is commonly used in Arduino-class development boards. It is a full speed (12Mbps) USB interface and has vendor ID 0x1a86 with product ID 0x7523.
* The GPIO pins (11, 12, 14, 17) plus the nearby RESET, POWER, and GND pins are all located on one side of the board, on J1 to provide JTAG connection.

== Pinenut-01S Module information and schematics ==
[[File:Pinenut-01S_PCB-Front.png|225px]][[File:Pinenut-01S_PCB-Back.png|225px]]
* [https://files.pine64.org/doc/Pinenut/Pinenut-01S%20V1.01%20SCH.pdf Pinenut-01S schematic ver 1.01]
* [https://wiki.pine64.org/images/6/6b/PineNut-01S_v1.01_KiCad.zip PineNut-01S KiCad schematic ver 1.01]
* [https://files.pine64.org/doc/Pinenut/NUT-01S%20GPIO%20Definition%20ver%201.0.pdf Pinenut-01S GPIO Definition ver 1.0]
* [https://files.pine64.org/doc/Pinenut/USB%20Adapter%20for%20Pinenut-01S%20Schematic%20V1.0.pdf USB Programmer adapter for Pinenut-01S schematic ver 1.0]
* The default firmware runs the UART at 2000000 bps. It will accept input whilst regularly outputting:<code> proc_hellow_entry: RISC-V rv32imafc cur key status:1</code>

== Pinenut-12S Module information ==
[[File:NUT-12S_module-front.jpg|200px]][[File:NUT-12S_module-back.jpg|200px]]
* [https://files.pine64.org/doc/Pinenut/NUT-12S%20GPIO%20Definition%20ver%201.0.pdf Pinenut-12S GPIO Definition ver 1.0]

== Datasheets for components and peripherals ==
* Bouffalo BL-602 SoC information:
** [https://github.com/bouffalolab/bl_docs Bouffalo Lab's official bl_docs repository]: should always contain the latest SoC documentation available, in PDF, HTML, and reStructuredText source forms.
** [https://github.com/pine64/bl602-docs/tree/main/mirrored PINE64's bl602-docs repository]: contains an archive of all historical datasheets and reference manual PDFs but may lag behind Bouffalo's official repository. If you notice that it is, please submit a pull request!
* USB/Serial adapter:
** [https://cdn.sparkfun.com/datasheets/Dev/Arduino/Other/CH340DS1.PDF CH340 serial converter]

== Misc notes ==
Planned to be available in at least three form factors:
* NUT-01S -> ESP-01S
* NUT-12S -> ESP-12S
* NUT-15 -> RTL8723/AMPAK

== Loading code ==
To load code, you must move the jumper to the position closest to the edge, press reset, load the code, move the jumper back toward the center of the board, and press reset again.

There are currently a number of loaders in progress, each with differing degrees of completeness and success on various operating systems.
* In the build tree, there is BLFlashCube for Windows, which is a proprietary GUI for flashing images. Linux and macOS binaries are available via [https://dev.bouffalolab.com/download Bouffalo Lab's developer portal].
* [https://github.com/stschake/bl60x-flash bl60x-flash] is in Python and has been reported successful on MacOS catalina (10.15.6) by Punnerud and madushan1000.
* [https://github.com/bouffalolab/BLOpenFlasher BLOpenFlasher] is a WIP, written in go, by Bouffalo Labs to provide source for a flash utility.
* [https://github.com/renzenicolai/bl602tool bl602tool] is a Python utility in development.
* [https://pypi.org/project/bflb-eflash-loader/ Bouffalo's Python Flash Loader] is a new (Dec 20) flash loader by the makers of the chip.
* <del>[https://pypi.org/project/bflb-image-build/ Bouffalo's image build] smooshes code and adds headers for downloads.</del>
* [https://pypi.org/project/bflb-mcu-tool/ Bouffalo's MCU tool] (Mar 2021) image tool replaced the above. Now combined with eflash loader, deals with partitions, DTS, signing, fuses etc.
* [https://github.com/spacemeowx2/blflash blflash serial flasher] BL602 serial flasher, inspired by BLOpenFlasher

== Development efforts ==
* [https://github.com/pine64/bl_iot_sdk PineCone BL602 GitHub Page (PINE64 fork)] has compilers, linkers, and all the code to build on Windows, Linux (x86_64), and MacOS.
* [https://github.com/bouffalolab/bl_iot_sdk Bouffalo Lab GitHub Page]
* [https://github.com/renzenicolai/bl602-docs/ BL602 Developer organize documentation GitHub Page]
* [https://github.com/renzenicolai/bl602tool BL602 Developer organize tool GitHub Page]
* [https://github.com/stschake/bl60x-flash Programming tool for Bouffalo Labs BL602/BL604 chips]
* [https://github.com/pine64/bl602-re BL602 reverse engineering working group]
* [https://github.com/pine64/bl602-sdio-linux Linux kernel module]
* [https://github.com/tchebb/bl602-docs BL602 Documentation]
* [https://github.com/spacemeowx2/blflash BL602 serial flasher]
* [https://github.com/mkroman/awesome-bouffalo#feature-matrix Awesome Bouffalo]

== Articles and Blogs ==
* [https://lupyuen.github.io/articles/pinecone Quick Peek of PineCone BL602 RISC-V Evaluation Board by Lup Yuen]
* [https://maero.dk/bl602-firmware-image-format/ Documenting the BouffaloLab BL602 firmware image format by MK]
* [https://lupyuen.github.io/articles/openocd Connect PineCone BL602 to OpenOCD by Lup Yuen]
* [https://lupyuen.github.io/articles/debug Debug Rust on PineCone BL602 with VSCode and GDB by Lup Yuen]
* [https://lupyuen.github.io/articles/mynewt Porting Mynewt to PineCone BL602 by Lup Yuen]
* [https://lupyuen.github.io/articles/flash Flashing Firmware to PineCone BL602 by Lup Yuen]
* [https://lupyuen.github.io/articles/led Control PineCone BL602 RGB LED with GPIO and PWM by Lup Yuen]
* [https://lupyuen.github.io/articles/gpio Mynewt GPIO ported to PineCone BL602 RISC-V Board by Lup Yuen]
* [https://lupyuen.github.io/articles/i2c PineCone BL602 talks to I2C Sensors by Lup Yuen]
* [https://lupyuen.github.io/articles/spi PineCone BL602 talks SPI too! by Lup Yuen]
* [https://lupyuen.github.io/articles/display PineCone BL602 Blasting Pixels to ST7789 Display with LVGL Library by Lup Yuen]
* [https://lupyuen.github.io/articles/uart PineCone BL602 Talks UART to Grove E-Ink Display by Lup Yuen]
* [https://lupyuen.github.io/articles/book The RISC-V BL602 Book by Lup Yuen]
* [https://lupyuen.github.io/articles/lora Connect PineCone BL602 to LoRa Transceiver by Lup Yuen]
* [https://lupyuen.github.io/articles/wisblock RAKwireless WisBlock talks LoRa with PineCone BL602 RISC-V Board by Lup Yuen]
* [https://lupyuen.github.io/articles/lora2 PineCone BL602 RISC-V Board Receives LoRa Packets by Lup Yuen]
* [https://lupyuen.github.io/articles/rust Run Rust RISC-V Firmware with BL602 IoT SDK by Lup Yuen]
* [https://lupyuen.github.io/articles/lorawan PineCone BL602 Talks LoRaWAN by Lup Yuen]
* [https://lupyuen.github.io/articles/lisp uLisp and Blockly on PineCone BL602 RISC-V Board by Lup Yuen]
* [https://lupyuen.github.io/articles/wasm Simulate RISC-V BL602 with WebAssembly, uLisp and Blockly by Lup Yuen]
* [https://lupyuen.github.io/articles/boot BL602 Bootloader by Lup Yuen]
* [https://lupyuen.github.io/articles/tflite Machine Learning on RISC-V BL602 with TensorFlow Lite by Lup Yuen]
* [https://lupyuen.github.io/articles/wifi Reverse Engineering WiFi on RISC-V BL602 by Lup Yuen]

[[Category:Nutcracker]]

PineCone

2021-07-24T10:07:23Z

AlephNull: /* Pinenut-01S Module information and schematics */ Clarify default firmware behaviour.

{{Note|Page under construction, information subject to change.}}
[[File:Pine64_BL602_EVB_photo-3-small.jpg|thumb|PineCone BL602 EVB (Evaluation Board)]]

== BL602 Specifications ==
* '''CPU:''' 32-bit RV32IMAFC RISC-V “SiFive E24 Core”
** [https://www.sifive.com/cores/e24 SiFive E24 Core information]
* '''Memory:'''
** 128KB ROM
** 276KB SRAM
** 1Kb eFuse
** 2MB Embedded Flash
* '''Security:'''
** Secure boot
** Secure debug
** AES 128/192/256
** SHA-1/224/256
** TRNG (True Random Number Generator)
** PKA (Public Key Accelerator)
* '''Wireless:'''
** Wi-Fi 802.11 b/g/n
** Bluetooth® Low Energy 5.0
** Wi-Fi Fast connection with BLE assistance
** Wi-Fi and BLE coexistence
** Wi-Fi Security WPS/WEP/WPA/WPA2/WPA3
** STA, SoftAP and sniffer modes
** Multi-Cloud connectivity
** 2.4 GHz RF transceiver
** Integrated RF balun, PA/LNA
* '''Package Type:'''
** 32 pin QFN 4mm x 4mm
* JTAG support (See below for BL602 impact)

[[File:BL602_Block_Diagram.jpg|600px]]

== JTAG ==
{| class="wikitable floatright"
|+ Default JTAG pins
|-
| GPIO Pin || JTAG Pin
|-
| GPIO17 || TDI
|-
| GPIO11 || TDO
|-
| GPIO12 || TMS
|-
| GPIO14 || TCK
|-
|}

BL602 multiplexes four GPIO pins to provide the familiar JTAG lines. See the accompanying table for the default pin mappings.

These are the default JTAG pins in use after a cold boot. However, many pieces of software, including the demo that's installed by default on new PineCones, remap these pins to other functions. You cannot use the default wiring for JTAG while such software is running. This issue is especially prevalent on the PineCone because three of the default JTAG pins are connected to the onboard RGB LED. Nothing about the LED itself interferes with JTAG, but any program that uses the LED will necessarily remap some of the default JTAG pins to be GPIO.

The MaskROM download mode that the BL602 enters when you tie GPIO8 high does '''not''' remap the default JTAG pins, and so you can and should use that mode while checking basic functionality of your JTAG adapter.

Note that, just as software can remap the default JTAG pins to be something else, it can also remap other pins to be JTAG. Control over this is quite granular, with 5-6 candidate pins for each individual JTAG signal that can be mapped independently of one another. LEE Lup Yuen has written some [https://lupyuen.github.io/articles/openocd#free-the-led-from-jtag-port sample code] showing how to remap the JTAG pins so that your software can use the LED without giving up support for debugging.

== Pine64 USB JTAG Adapter information and schematics ==
* [https://files.pine64.org/doc/Pinenut/PINE64%20USB%20JTAG%20Adapter%20Schematic-20201215.pdf PINE64 USB JTAG Adapter schematic 20202018 1.0]
* [[:File:PINE64_USB_JTAG_Adapter_Schematic_ver_1.0a-20210109.pdf|PINE64 USB JTAG Adapter schematic 20210109 1.0a]]

== PineCone BL602 EVB information and schematics ==
* Approximate dimensions: 26mm x 43mm
* Board layout:
[[File:PADI-II_EVB.png]]
* [https://files.pine64.org/doc/Pinenut/Pine64%20BL602%20EVB%20Schematic%20ver%201.1.pdf PineCone BL602 EVB schematic ver 1.1]
** Note: In PineCone revision 1.1 ("BL62B_EVB V1.1" silkscreened on back of board), CC1 and CC2 share one 5.1KΩ resistor. This means the board will fail to power when you use an e-marked USB-C cable like the one that comes with Apple chargers. See [https://medium.com/@leung.benson/how-to-design-a-proper-usb-c-power-sink-hint-not-the-way-raspberry-pi-4-did-it-f470d7a5910 this article] for details of why this happens. The next schematic design will give each line its own 5.1KΩ resistor as per the USB-C specification.
* The board uses a CH340 Serial/USB adapter. This chip is commonly used in Arduino-class development boards. It is a full speed (12Mbps) USB interface and has vendor ID 0x1a86 with product ID 0x7523.
* The GPIO pins (11, 12, 14, 17) plus the nearby RESET, POWER, and GND pins are all located on one side of the board, on J1 to provide JTAG connection.

== Pinenut-01S Module information and schematics ==
[[File:Pinenut-01S_PCB-Front.png|225px]][[File:Pinenut-01S_PCB-Back.png|225px]]
* [https://files.pine64.org/doc/Pinenut/Pinenut-01S%20V1.01%20SCH.pdf Pinenut-01S schematic ver 1.01]
* [https://wiki.pine64.org/images/6/6b/PineNut-01S_v1.01_KiCad.zip PineNut-01S KiCad schematic ver 1.01]
* [https://files.pine64.org/doc/Pinenut/NUT-01S%20GPIO%20Definition%20ver%201.0.pdf Pinenut-01S GPIO Definition ver 1.0]
* [https://files.pine64.org/doc/Pinenut/USB%20Adapter%20for%20Pinenut-01S%20Schematic%20V1.0.pdf USB Programmer adapter for Pinenut-01S schematic ver 1.0]
* UART is at 2000000 baud by default. Default firmware seems to output something, but it's not text.

== Pinenut-12S Module information ==
[[File:NUT-12S_module-front.jpg|200px]][[File:NUT-12S_module-back.jpg|200px]]
* [https://files.pine64.org/doc/Pinenut/NUT-12S%20GPIO%20Definition%20ver%201.0.pdf Pinenut-12S GPIO Definition ver 1.0]

== Datasheets for components and peripherals ==
* Bouffalo BL-602 SoC information:
** [https://github.com/bouffalolab/bl_docs Bouffalo Lab's official bl_docs repository]: should always contain the latest SoC documentation available, in PDF, HTML, and reStructuredText source forms.
** [https://github.com/pine64/bl602-docs/tree/main/mirrored PINE64's bl602-docs repository]: contains an archive of all historical datasheets and reference manual PDFs but may lag behind Bouffalo's official repository. If you notice that it is, please submit a pull request!
* USB/Serial adapter:
** [https://cdn.sparkfun.com/datasheets/Dev/Arduino/Other/CH340DS1.PDF CH340 serial converter]

== Misc notes ==
Planned to be available in at least three form factors:
* NUT-01S -> ESP-01S
* NUT-12S -> ESP-12S
* NUT-15 -> RTL8723/AMPAK

== Loading code ==
To load code, you must move the jumper to the position closest to the edge, press reset, load the code, move the jumper back toward the center of the board, and press reset again.

There are currently a number of loaders in progress, each with differing degrees of completeness and success on various operating systems.
* In the build tree, there is BLFlashCube for Windows, which is a proprietary GUI for flashing images. Linux and macOS binaries are available via [https://dev.bouffalolab.com/download Bouffalo Lab's developer portal].
* [https://github.com/stschake/bl60x-flash bl60x-flash] is in Python and has been reported successful on MacOS catalina (10.15.6) by Punnerud and madushan1000.
* [https://github.com/bouffalolab/BLOpenFlasher BLOpenFlasher] is a WIP, written in go, by Bouffalo Labs to provide source for a flash utility.
* [https://github.com/renzenicolai/bl602tool bl602tool] is a Python utility in development.
* [https://pypi.org/project/bflb-eflash-loader/ Bouffalo's Python Flash Loader] is a new (Dec 20) flash loader by the makers of the chip.
* <del>[https://pypi.org/project/bflb-image-build/ Bouffalo's image build] smooshes code and adds headers for downloads.</del>
* [https://pypi.org/project/bflb-mcu-tool/ Bouffalo's MCU tool] (Mar 2021) image tool replaced the above. Now combined with eflash loader, deals with partitions, DTS, signing, fuses etc.
* [https://github.com/spacemeowx2/blflash blflash serial flasher] BL602 serial flasher, inspired by BLOpenFlasher

== Development efforts ==
* [https://github.com/pine64/bl_iot_sdk PineCone BL602 GitHub Page (PINE64 fork)] has compilers, linkers, and all the code to build on Windows, Linux (x86_64), and MacOS.
* [https://github.com/bouffalolab/bl_iot_sdk Bouffalo Lab GitHub Page]
* [https://github.com/renzenicolai/bl602-docs/ BL602 Developer organize documentation GitHub Page]
* [https://github.com/renzenicolai/bl602tool BL602 Developer organize tool GitHub Page]
* [https://github.com/stschake/bl60x-flash Programming tool for Bouffalo Labs BL602/BL604 chips]
* [https://github.com/pine64/bl602-re BL602 reverse engineering working group]
* [https://github.com/pine64/bl602-sdio-linux Linux kernel module]
* [https://github.com/tchebb/bl602-docs BL602 Documentation]
* [https://github.com/spacemeowx2/blflash BL602 serial flasher]
* [https://github.com/mkroman/awesome-bouffalo#feature-matrix Awesome Bouffalo]

== Articles and Blogs ==
* [https://lupyuen.github.io/articles/pinecone Quick Peek of PineCone BL602 RISC-V Evaluation Board by Lup Yuen]
* [https://maero.dk/bl602-firmware-image-format/ Documenting the BouffaloLab BL602 firmware image format by MK]
* [https://lupyuen.github.io/articles/openocd Connect PineCone BL602 to OpenOCD by Lup Yuen]
* [https://lupyuen.github.io/articles/debug Debug Rust on PineCone BL602 with VSCode and GDB by Lup Yuen]
* [https://lupyuen.github.io/articles/mynewt Porting Mynewt to PineCone BL602 by Lup Yuen]
* [https://lupyuen.github.io/articles/flash Flashing Firmware to PineCone BL602 by Lup Yuen]
* [https://lupyuen.github.io/articles/led Control PineCone BL602 RGB LED with GPIO and PWM by Lup Yuen]
* [https://lupyuen.github.io/articles/gpio Mynewt GPIO ported to PineCone BL602 RISC-V Board by Lup Yuen]
* [https://lupyuen.github.io/articles/i2c PineCone BL602 talks to I2C Sensors by Lup Yuen]
* [https://lupyuen.github.io/articles/spi PineCone BL602 talks SPI too! by Lup Yuen]
* [https://lupyuen.github.io/articles/display PineCone BL602 Blasting Pixels to ST7789 Display with LVGL Library by Lup Yuen]
* [https://lupyuen.github.io/articles/uart PineCone BL602 Talks UART to Grove E-Ink Display by Lup Yuen]
* [https://lupyuen.github.io/articles/book The RISC-V BL602 Book by Lup Yuen]
* [https://lupyuen.github.io/articles/lora Connect PineCone BL602 to LoRa Transceiver by Lup Yuen]
* [https://lupyuen.github.io/articles/wisblock RAKwireless WisBlock talks LoRa with PineCone BL602 RISC-V Board by Lup Yuen]
* [https://lupyuen.github.io/articles/lora2 PineCone BL602 RISC-V Board Receives LoRa Packets by Lup Yuen]
* [https://lupyuen.github.io/articles/rust Run Rust RISC-V Firmware with BL602 IoT SDK by Lup Yuen]
* [https://lupyuen.github.io/articles/lorawan PineCone BL602 Talks LoRaWAN by Lup Yuen]
* [https://lupyuen.github.io/articles/lisp uLisp and Blockly on PineCone BL602 RISC-V Board by Lup Yuen]
* [https://lupyuen.github.io/articles/wasm Simulate RISC-V BL602 with WebAssembly, uLisp and Blockly by Lup Yuen]
* [https://lupyuen.github.io/articles/boot BL602 Bootloader by Lup Yuen]
* [https://lupyuen.github.io/articles/tflite Machine Learning on RISC-V BL602 with TensorFlow Lite by Lup Yuen]
* [https://lupyuen.github.io/articles/wifi Reverse Engineering WiFi on RISC-V BL602 by Lup Yuen]

[[Category:Nutcracker]]

ROCKPro64

2021-05-09T01:41:35Z

AlephNull: /* Setup a serial console (UART) */ Summarise the serial port details and include a "don't connect RxD until it has started booting" warning.

The [https://www.pine64.org/rockpro64/ '''ROCKPro64'''] is the most powerful Single Board Computer released by Pine64. It is powered by a Rockchip RK3399 Hexa-Core (dual ARM Cortex A72 and quad ARM Cortex A53) 64-Bit Processor with a MALI T-860 Quad-Core GPU.

Key features include a PCIe x4 open ended slot, the use of LPDDR4 RAM, and industry standard heatsink mounting holes.

The ROCKPro64 is equipped with 2GB or 4GB LPDDR4 system memory, and 128Mb SPI boot Flash. There is also an optional eMMC module (up to 128GB) and microSD slot for booting. The board is equipped with 1x USB 3.0 type C Host with DP 1.2, 1x USB 3.0 type A Host, 2x USB 2.0 Host, Gigabit Ethernet, PI-2 GPIO Bus, MiPi DSI interface, eDP interface, touch Panel interface, stereo MiPi CSI interface, as well as many other device interfaces such as UART, SPI, I2C, for makers to integrate with sensors and other peripherals. Many different Operating Systems (OS) are freely available from the open source community, such as Android, Linux (Ubuntu, Debian, Arch), and BSD.

= Board layout =
[[File:ROCKPro64_annotated.jpg]]

[[File:ROCKPro64v21FRONT.jpg|200px|thumb|right|A hi-res picture of v2.1 front]]

[[File:ROCKPro64v21REAR.jpg|200px|thumb|right|A hi-res picture of v2.1 rear]]

== Main chips ==
* RK3399 system-on-chip (1)
* LPDDR4 SDRAM 1 (18)
* LPDDR4 SDRAM 2 (3)
* SPI NOR flash memory (17)
* RK808 power management (near 19)
* RTL8211 ethernet transceiver (near 25)
* ES8316 Sound Codec (on rear of board)
* The heatsink mounting holes around the RK3399 are 59 mm apart

== Switches ==

The Power button (11, SW3): is the same as on your mobile phone - press and release after about 1 second to power on. Press and hold for about 3 seconds to power off.

The Reset button (10, SW901): perfoms a reset.

The Recover button (28, SW900): used to enter maskrom mode.

== Connectors, sockets and headers ==
{| class="wikitable sortable"
! Diagram !! Schematic designator || Silkscreen label !! Number of pins !! Description
|-
| style="text-align: center;" | 2 || U39 || PI-2-bus || style="text-align: center;" | 40 || Pi-2 bus
|-
| style="text-align: center;" | 4 || J8 || +FAN- || style="text-align: center;" | 2 || PWM controlled fan header
|-
| style="text-align: center;" | 5 || J10 || SPDIF || style="text-align: center;" | 3 || SPDIF header
|-
| style="text-align: center;" | 6 || U6 || +RTC- || style="text-align: center;" | 2 || RTC battery backup header
|-
| style="text-align: center;" | 7 || U31 || Wifi-BT || style="text-align: center;" | 16 || SDIO WIFI/BT module-MIMO 2
|-
| style="text-align: center;" | 8 || USB3 || || style="text-align: center;" | 9 || USB-3 and USB Type C
|-
| style="text-align: center;" | 9 || USB1 || || style="text-align: center;" | 2×4 || Dual USB-2
|-
| style="text-align: center;" | 12 || IR1 || IR || style="text-align: center;" | 3 || infrared receiver socket
|-
| style="text-align: center;" | 13 || J16 || Headphone+mic || style="text-align: center;" | 4 || Headphone + mic 3.5mm jack
|-
| style="text-align: center;" | - || CON16 || GND PWR RST GND || style="text-align: center;" | 4 || Power & reset, unpopulated header near Headphone jack
|-
| style="text-align: center;" | 14 || U29 || EMMC || style="text-align: center;" | 34 || eMMC connector
|-
| style="text-align: center;" | 14* || J13 || || style="text-align: center;" | 13 || TF-card, a.k.a. microSD (* under 14 on the bottom side)
|-
| style="text-align: center;" | 15 || U30 || || style="text-align: center;" | 14 || SDIO WIFI/BT module-MIMO 1
|-
| style="text-align: center;" | 16 || SW4 || || style="text-align: center;" | 2 || Jumper to [[#Disable eMMC]]
|-
| style="text-align: center;" | 19 || J15 || PCI || style="text-align: center;" | 64 || PCI-express X4 socket
|-
| style="text-align: center;" | 20 || J21 || DSI || style="text-align: center;" | 30 || DSI
|-
| style="text-align: center;" | 21 || J22 || EDP || style="text-align: center;" | 30 || LCD EDP
|-
| style="text-align: center;" | 22 || CON1 || TP || style="text-align: center;" | 6 || touch panel connector
|-
| style="text-align: center;" | 23 || CON15 || || style="text-align: center;" | 4 || DC out for SATA disk cable (direct connect from DC-IN)
|-
| style="text-align: center;" | 24 || J11 || DC-IN || style="text-align: center;" | 2 || Power input, positive tip; 12V/3A (minimum) recommended
|-
| style="text-align: center;" | 25 || U32 || || style="text-align: center;" | 8 || RJ45
|-
| style="text-align: center;" | 26 || J14 || || style="text-align: center;" | 19 || HDMI
|-
| style="text-align: center;" | 27 || J17 || MIPI CAM || style="text-align: center;" | 32 || MIPI-1
|-
| style="text-align: center;" | 29 || J19 || MIPI CAM || style="text-align: center;" | 32 || MIPI-2
|-
| style="text-align: center;" | 30 || J18 || CIF || style="text-align: center;" | 26 || CIF
|}

== LEDs ==

A green LED next to the 12V input barrel connector will light as long as there is 12V applied to the connector. (Even if the RockPro64 is powered off.)

A white LED behind the reset button will light as long as the RockPro64 is running (it comes on a few seconds after power on, when control is passed to the operating system.)

A red LED behind the reset button is DIY - it is lit for example if the board is in OTG mode with an Ayufan image, or if an Android image is in standby mode.

Yellow and green LEDs on the LAN socket behave in a standard way.

== Jumpers ==
They are used for boot device selection, as described in the following section.

=== Disable eMMC ===

There is an unlabelled (on the PCB silk-screen) 2-pin jumper (16) between the eMMC socket (14) and the SPI chip (17). It is designated as SW4 on the [[#Board Information, Schematics and Certifications | schematic diagram]]. The default condition is OPEN (no jumper). It is useful for controlling the boot as follows:

Default boot device (with no SPI software) is eMMC, then SDcard. If both the eMMC and the SDcard contain bootable images then the eMMC can be disabled by installing the jumper. This completely removes the eMMC from the resulting OS. If you wish the eMMC to be visible in the booted OS the jumper should be removed 2 seconds after applying power (and before the white LED comes on).

The possible combinations are summarised in the table below (1 = present, 0 = not present, S = boot from the µSD card, M = boot from the eMMC module, X = unsupported combination):

{| class="wikitable sortable" style="text-align: center;"
! µSD !! eMMC !! SW4 !! boot
|-
| 0 || 0 || 0 || X
|-
| 0 || 0 || 1 || X
|-
| 0 || 1 || 0 || M
|-
| 0 || 1 || 1 || X
|-
| 1 || 0 || 0 || S
|-
| 1 || 0 || 1 || S
|-
| 1 || 1 || 0 || M
|-
| 1 || 1 || 1 || S
|}

=== Disable SPI (while booting) ===
There is a second possibility to jumper your ROCKPro64: If you mess-up your SPI and are unable to boot, jumpering pins 23 (CLK) and 25 pin (GND) on the PI-2-bus header will disable the SPI as a boot device. (This was taken from the IRC logs, 09 August 2018 @ 17:23) You have to remove the jumper 2 seconds after having started your RP64 (before the white LED turns ON) otherwise the SPI will be missing and you won't be able to flash it.
Ayufan images contain (at the moment) only one script for the SPI and the RP64, it's "rockpro64_reset_spi_flash". Other SPI scripts are dedicated to the R64 (as it is written on the name) and it will mess-up your RP64 SPI if you use them.

= Getting Started =

This section gives important information to get the board up and running.

== Software and OS Image Builds ==

In the '[[ROCKPro64 Software Release]]' page you will find a complete list of currently supported Operating System images that work with the ROCKPro64 as well as other related software. The Software Release page has links to download the images as well as high level instructions how to load each image.

The list includes OS images and descriptions of:

[[ROCKPro64_Software_Release#Armbian|'''Armbian (microSD and eMMC Boot)''']]

[[ROCKPro64_Software_Release#Debian_by_mrfixit2001|'''Debian (microSD and eMMC Boot)''']]

[[ROCKPro64_Software_Release#DietPi|'''DietPi (microSD and eMMC Boot)''']]

[[ROCKPro64_Software_Release#OpenMediaVault|'''Open Media Vault (microSD and eMMC Boot)''']]

[[ROCKPro64_Software_Release#LibreELEC.28KODI.29|'''LibreELEC for KODI (microSD and eMMC Boot)''']]

[[ROCKPro64_Software_Release#Slackware|'''Slackware (microSD and eMMC Boot)''']]

[[ROCKPro64_Software_Release#Nems_Linux|'''Nagios Enterprise Monitoring Server (microSD and eMMC Boot)''']]

[[ROCKPro64_Software_Release#NextCloudPi|'''NextCloudPi (microSD and eMMC Boot)''']]

[[ROCKPro64_Software_Release#Cent_OS|'''Cent OS (microSD Boot)''']]

[[ROCKPro64_Software_Release#Manjaro_ARM|'''Manjaro ARM (microSD and eMMC Boot)''']]

[[ROCKPro64_Software_Release#OpenWrt|'''OpenWrt (microSD and eMMC Boot)''']]

Please see the [[NOOB]] page for detailed discussion of what you need (prerequisites) as well as instructions if the high level instructions are insufficient.

== More advanced Linux bits ==

Some Linux tips are given below.

=== How to update your Linux ===

For Debian/Ubuntu images entering the following commands at a terminal prompt

<code>sudo apt-get update</code> 
<code>sudo apt-get upgrade</code>

will keep your installation up to date. To update Ayufan images to the next release (when available) use the following command

<code>sudo apt-get dist-upgrade</code>

If you are happy to update your system to pre-releases of Ayufan images then modify /etc/apt/sources.list.d/ayufan-rock64.list as per the comment in that file.

The kernel in Ayufan releases is under active development and, if you wish to install a later version, then it is best to use a package manager. In synaptic (for example), if you search for package names linux-image-4.4 you should see your currently installed version(s) as well as any more recent ones. Similarly if you wish to install the mainline kernel then searching for linux-image-4.18 will show you what is available. '''At the time of writing (August 2018) there are significant features missing from the mainline kernel for aarch64 processors (e.g. HDMI sound).'''

=== Useful scripts ===
After you install an Ayufan image you will find some scripts in /usr/local/sbin/ and /usr/local/bin/ that may be useful. (Need to expand this section)

=== Video playback ===
Ayufan has some old documentation on [https://github.com/ayufan-rock64/linux-build/blob/master/recipes/video-playback.md video playback here.] For your ROCKPro64 the install should be

<code>sudo apt-get install ffmpeg mpv libmali-rk-midgard-t86x-r14p0-gbm</code>

(These modules are included in the Ayufan deskop releases.) At which stage rkmpv myvideo.mp4 will play a fullscreen, hardware assisted, version of your video. rkmpv is at /usr/local/bin/rkmpv

=== Swapping kernel versions ===
extlinux is in use on Ayufan images (at least) which enables some switching between installed kernel versions - [https://github.com/ayufan-rock64/linux-build/blob/master/recipes/extlinux.md intro documentation is here.] In particular after you install any additional kernels, you can edit your /boot/extlinux/extlinux.conf file to specify which of the kernels you have installed to use for the next boot.

From Ayufan version 0.7.11 the script /usr/local/sbin/change-default-kernel.sh does a nice little menu swap for you if you run it as root (sudo).

=== Using an NVMe disk for rootfs ===
Forum member Bullet64 has documented [https://forum.frank-mankel.org/topic/208/booten-von-der-nvme-platte how to move rootfs to an NVMe disk.] This is useful until we get a full SPI option to boot from the NVMe.

== More advanced bits related to any OS ==

This section gives some hints for advanced users.

=== Setup a serial console (UART)===
The early adopters (and late-comers who fiddle excessively with their boards or don't want to use a keyboard and monitor) have a need to monitor the low-level boot behaviour: this is done with a serial console.
The console is a 3.3v serial port using pins 8 (TxD from RK3399) and 10 (RxD to RK3399) of U39 (the PI-2 bus), with pin 6 as a convenient ground, running at 1500000,N,8,1 (1.5Mbps).
Do not connect RxD (pin 10) until the U-Boot SPL is running (see [[RK3399 boot sequence]]) or the SPL will not start.
There is a great, detailed description how to get this working specifically on the ROCKPro64 [https://forum.pine64.org/showthread.php?tid=6387 here].

=== Booting from USB or PXE ===

The default choice of boot device is first eMMC (if present) then SDcard. See [[ ROCKPro64_Main_Page#Disable_eMMC | jumpers above for details on adjusting this sequence.]]

It is possible to flash the SPI to extend the options for boot devices to USB drives or PXE. The preferred method is now the rock64_write_spi_flash.sh script (see [[ROCKPro64_Main_Page#Useful_scripts | useful scripts above.]]) The NOOB wiki page has more details [[NOOB#Flashing_u-boot_to_SPI_Flash | here.]]

Background info and historic details of this usage [https://github.com/ayufan-rock64/linux-build/blob/master/recipes/flash-spi.md can be found here.]

=== Boot sequence ===

The RockPro64 boot sequence has been documented [https://github.com/sigmaris/u-boot/wiki/RockPro64-boot-sequence here] by sigmaris.

=== OTG mode ===

You can boot your ROCKPro64 into OTG mode with the use of the Recover button (see [[ROCKPro64_Main_Page#Switches | switch 28 above.]]) Note there are 2 OTG ports on your ROCKPro64: the type-C USB 3 socket is definitely one. From the schematic it appears the USB 3 (type A) socket is the other, but this has yet to be confirmed.

The method is to power off the board. Then push and hold the Recover button and push and release the Power button.
* If you have an Ayufan bootable image in either the SDcard or eMMC then there are 4 OTG modes [https://github.com/ayufan-rock64/linux-u-boot/commit/ea6efecdfecc57c853a6f32f78469d1b2417329b described here] including Android fastboot, RockUSB and MaskROM modes. Releasing the Recover button as soon as the white LED lights counts as 1 blink. Keeping it pressed you will get 2 blinks of the white LED etc. Once the board enters OTG mode the red LED will be lit. In mode 1 the boot and linux-root partitions of the card with the Ayufan image (partitions 6 & 7 of a linux installation) are made available as devices. In all cases the USB device made available at the host has device ID 18d1:d00d.
* If you do not have an Ayufan image in either the SDcard or the eMMC, then neither white nor red LEDs will light, but the board will enter MaskROM mode where the USB device made available at the host has device ID 2207:330c.

=== NVMe drives ===
Please be aware that [https://pine64.com/product/rockpro64-pci-e-x4-to-m-2-ngff-nvme-ssd-interface-card the Pine64 SSD interface card] is intended for use with NVMe devices. These can be identified by the fact they have a single (Key M) notch, e.g. [https://www.wdc.com/content/dam/wdc/website/products/family/wd-black-pcie-ssd/wdfWDBlackSSD_PCIe_img1.jpg.imgw.500.500.jpg the WD Black devices.]

While M2/NGFF SATA devices (with a Key B notch, typically have Key M as well) will physically fit, they will not work. e.g. [https://www.wdc.com/content/dam/wdc/website/products/personal/internal_storage/wd_blue_3d_nand_sata_ssd/blue3d_product-overview.jpg.imgw.1000.1000.jpg WD Blue devices.]

=== SATA drives ===
SATA drives can be connected directly via the [https://pine64.com/?product=rockpro64-pci-e-to-dual-sata-ii-interface-card ROCKPro64 PCIe interface card.] Please note the card does not include the power cable - that is a [https://pine64.com/?product=rockpro64-power-cable-for-dual-sata-drives separate item.] Equally you must be aware that connecting SATA drives in this manner means they will be drawing power from your ROCKPro64 - please ensure you are using a 5A or better power supply.

ExplainingComputers did a YouTube [https://www.youtube.com/watch?v=9CCQicHwfDI ROCKPro64 PCIe SATA card review and tests using a Ubuntu console and OpenMediaVault.]

=== Wi-Fi & Bluetooth module ===
If you have bought the [https://pine64.com/product/rockpro64-1x1-dual-band-wifi-802-11ac-bluetooth-5-0-module Wi-Fi and Bluetooth module] from the Pine store then instructions for connecting it can be found on the accessories page [[ Accessories_Step_by_Step_Guides#Wifi.2FBluetooth_module | here.]] '''Please note that the 0.7.9 Ayufan's linux releases (August 2018) have deliberately DISABLED support for this module in the search for stability. It can be tested and used with the Android image.'''

It can also be used on Manjaro by installing ap6256-firmware and wireless-regdb packages.

=== 7" LCD Touch Screen ===
Instructions for connecting the [https://pine64.com/?product=7-lcd-touch-screen-panel LCD touch screen] from the Pine [[ Accessories_Step_by_Step_Guides#7.22_LCD_Touch_Screen_Panel | are here.]]

'''Note at present (August 2018) this screen is only supported by the Android image.'''

{{warning|1= When using the touchscreen ensure the cables are properly connected and tightened down and that you do not let the metal backplane touch the SBC}}

=== RTC battery backup ===
The Pine store has a couple of options for RTC battery backups: a [https://pine64.com/product/rtc-backup-battery-holder-2-x-aaa AAA version here] or a [https://pine64.com/product/rtc-backup-battery-holder-cr-2032 CR-2032 version here.] Instructions for plugging in either of them are also on the [[ Accessories_Step_by_Step_Guides| Accessories page ]]

=== Acryllic open enclosure ===
Assembly instructions for the [https://pine64.com/product/pine-a64-rockpro64-acrylic-open-enclosure acrylic enclosure] from the Pine store are also on the [[ Accessories_Step_by_Step_Guides| Accessories page ]]

=== NAS case ===
The [https://files.pine64.org/doc/rockpro64/ROCKPro64%20NAS%20Case%20Exploded%20View%20Diagram.pdf Exploded View Installation Diagram] for the [https://pine64.com/product/rockpro64-metal-desktop-nas-casing NAS case from the Pine store].

Detailed '''NAS Case overview and assembly instructions''' can be found [[NASCase | here]].

= [[ROCKPro64_Hardware_Accessory_Compatibility|Hardware Compatibility]] =
== Hardware Compatibility Page ==
Please contribute to the hardware compatibility page, which lists hardware which has been tested with the rockpro64, whether successful or not.

* [[ROCKPro64_Hardware_Accessory_Compatibility#PCIe devices|PCIe devices]]
* [[ROCKPro64_Hardware_Accessory_Compatibility#NVMe_SSD_drives|NVMe SSD drives]]
* [[ROCKPro64_Hardware_Accessory_Compatibility#USB_hardware|USB hardware]]
* [[ROCKPro64_Hardware_Accessory_Compatibility#USB_C_alternate_mode_DP|USB C alternate mode DP]]
* [[ROCKPro64_Hardware_Accessory_Compatibility#Other_hardware|Other hardware]]

== Limitations ==
=== PCIe card issue and/or asynchronous external abort on flash read/write ===
==== Older firmware overwrites actively used memory ====
Some people get system freeze when:
* use SATA disk with ROCKPro64 PCIe card. (maybe on newer PCIe card ASM1062 vs ASM1061)
* or do read or write 4GB to the flash. (not using PCIe)

If you connect the serial console you will see a Linux kernel oops: (a)synchronous external abort.

Both issues are in fact the same software BUG. There is no hardware problem.
Currently most OS do use uboot with a rockpro blob FW which use memory that Linux kernel is not aware of.
People are currently fixing this BUG, but it may take some time.
In the mean time, you can fix it manually.

The latest u-boot can boot the rockpro64 without any blobs from rockchip. Install first arm-none-eabi-gcc and aarch64-linux-gnu-gcc compiler, then run the following commands:

git clone https://github.com/ARM-software/arm-trusted-firmware.git atf
make -C atf CROSS_COMPILE=aarch64-linux-gnu- PLAT=rk3399 bl31
git clone https://gitlab.denx.de/u-boot/u-boot.git u-boot
cd u-boot/
git checkout v2020.01-rc5
make rockpro64-rk3399_defconfig
BL31=../atf/build/rk3399/release/bl31/bl31.elf make ARCH=arm CROSS_COMPILE=aarch64-linux-gnu-

Which gives you idbloader.img and u-boot.itb. Copy them to the rockpro64, and run the following: (Or put your SD card into your PC)

sudo dd if=idbloader.img of=/dev/mmcblk0 seek=64
sudo dd if=u-boot.itb of=/dev/mmcblk0 seek=16384
sync

==== PCIe controller hardware error handling bug ====
There is an issue with the rk3399 pcie controller that is currently unmitigated:
*[https://lore.kernel.org/linux-pci/CAMdYz...gmail.com/ LKML Original Thread]
*[https://lkml.org/lkml/2020/4/6/320 LKML Additional Information]

The rk3399 pcie controller throws either a synchronous abort or a SError when a pcie device sends an unknown message.

The error type is determined by which cpu cluster handles the message.

=== Virtualization ===
The PCIe controller on the rk3399 is not behind an IOMMU.
This means it is not possible to safely pass through PCIe devices to a virtual machine.

= Board Features =

This section outlines the most important characteristics of the board and its components.

== SoC and Memory Specification ==
* Based on Rockchip RK3399
[[File:Rockchip_RK3399.png|right]]

=== CPU Architecture ===
* [https://developer.arm.com/products/processors/cortex-a/cortex-a72 Dual-core Cortex-A72 up to 2.0GHz CPU]
* [https://developer.arm.com/products/processors/cortex-a/cortex-a53 Quad-core Cortex-A53 up to 1.5GHz CPU]
* big.LITTLE architecture: Dual Cortex-A72 + Quad Cortex-A53, 64-bit CPU
* Cortex-A72:
** 1-4x Symmetrical Multiprocessing (SMP) within a single processor cluster, and multiple coherent SMP processor clusters through AMBA 5 CHI or AMBA 4 ACE technology
** AArch64 for 64-bit support and new architectural features
** L1 cache 48KB Icache and 32KB Dcache for each A72
** L2 cache 1024KB for big cluster
** DSP & SIMD extensions
** VFPv4 floating point
** Hardware virtualization support
* Cortex-A53:
** L1 cache 32KB Icache and 32KB Dcache for each A53
** L2 cache 512KB for little cluster
* Full implementation of the ARM architecture v8-A instruction set
* ARM Neon Advanced SIMD (single instruction, multiple data) support for accelerated media and signal processing computation
* ARMv8 Cryptography Extensions
* In-order pipeline with symmetric dual-issue of most instructions
* Include VFP v3 hardware to support single and double-precision operations
* TrustZone technology support
* Full CoreSight debug solution
* One isolated voltage domain to support DVFS

=== GPU Architecture ===
* [https://developer.arm.com/products/graphics-and-multimedia/mali-gpus/mali-t860-and-mali-t880-gpus ARM Mali-T860MP4 Quad-core GPU]
* The highest performance GPUs built on Arm Mali’s famous Midgard architecture, the Mali-T860 GPU is designed for complex graphics use cases and provide stunning visuals for UHD content.
* Frequency 650MHz
* Throughput 1300Mtri/s, 10.4Gpix/s
* OpenGL® ES 1.1, 1.2, 2.0, 3.1, 3.2., Vulkan 1.0*., OpenCL™ 1.1, 1.2., DirectX® 11 FL11_1., RenderScript™.

=== System Memory ===
* LPDDR4 RAM Memory Variants: Dual Channels 2GB and 4GB.
* Storage Memory: 128Mb built-in SPI Flash memory (as at August 2018 only support for USB boot).

== Display ==
* Dual VOP: one supports 4096x2160 with AFBC supported；The other supports 2560x1600
* Dual channel MIPI-DSI (4 lanes per channel)
* eDP 1.3 (4 lanes with 10.8Gbps) to support display, with PSR
* Digital Video port up to 4Kp60
* DisplayPort 1.2 (4 lanes, up to 4K 60Hz)
* Supports Rec.2020 and conversion to Rec.709

== Video ==
* Digital Video output up to 4K@60Hz
* 4K HDR @ 30fps
* H.264/AVC Base/Main/High/High10 profile @ level 5.1; up to 4Kx2K @ 60fps
* H.265/HEVC Main/Main10 profile @ level 5.1 High-tier; up to 4Kx2K @ 60fps
* VP9, up to 4Kx2K @ 60fps
* MPEG-1, ISO/IEC 11172-2, up to 1080P @ 60fps
* MPEG-2, ISO/IEC 13818-2, SP@ML, MP@HL, up to 1080P @ 60fps
* MPEG-4, ISO/IEC 14496-2, SP@L0-3, ASP@L0-5, up to 1080P @ 60fps
* VC-1, SP@ML, MP@HL, AP@L0-3, up to 1080P @ 60fps
* MVC is supported based on H.264 or H.265, up to 1080P @ 60fps

== Audio ==
* 3.5mm Phone Jack
* 3-pin S/PDIF header
* Audio via Digital Video port

== Camera ==
* Dual mipi CSI，dual ISP,Maximum input resolution of 13M pixels

== Network ==
* 10/100/1000Mbps Ethernet
* Wi-Fi 802.11 ac/a/b/g/n with Bluetooth 4.01 (old version with 2x2) / Bluetooth 5 (new version with 1x1) (optional)

== Storage ==
* microSD - bootable, support SDHC and SDXC, storage up to 256GB
* eMMC - bootable (optional eMMC Module)
* 1 USB3.0 Host port
* 1 USB type C OTG port with DP output
* 2 USB2.0 Dedicated Host ports

== Expansion Ports ==
* 2x20 pins "Pi2" GPIO Header
* PCIe 2.1 (4 full-duplex lanes with 20Gbps) x4 open ended port

== Working Features ==
{| class="wikitable sortable"
! style="font-weight:bold;" | Feature/Option
! style="font-weight:bold;" | Android
! style="font-weight:bold;" | Android Version
! style="font-weight:bold;" | Linux
! style="font-weight:bold;" | Linux Version
! style="font-weight:bold;" | Test/Verify Steps
! style="font-weight:bold;" | Notes
! style="font-weight:bold;" | Product Link
|-
| Pine64 LCD Touchscreen (Screen/Touch)
| Yes/Yes
|
| No/No
|
|
| Maybe this will help get this working? https://github.com/avafinger/pine64-touchscreen
| https://pine64.com/?product=7-lcd-touch-screen-panel
|-
| ROCKPro64 2×2 MIMO Dual Band WIFI 802.11AC / BLUETOOTH 4.2 MODULE (old)
ROCKPro64 1x1 Dual Band WIFI 802.11AC / BLUETOOTH 5.0 MODULE (new)
| Yes/Yes
|
| No/No
|
|
| In 0.7.9 Ayufan linux releases this is deliberately disabled for stability reasons.
| https://store.pine64.org/product/rockpro64-1x1-dual-band-wifi-802-11acbluetooth-5-0-module
|-
| USB OTG
|
|
|
|
| use this script: https://github.com/ayufan-rock64/linux-package/blob/master/root-rockpro64/usr/local/sbin/rockpro64_enable_otg.sh then configure ip on usb0: ifconfig usb0 169.169.222.222 and run iperf, you should likely see about 200-300MB/s
| https://wiki.pine64.org/index.php/ROCKPro64_Main_Page#OTG_mode
|
|-
| USB Mass Storage USB2/USB3
| Yes/yes
|
| Yes/Yes
|
|
|
|
|-
| Dedicated Fan Power (pwm1)
|
|
| Yes
|
|
| You might want to use ATS. https://github.com/tuxd3v/ats
|
|-
| GPIO pins (raw or via RPI python scripts)
|
|
|
|
|
| Check out what Frank Mankel has done. https://forum.frank-mankel.org/topic/292/rockpro64-rp64-gpio/2
|
|-
| MIPI CSI Camera 1 and 2
|
|
|
|
|
|
|
|-
| eDP
|
|
|
|
|
|
|
|-
| HDMI Audio
| Yes
| 7.1.2
| Yes
| 4.4.132-1083 - 4.4.138-1100
|
| Stopped working in 4.4.154.1105. Ayufan is looking into it.
|
|-
| 3.5mm Audio/Mic
|
|
|
|
|
|
|
|-
| USB-C Host
|
|
|
|
|
|
|
|-
| Display via USB-C
| Yes
| 7.x and 8.x
|
|
|
| eDP via USB-C per tillim. No sound on Android 7.x. Sound does work on Android 8.x
|
|-
| ROCKPro64 PLAYBOX ENCLOSURE
| N/A
|
| N/A
|
| N/A
| Ventilation does not exist, thus requires manual changes to add venting. Case should be modified to account power adapter not being centered in cut holes. Opening the case once close without modifying it first is near impossible without special tools. Graphene heatsink is included and does well for Linux but not Android.
| https://pine64.com/?product=rockpro64-playbox-enclosure
|-
| ROCKPro64 30mm Tall Profile Heatsink
| N/A
|
| N/A
|
| N/A
|
| https://store.pine64.org/?product=rockpro64-heatsink
|-
| ROCKPro64 20mm Mid Profile Heatsink
| N/A
|
| N/A
|
| N/A
|
| https://pine64.com/?product=rockpro64-20mm-mid-profile-heatsink
|-
| Fan For ROCKPro64 20mm Mid Profile Heatsink
| N/A
|
| N/A
|
| N/A
| You might want to use fanctl to control the fan while keeping your CPU cool https://github.com/tuxd3v/fanctl
| https://pine64.com/?product=fan-for-rockpro64-20mm-mid-profile-heatsink
|-
| HDMI output 4K@60Hz
|
|
|
|
|
|
|
|-
| PCIe 2.1
|
|
|
|
|
|
|
|-
| Real Time Clock (RTC) battery backup
|
|
|
|
|
|
| https://store.pine64.org/?product=rtc-backup-battery-cr-battery
|-
| Boot from USB/PXE
|
|
|
|
|
|
|
|}

RockChip themselves have tables of supported features at 4.4 and mainline kernel versions [https://opensource.rock-chips.com/wiki_Status_Matrix in their wiki here.]

= Board Information, Schematics and Certifications =
* Board Dimensions: 133mm x 80mm x 19mm
* Input Power: +12V @3A/5A with 5.5mm/2.1mm Type M Barrel type DC connector
* [https://files.pine64.org/doc/rockpro64/rockpro64_v21-SCH.pdf ROCKPro64 Schematic v2.1 (Second Batch Production Release)]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-top.dxf ROCKPro64 v2.1 Board Top Outline in AutoCad DXF format]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-bottom.dxf ROCKPro64 v2.1 Board Bottom Outline in AutoCad DXF format]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-top.pdf ROCKPro64 v2.1 Board Top Outline in PDF format]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-bottom.pdf ROCKPro64 v2.1 Board Bottom Outline in PDF format]
* [https://files.pine64.org/doc/rockpro64/rockpro64_v20-SCH.pdf ROCKPro64 Schematic v2.0 (Pilot Production Release)]
** [https://files.pine64.org/doc/rockpro64/ROCKPRo64%20Engineering%20Change%20Notice%2020180628RP01.pdf Engineering Change Notice for v2.0 to turn on 3.3V power on PCIe]
* [https://files.pine64.org/doc/rockpro64/rockpro64_wifi_ap6359SA.pdf ROCKPro64 AP6359SA Wifi/BT Schematic]
* [https://files.pine64.org/doc/rockpro64/Rockpro64%20Pi-2%20Connector%20ver0.2.png ROCKPro64 Pi-2 Pin assignment and definition]
* [https://files.pine64.org/doc/rockpro64/RockPro-3D-model.zip ROCKPro64 3D model]

* Certifications:
** Disclaimer: Please note that PINE64 SBC is not a "final" product and in general certification is not necessary. However, PINE64 still submit the SBC for FCC, CE, and ROHS certification and obtain the certificates to proof that SBC board is capable on passing the testing. Please note a final commercial product needs to performs its owns testing and obtains its owns certificates.
** [https://files.pine64.org/doc/cert/ROCKPro64%20FCC%20SDOC%20Certificate.pdf ROCKPro64 FCC Certificate]
** [https://files.pine64.org/doc/cert/ROCKPro64%20CE-EMC%20Certificate.pdf ROCKPro64 CE Certificate]
** [https://files.pine64.org/doc/cert/ROCKPro64%20ROHS%20%20SEC180529404001E%20Report.pdf ROCK64 RoHS Report]

= Datasheets for Components and Peripherals =
* Rockchip RK3399 SoC information:
** [https://www.rock-chips.com/a/en/products/RK33_Series/2016/0419/758.html Rockchip RK3399 SoC Brief]
** [https://opensource.rock-chips.com/images/2/28/Rockchip_RK3399_Datasheet_V1.8-20180529.pdf Rockchip RK3399 Datasheet V1.8]
** [https://opensource.rock-chips.com/images/e/ee/Rockchip_RK3399TRM_V1.4_Part1-20170408.pdf Rockchip RK3399 Technical Reference Manual part 1]
** [https://files.pine64.org/doc/datasheet/rockpro64/RK808%20datasheet%20V0.8.pdf Rockchip RK808 Datasheet V0.8]
* LPDDR4 (200 Balls) SDRAM:
** [https://files.pine64.org/doc/datasheet/rockpro64/SM512M32Z01MD2BNP(200BALL).pdf Micron LPDDR4 Mobile LPDDR4 Datasheet]
* eMMC information:
** [https://files.pine64.org/doc/rock64/PINE64_eMMC_Module_20170719.pdf PINE64 eMMC module schematic]
** [https://files.pine64.org/doc/rock64/usb%20emmc%20module%20adapter%20v2.pdf PINE64 USB adapter for eMMC module V2 schematic]
** [https://files.pine64.org/doc/rock64/USB%20adapter%20for%20eMMC%20module%20PCB.tar PINE64 USB adapter for eMMC module PCB in JPEG]
** [https://files.pine64.org/doc/datasheet/pine64/E-00517%20FORESEE_eMMC_NCEMAM8B-16G%20SPEC.pdf 16GB Foresee eMMC Datasheet]
** [https://files.pine64.org/doc/datasheet/pine64/SDINADF4-16-128GB-H%20data%20sheet%20v1.13.pdf 32GB/64GB/128GB SanDisk eMMC Datasheet]
* SPI NOR Flash information:
** [https://files.pine64.org/doc/datasheet/pine64/w25q128jv%20spi%20revc%2011162016.pdf WinBond 128Mb SPI Flash Datasheet]
** [https://files.pine64.org/doc/datasheet/pine64/GD25Q128C-Rev2.5.pdf GigaDevice 128Mb SPI Flash Datasheet]
* Heatsink related info:
** [https://files.pine64.org/doc/datasheet/rockpro64/Rockpro%20Passive%20Heatsink%20Spec.jpg ROCKPro64 Passive Heatsink Dimension Drawing]
** [https://files.pine64.org/doc/datasheet/rockpro64/LMS-TC150%20Silicon%20Thermal%20Pad.pdf Heatsink Thermal Pad Specification]
* Wireless related info:
** [https://files.pine64.org/doc/datasheet/rockpro64/AP6256%20datasheet_V1.3_12202017.pdf AMPAK AP6256 11AC WiFi + Bluetooth5.0 Datasheet]]
* Ethernet related info:
** [https://files.pine64.org/doc/datasheet/rock64/RTL8211F-CG-Realtek.pdf Realtek RTL8211F 10/100/1000M Ethernet Transceiver Datasheet]
* Peripheral related info:
** [https://files.pine64.org/doc/datasheet/rockpro64/ASM1061_Data%20Sheet_R1_8.pdf asmedia ASM1061 PCIe SATA 2.0 Datasheet]
* Remote control button mapping
** [https://files.pine64.org/doc/Pine%20A64%20Schematic/remote-wit-logo.jpg Official Remote Control for the PINE64 Button Mapping]
* Audio Codec (ES8316) (Under Board)
** [https://everest-semi.com/pdf/ES8316%20PB.pdf Everest ES8316 Audio Codec]

= Useful articles and blog posts =

If you want to dive in to the ecosystem, here's a short list of various articles and blog posts that can help you set up your soft- or hardware development environment.

* [https://stikonas.eu/wordpress/2019/09/15/blobless-boot-with-rockpro64/ Blobless boot with RockPro64 by Andrius Štikonas]

* [https://marcin.juszkiewicz.com.pl/2020/06/17/ebbr-on-rockpro64/ EBBR on RockPro64 by Marcin Juszkiewicz]

= The NAS Case for the ROCKPro64 =
[[file:NASCaseMain.png|thumb|right|Front View of the PINE64 NAS Case for the ROCKPro64]]
Please [[NASCase | follow this this link]] for '''detailed instructions on how to assemble the ROCKPro64 NAS Case'''.

The NAS Case instructions also contains detailed information about:
*what the NAS Case ships with
*What additional things you need to purchase for your NAS Case
*What optional things you can consider purchasing for your NAS build
*What OS Image we recommend you use for your NAS build
*IO accessibility after installing the ROCKPro64 into the NAS Case
*[https://files.pine64.org/doc/rockpro64/ROCKPro64%20NAS%20Case%20Exploded%20View%20Diagram.pdf NAS Case Exploded View]
*[https://files.pine64.org/doc/rockpro64/NAS%20Case%20Drawing.dwg NAS Case Drawing]

= Other Resources =
* [https://forum.pine64.org/forumdisplay.php?fid=98 ROCKPro64 Forum]
* [https://pine64.com/?post_type=product Pine64 shop]
* [https://github.com/rockchip-linux Rockchip Linux GitHub Repo]
* [https://opensource.rock-chips.com/ Rockchip Open Source Wiki]
* ExplainingComputers have a video review [https://www.youtube.com/watch?v=CeoNHGFN_30 of the RockPro64 here, including linux first boot.]

[[Category:ROCKPro64]] [[Category:Rockchip RK3399]]

ROCKPro64

2021-05-09T01:23:46Z

AlephNull: Add schematic switch designators, list SW4 as a "connector" since it's a header, add CON16.

The [https://www.pine64.org/rockpro64/ '''ROCKPro64'''] is the most powerful Single Board Computer released by Pine64. It is powered by a Rockchip RK3399 Hexa-Core (dual ARM Cortex A72 and quad ARM Cortex A53) 64-Bit Processor with a MALI T-860 Quad-Core GPU.

Key features include a PCIe x4 open ended slot, the use of LPDDR4 RAM, and industry standard heatsink mounting holes.

The ROCKPro64 is equipped with 2GB or 4GB LPDDR4 system memory, and 128Mb SPI boot Flash. There is also an optional eMMC module (up to 128GB) and microSD slot for booting. The board is equipped with 1x USB 3.0 type C Host with DP 1.2, 1x USB 3.0 type A Host, 2x USB 2.0 Host, Gigabit Ethernet, PI-2 GPIO Bus, MiPi DSI interface, eDP interface, touch Panel interface, stereo MiPi CSI interface, as well as many other device interfaces such as UART, SPI, I2C, for makers to integrate with sensors and other peripherals. Many different Operating Systems (OS) are freely available from the open source community, such as Android, Linux (Ubuntu, Debian, Arch), and BSD.

= Board layout =
[[File:ROCKPro64_annotated.jpg]]

[[File:ROCKPro64v21FRONT.jpg|200px|thumb|right|A hi-res picture of v2.1 front]]

[[File:ROCKPro64v21REAR.jpg|200px|thumb|right|A hi-res picture of v2.1 rear]]

== Main chips ==
* RK3399 system-on-chip (1)
* LPDDR4 SDRAM 1 (18)
* LPDDR4 SDRAM 2 (3)
* SPI NOR flash memory (17)
* RK808 power management (near 19)
* RTL8211 ethernet transceiver (near 25)
* ES8316 Sound Codec (on rear of board)
* The heatsink mounting holes around the RK3399 are 59 mm apart

== Switches ==

The Power button (11, SW3): is the same as on your mobile phone - press and release after about 1 second to power on. Press and hold for about 3 seconds to power off.

The Reset button (10, SW901): perfoms a reset.

The Recover button (28, SW900): used to enter maskrom mode.

== Connectors, sockets and headers ==
{| class="wikitable sortable"
! Diagram !! Schematic designator || Silkscreen label !! Number of pins !! Description
|-
| style="text-align: center;" | 2 || U39 || PI-2-bus || style="text-align: center;" | 40 || Pi-2 bus
|-
| style="text-align: center;" | 4 || J8 || +FAN- || style="text-align: center;" | 2 || PWM controlled fan header
|-
| style="text-align: center;" | 5 || J10 || SPDIF || style="text-align: center;" | 3 || SPDIF header
|-
| style="text-align: center;" | 6 || U6 || +RTC- || style="text-align: center;" | 2 || RTC battery backup header
|-
| style="text-align: center;" | 7 || U31 || Wifi-BT || style="text-align: center;" | 16 || SDIO WIFI/BT module-MIMO 2
|-
| style="text-align: center;" | 8 || USB3 || || style="text-align: center;" | 9 || USB-3 and USB Type C
|-
| style="text-align: center;" | 9 || USB1 || || style="text-align: center;" | 2×4 || Dual USB-2
|-
| style="text-align: center;" | 12 || IR1 || IR || style="text-align: center;" | 3 || infrared receiver socket
|-
| style="text-align: center;" | 13 || J16 || Headphone+mic || style="text-align: center;" | 4 || Headphone + mic 3.5mm jack
|-
| style="text-align: center;" | - || CON16 || GND PWR RST GND || style="text-align: center;" | 4 || Power & reset, unpopulated header near Headphone jack
|-
| style="text-align: center;" | 14 || U29 || EMMC || style="text-align: center;" | 34 || eMMC connector
|-
| style="text-align: center;" | 14* || J13 || || style="text-align: center;" | 13 || TF-card, a.k.a. microSD (* under 14 on the bottom side)
|-
| style="text-align: center;" | 15 || U30 || || style="text-align: center;" | 14 || SDIO WIFI/BT module-MIMO 1
|-
| style="text-align: center;" | 16 || SW4 || || style="text-align: center;" | 2 || Jumper to [[#Disable eMMC]]
|-
| style="text-align: center;" | 19 || J15 || PCI || style="text-align: center;" | 64 || PCI-express X4 socket
|-
| style="text-align: center;" | 20 || J21 || DSI || style="text-align: center;" | 30 || DSI
|-
| style="text-align: center;" | 21 || J22 || EDP || style="text-align: center;" | 30 || LCD EDP
|-
| style="text-align: center;" | 22 || CON1 || TP || style="text-align: center;" | 6 || touch panel connector
|-
| style="text-align: center;" | 23 || CON15 || || style="text-align: center;" | 4 || DC out for SATA disk cable (direct connect from DC-IN)
|-
| style="text-align: center;" | 24 || J11 || DC-IN || style="text-align: center;" | 2 || Power input, positive tip; 12V/3A (minimum) recommended
|-
| style="text-align: center;" | 25 || U32 || || style="text-align: center;" | 8 || RJ45
|-
| style="text-align: center;" | 26 || J14 || || style="text-align: center;" | 19 || HDMI
|-
| style="text-align: center;" | 27 || J17 || MIPI CAM || style="text-align: center;" | 32 || MIPI-1
|-
| style="text-align: center;" | 29 || J19 || MIPI CAM || style="text-align: center;" | 32 || MIPI-2
|-
| style="text-align: center;" | 30 || J18 || CIF || style="text-align: center;" | 26 || CIF
|}

== LEDs ==

A green LED next to the 12V input barrel connector will light as long as there is 12V applied to the connector. (Even if the RockPro64 is powered off.)

A white LED behind the reset button will light as long as the RockPro64 is running (it comes on a few seconds after power on, when control is passed to the operating system.)

A red LED behind the reset button is DIY - it is lit for example if the board is in OTG mode with an Ayufan image, or if an Android image is in standby mode.

Yellow and green LEDs on the LAN socket behave in a standard way.

== Jumpers ==
They are used for boot device selection, as described in the following section.

=== Disable eMMC ===

There is an unlabelled (on the PCB silk-screen) 2-pin jumper (16) between the eMMC socket (14) and the SPI chip (17). It is designated as SW4 on the [[#Board Information, Schematics and Certifications | schematic diagram]]. The default condition is OPEN (no jumper). It is useful for controlling the boot as follows:

Default boot device (with no SPI software) is eMMC, then SDcard. If both the eMMC and the SDcard contain bootable images then the eMMC can be disabled by installing the jumper. This completely removes the eMMC from the resulting OS. If you wish the eMMC to be visible in the booted OS the jumper should be removed 2 seconds after applying power (and before the white LED comes on).

The possible combinations are summarised in the table below (1 = present, 0 = not present, S = boot from the µSD card, M = boot from the eMMC module, X = unsupported combination):

{| class="wikitable sortable" style="text-align: center;"
! µSD !! eMMC !! SW4 !! boot
|-
| 0 || 0 || 0 || X
|-
| 0 || 0 || 1 || X
|-
| 0 || 1 || 0 || M
|-
| 0 || 1 || 1 || X
|-
| 1 || 0 || 0 || S
|-
| 1 || 0 || 1 || S
|-
| 1 || 1 || 0 || M
|-
| 1 || 1 || 1 || S
|}

=== Disable SPI (while booting) ===
There is a second possibility to jumper your ROCKPro64: If you mess-up your SPI and are unable to boot, jumpering pins 23 (CLK) and 25 pin (GND) on the PI-2-bus header will disable the SPI as a boot device. (This was taken from the IRC logs, 09 August 2018 @ 17:23) You have to remove the jumper 2 seconds after having started your RP64 (before the white LED turns ON) otherwise the SPI will be missing and you won't be able to flash it.
Ayufan images contain (at the moment) only one script for the SPI and the RP64, it's "rockpro64_reset_spi_flash". Other SPI scripts are dedicated to the R64 (as it is written on the name) and it will mess-up your RP64 SPI if you use them.

= Getting Started =

This section gives important information to get the board up and running.

== Software and OS Image Builds ==

In the '[[ROCKPro64 Software Release]]' page you will find a complete list of currently supported Operating System images that work with the ROCKPro64 as well as other related software. The Software Release page has links to download the images as well as high level instructions how to load each image.

The list includes OS images and descriptions of:

[[ROCKPro64_Software_Release#Armbian|'''Armbian (microSD and eMMC Boot)''']]

[[ROCKPro64_Software_Release#Debian_by_mrfixit2001|'''Debian (microSD and eMMC Boot)''']]

[[ROCKPro64_Software_Release#DietPi|'''DietPi (microSD and eMMC Boot)''']]

[[ROCKPro64_Software_Release#OpenMediaVault|'''Open Media Vault (microSD and eMMC Boot)''']]

[[ROCKPro64_Software_Release#LibreELEC.28KODI.29|'''LibreELEC for KODI (microSD and eMMC Boot)''']]

[[ROCKPro64_Software_Release#Slackware|'''Slackware (microSD and eMMC Boot)''']]

[[ROCKPro64_Software_Release#Nems_Linux|'''Nagios Enterprise Monitoring Server (microSD and eMMC Boot)''']]

[[ROCKPro64_Software_Release#NextCloudPi|'''NextCloudPi (microSD and eMMC Boot)''']]

[[ROCKPro64_Software_Release#Cent_OS|'''Cent OS (microSD Boot)''']]

[[ROCKPro64_Software_Release#Manjaro_ARM|'''Manjaro ARM (microSD and eMMC Boot)''']]

[[ROCKPro64_Software_Release#OpenWrt|'''OpenWrt (microSD and eMMC Boot)''']]

Please see the [[NOOB]] page for detailed discussion of what you need (prerequisites) as well as instructions if the high level instructions are insufficient.

== More advanced Linux bits ==

Some Linux tips are given below.

=== How to update your Linux ===

For Debian/Ubuntu images entering the following commands at a terminal prompt

<code>sudo apt-get update</code> 
<code>sudo apt-get upgrade</code>

will keep your installation up to date. To update Ayufan images to the next release (when available) use the following command

<code>sudo apt-get dist-upgrade</code>

If you are happy to update your system to pre-releases of Ayufan images then modify /etc/apt/sources.list.d/ayufan-rock64.list as per the comment in that file.

The kernel in Ayufan releases is under active development and, if you wish to install a later version, then it is best to use a package manager. In synaptic (for example), if you search for package names linux-image-4.4 you should see your currently installed version(s) as well as any more recent ones. Similarly if you wish to install the mainline kernel then searching for linux-image-4.18 will show you what is available. '''At the time of writing (August 2018) there are significant features missing from the mainline kernel for aarch64 processors (e.g. HDMI sound).'''

=== Useful scripts ===
After you install an Ayufan image you will find some scripts in /usr/local/sbin/ and /usr/local/bin/ that may be useful. (Need to expand this section)

=== Video playback ===
Ayufan has some old documentation on [https://github.com/ayufan-rock64/linux-build/blob/master/recipes/video-playback.md video playback here.] For your ROCKPro64 the install should be

<code>sudo apt-get install ffmpeg mpv libmali-rk-midgard-t86x-r14p0-gbm</code>

(These modules are included in the Ayufan deskop releases.) At which stage rkmpv myvideo.mp4 will play a fullscreen, hardware assisted, version of your video. rkmpv is at /usr/local/bin/rkmpv

=== Swapping kernel versions ===
extlinux is in use on Ayufan images (at least) which enables some switching between installed kernel versions - [https://github.com/ayufan-rock64/linux-build/blob/master/recipes/extlinux.md intro documentation is here.] In particular after you install any additional kernels, you can edit your /boot/extlinux/extlinux.conf file to specify which of the kernels you have installed to use for the next boot.

From Ayufan version 0.7.11 the script /usr/local/sbin/change-default-kernel.sh does a nice little menu swap for you if you run it as root (sudo).

=== Using an NVMe disk for rootfs ===
Forum member Bullet64 has documented [https://forum.frank-mankel.org/topic/208/booten-von-der-nvme-platte how to move rootfs to an NVMe disk.] This is useful until we get a full SPI option to boot from the NVMe.

== More advanced bits related to any OS ==

This section gives some hints for advanced users.

=== Setup a serial console (UART)===
The early adopters (and late-comers who fiddle excessively with their boards!) have a need to monitor the low-level boot behaviour: this is done with a serial console and there [https://forum.pine64.org/showthread.php?tid=6387 is a great description how to get this working specifically for your ROCKPro64 here.]

=== Booting from USB or PXE ===

The default choice of boot device is first eMMC (if present) then SDcard. See [[ ROCKPro64_Main_Page#Disable_eMMC | jumpers above for details on adjusting this sequence.]]

It is possible to flash the SPI to extend the options for boot devices to USB drives or PXE. The preferred method is now the rock64_write_spi_flash.sh script (see [[ROCKPro64_Main_Page#Useful_scripts | useful scripts above.]]) The NOOB wiki page has more details [[NOOB#Flashing_u-boot_to_SPI_Flash | here.]]

Background info and historic details of this usage [https://github.com/ayufan-rock64/linux-build/blob/master/recipes/flash-spi.md can be found here.]

=== Boot sequence ===

The RockPro64 boot sequence has been documented [https://github.com/sigmaris/u-boot/wiki/RockPro64-boot-sequence here] by sigmaris.

=== OTG mode ===

You can boot your ROCKPro64 into OTG mode with the use of the Recover button (see [[ROCKPro64_Main_Page#Switches | switch 28 above.]]) Note there are 2 OTG ports on your ROCKPro64: the type-C USB 3 socket is definitely one. From the schematic it appears the USB 3 (type A) socket is the other, but this has yet to be confirmed.

The method is to power off the board. Then push and hold the Recover button and push and release the Power button.
* If you have an Ayufan bootable image in either the SDcard or eMMC then there are 4 OTG modes [https://github.com/ayufan-rock64/linux-u-boot/commit/ea6efecdfecc57c853a6f32f78469d1b2417329b described here] including Android fastboot, RockUSB and MaskROM modes. Releasing the Recover button as soon as the white LED lights counts as 1 blink. Keeping it pressed you will get 2 blinks of the white LED etc. Once the board enters OTG mode the red LED will be lit. In mode 1 the boot and linux-root partitions of the card with the Ayufan image (partitions 6 & 7 of a linux installation) are made available as devices. In all cases the USB device made available at the host has device ID 18d1:d00d.
* If you do not have an Ayufan image in either the SDcard or the eMMC, then neither white nor red LEDs will light, but the board will enter MaskROM mode where the USB device made available at the host has device ID 2207:330c.

=== NVMe drives ===
Please be aware that [https://pine64.com/product/rockpro64-pci-e-x4-to-m-2-ngff-nvme-ssd-interface-card the Pine64 SSD interface card] is intended for use with NVMe devices. These can be identified by the fact they have a single (Key M) notch, e.g. [https://www.wdc.com/content/dam/wdc/website/products/family/wd-black-pcie-ssd/wdfWDBlackSSD_PCIe_img1.jpg.imgw.500.500.jpg the WD Black devices.]

While M2/NGFF SATA devices (with a Key B notch, typically have Key M as well) will physically fit, they will not work. e.g. [https://www.wdc.com/content/dam/wdc/website/products/personal/internal_storage/wd_blue_3d_nand_sata_ssd/blue3d_product-overview.jpg.imgw.1000.1000.jpg WD Blue devices.]

=== SATA drives ===
SATA drives can be connected directly via the [https://pine64.com/?product=rockpro64-pci-e-to-dual-sata-ii-interface-card ROCKPro64 PCIe interface card.] Please note the card does not include the power cable - that is a [https://pine64.com/?product=rockpro64-power-cable-for-dual-sata-drives separate item.] Equally you must be aware that connecting SATA drives in this manner means they will be drawing power from your ROCKPro64 - please ensure you are using a 5A or better power supply.

ExplainingComputers did a YouTube [https://www.youtube.com/watch?v=9CCQicHwfDI ROCKPro64 PCIe SATA card review and tests using a Ubuntu console and OpenMediaVault.]

=== Wi-Fi & Bluetooth module ===
If you have bought the [https://pine64.com/product/rockpro64-1x1-dual-band-wifi-802-11ac-bluetooth-5-0-module Wi-Fi and Bluetooth module] from the Pine store then instructions for connecting it can be found on the accessories page [[ Accessories_Step_by_Step_Guides#Wifi.2FBluetooth_module | here.]] '''Please note that the 0.7.9 Ayufan's linux releases (August 2018) have deliberately DISABLED support for this module in the search for stability. It can be tested and used with the Android image.'''

It can also be used on Manjaro by installing ap6256-firmware and wireless-regdb packages.

=== 7" LCD Touch Screen ===
Instructions for connecting the [https://pine64.com/?product=7-lcd-touch-screen-panel LCD touch screen] from the Pine [[ Accessories_Step_by_Step_Guides#7.22_LCD_Touch_Screen_Panel | are here.]]

'''Note at present (August 2018) this screen is only supported by the Android image.'''

{{warning|1= When using the touchscreen ensure the cables are properly connected and tightened down and that you do not let the metal backplane touch the SBC}}

=== RTC battery backup ===
The Pine store has a couple of options for RTC battery backups: a [https://pine64.com/product/rtc-backup-battery-holder-2-x-aaa AAA version here] or a [https://pine64.com/product/rtc-backup-battery-holder-cr-2032 CR-2032 version here.] Instructions for plugging in either of them are also on the [[ Accessories_Step_by_Step_Guides| Accessories page ]]

=== Acryllic open enclosure ===
Assembly instructions for the [https://pine64.com/product/pine-a64-rockpro64-acrylic-open-enclosure acrylic enclosure] from the Pine store are also on the [[ Accessories_Step_by_Step_Guides| Accessories page ]]

=== NAS case ===
The [https://files.pine64.org/doc/rockpro64/ROCKPro64%20NAS%20Case%20Exploded%20View%20Diagram.pdf Exploded View Installation Diagram] for the [https://pine64.com/product/rockpro64-metal-desktop-nas-casing NAS case from the Pine store].

Detailed '''NAS Case overview and assembly instructions''' can be found [[NASCase | here]].

= [[ROCKPro64_Hardware_Accessory_Compatibility|Hardware Compatibility]] =
== Hardware Compatibility Page ==
Please contribute to the hardware compatibility page, which lists hardware which has been tested with the rockpro64, whether successful or not.

* [[ROCKPro64_Hardware_Accessory_Compatibility#PCIe devices|PCIe devices]]
* [[ROCKPro64_Hardware_Accessory_Compatibility#NVMe_SSD_drives|NVMe SSD drives]]
* [[ROCKPro64_Hardware_Accessory_Compatibility#USB_hardware|USB hardware]]
* [[ROCKPro64_Hardware_Accessory_Compatibility#USB_C_alternate_mode_DP|USB C alternate mode DP]]
* [[ROCKPro64_Hardware_Accessory_Compatibility#Other_hardware|Other hardware]]

== Limitations ==
=== PCIe card issue and/or asynchronous external abort on flash read/write ===
==== Older firmware overwrites actively used memory ====
Some people get system freeze when:
* use SATA disk with ROCKPro64 PCIe card. (maybe on newer PCIe card ASM1062 vs ASM1061)
* or do read or write 4GB to the flash. (not using PCIe)

If you connect the serial console you will see a Linux kernel oops: (a)synchronous external abort.

Both issues are in fact the same software BUG. There is no hardware problem.
Currently most OS do use uboot with a rockpro blob FW which use memory that Linux kernel is not aware of.
People are currently fixing this BUG, but it may take some time.
In the mean time, you can fix it manually.

The latest u-boot can boot the rockpro64 without any blobs from rockchip. Install first arm-none-eabi-gcc and aarch64-linux-gnu-gcc compiler, then run the following commands:

git clone https://github.com/ARM-software/arm-trusted-firmware.git atf
make -C atf CROSS_COMPILE=aarch64-linux-gnu- PLAT=rk3399 bl31
git clone https://gitlab.denx.de/u-boot/u-boot.git u-boot
cd u-boot/
git checkout v2020.01-rc5
make rockpro64-rk3399_defconfig
BL31=../atf/build/rk3399/release/bl31/bl31.elf make ARCH=arm CROSS_COMPILE=aarch64-linux-gnu-

Which gives you idbloader.img and u-boot.itb. Copy them to the rockpro64, and run the following: (Or put your SD card into your PC)

sudo dd if=idbloader.img of=/dev/mmcblk0 seek=64
sudo dd if=u-boot.itb of=/dev/mmcblk0 seek=16384
sync

==== PCIe controller hardware error handling bug ====
There is an issue with the rk3399 pcie controller that is currently unmitigated:
*[https://lore.kernel.org/linux-pci/CAMdYz...gmail.com/ LKML Original Thread]
*[https://lkml.org/lkml/2020/4/6/320 LKML Additional Information]

The rk3399 pcie controller throws either a synchronous abort or a SError when a pcie device sends an unknown message.

The error type is determined by which cpu cluster handles the message.

=== Virtualization ===
The PCIe controller on the rk3399 is not behind an IOMMU.
This means it is not possible to safely pass through PCIe devices to a virtual machine.

= Board Features =

This section outlines the most important characteristics of the board and its components.

== SoC and Memory Specification ==
* Based on Rockchip RK3399
[[File:Rockchip_RK3399.png|right]]

=== CPU Architecture ===
* [https://developer.arm.com/products/processors/cortex-a/cortex-a72 Dual-core Cortex-A72 up to 2.0GHz CPU]
* [https://developer.arm.com/products/processors/cortex-a/cortex-a53 Quad-core Cortex-A53 up to 1.5GHz CPU]
* big.LITTLE architecture: Dual Cortex-A72 + Quad Cortex-A53, 64-bit CPU
* Cortex-A72:
** 1-4x Symmetrical Multiprocessing (SMP) within a single processor cluster, and multiple coherent SMP processor clusters through AMBA 5 CHI or AMBA 4 ACE technology
** AArch64 for 64-bit support and new architectural features
** L1 cache 48KB Icache and 32KB Dcache for each A72
** L2 cache 1024KB for big cluster
** DSP & SIMD extensions
** VFPv4 floating point
** Hardware virtualization support
* Cortex-A53:
** L1 cache 32KB Icache and 32KB Dcache for each A53
** L2 cache 512KB for little cluster
* Full implementation of the ARM architecture v8-A instruction set
* ARM Neon Advanced SIMD (single instruction, multiple data) support for accelerated media and signal processing computation
* ARMv8 Cryptography Extensions
* In-order pipeline with symmetric dual-issue of most instructions
* Include VFP v3 hardware to support single and double-precision operations
* TrustZone technology support
* Full CoreSight debug solution
* One isolated voltage domain to support DVFS

=== GPU Architecture ===
* [https://developer.arm.com/products/graphics-and-multimedia/mali-gpus/mali-t860-and-mali-t880-gpus ARM Mali-T860MP4 Quad-core GPU]
* The highest performance GPUs built on Arm Mali’s famous Midgard architecture, the Mali-T860 GPU is designed for complex graphics use cases and provide stunning visuals for UHD content.
* Frequency 650MHz
* Throughput 1300Mtri/s, 10.4Gpix/s
* OpenGL® ES 1.1, 1.2, 2.0, 3.1, 3.2., Vulkan 1.0*., OpenCL™ 1.1, 1.2., DirectX® 11 FL11_1., RenderScript™.

=== System Memory ===
* LPDDR4 RAM Memory Variants: Dual Channels 2GB and 4GB.
* Storage Memory: 128Mb built-in SPI Flash memory (as at August 2018 only support for USB boot).

== Display ==
* Dual VOP: one supports 4096x2160 with AFBC supported；The other supports 2560x1600
* Dual channel MIPI-DSI (4 lanes per channel)
* eDP 1.3 (4 lanes with 10.8Gbps) to support display, with PSR
* Digital Video port up to 4Kp60
* DisplayPort 1.2 (4 lanes, up to 4K 60Hz)
* Supports Rec.2020 and conversion to Rec.709

== Video ==
* Digital Video output up to 4K@60Hz
* 4K HDR @ 30fps
* H.264/AVC Base/Main/High/High10 profile @ level 5.1; up to 4Kx2K @ 60fps
* H.265/HEVC Main/Main10 profile @ level 5.1 High-tier; up to 4Kx2K @ 60fps
* VP9, up to 4Kx2K @ 60fps
* MPEG-1, ISO/IEC 11172-2, up to 1080P @ 60fps
* MPEG-2, ISO/IEC 13818-2, SP@ML, MP@HL, up to 1080P @ 60fps
* MPEG-4, ISO/IEC 14496-2, SP@L0-3, ASP@L0-5, up to 1080P @ 60fps
* VC-1, SP@ML, MP@HL, AP@L0-3, up to 1080P @ 60fps
* MVC is supported based on H.264 or H.265, up to 1080P @ 60fps

== Audio ==
* 3.5mm Phone Jack
* 3-pin S/PDIF header
* Audio via Digital Video port

== Camera ==
* Dual mipi CSI，dual ISP,Maximum input resolution of 13M pixels

== Network ==
* 10/100/1000Mbps Ethernet
* Wi-Fi 802.11 ac/a/b/g/n with Bluetooth 4.01 (old version with 2x2) / Bluetooth 5 (new version with 1x1) (optional)

== Storage ==
* microSD - bootable, support SDHC and SDXC, storage up to 256GB
* eMMC - bootable (optional eMMC Module)
* 1 USB3.0 Host port
* 1 USB type C OTG port with DP output
* 2 USB2.0 Dedicated Host ports

== Expansion Ports ==
* 2x20 pins "Pi2" GPIO Header
* PCIe 2.1 (4 full-duplex lanes with 20Gbps) x4 open ended port

== Working Features ==
{| class="wikitable sortable"
! style="font-weight:bold;" | Feature/Option
! style="font-weight:bold;" | Android
! style="font-weight:bold;" | Android Version
! style="font-weight:bold;" | Linux
! style="font-weight:bold;" | Linux Version
! style="font-weight:bold;" | Test/Verify Steps
! style="font-weight:bold;" | Notes
! style="font-weight:bold;" | Product Link
|-
| Pine64 LCD Touchscreen (Screen/Touch)
| Yes/Yes
|
| No/No
|
|
| Maybe this will help get this working? https://github.com/avafinger/pine64-touchscreen
| https://pine64.com/?product=7-lcd-touch-screen-panel
|-
| ROCKPro64 2×2 MIMO Dual Band WIFI 802.11AC / BLUETOOTH 4.2 MODULE (old)
ROCKPro64 1x1 Dual Band WIFI 802.11AC / BLUETOOTH 5.0 MODULE (new)
| Yes/Yes
|
| No/No
|
|
| In 0.7.9 Ayufan linux releases this is deliberately disabled for stability reasons.
| https://store.pine64.org/product/rockpro64-1x1-dual-band-wifi-802-11acbluetooth-5-0-module
|-
| USB OTG
|
|
|
|
| use this script: https://github.com/ayufan-rock64/linux-package/blob/master/root-rockpro64/usr/local/sbin/rockpro64_enable_otg.sh then configure ip on usb0: ifconfig usb0 169.169.222.222 and run iperf, you should likely see about 200-300MB/s
| https://wiki.pine64.org/index.php/ROCKPro64_Main_Page#OTG_mode
|
|-
| USB Mass Storage USB2/USB3
| Yes/yes
|
| Yes/Yes
|
|
|
|
|-
| Dedicated Fan Power (pwm1)
|
|
| Yes
|
|
| You might want to use ATS. https://github.com/tuxd3v/ats
|
|-
| GPIO pins (raw or via RPI python scripts)
|
|
|
|
|
| Check out what Frank Mankel has done. https://forum.frank-mankel.org/topic/292/rockpro64-rp64-gpio/2
|
|-
| MIPI CSI Camera 1 and 2
|
|
|
|
|
|
|
|-
| eDP
|
|
|
|
|
|
|
|-
| HDMI Audio
| Yes
| 7.1.2
| Yes
| 4.4.132-1083 - 4.4.138-1100
|
| Stopped working in 4.4.154.1105. Ayufan is looking into it.
|
|-
| 3.5mm Audio/Mic
|
|
|
|
|
|
|
|-
| USB-C Host
|
|
|
|
|
|
|
|-
| Display via USB-C
| Yes
| 7.x and 8.x
|
|
|
| eDP via USB-C per tillim. No sound on Android 7.x. Sound does work on Android 8.x
|
|-
| ROCKPro64 PLAYBOX ENCLOSURE
| N/A
|
| N/A
|
| N/A
| Ventilation does not exist, thus requires manual changes to add venting. Case should be modified to account power adapter not being centered in cut holes. Opening the case once close without modifying it first is near impossible without special tools. Graphene heatsink is included and does well for Linux but not Android.
| https://pine64.com/?product=rockpro64-playbox-enclosure
|-
| ROCKPro64 30mm Tall Profile Heatsink
| N/A
|
| N/A
|
| N/A
|
| https://store.pine64.org/?product=rockpro64-heatsink
|-
| ROCKPro64 20mm Mid Profile Heatsink
| N/A
|
| N/A
|
| N/A
|
| https://pine64.com/?product=rockpro64-20mm-mid-profile-heatsink
|-
| Fan For ROCKPro64 20mm Mid Profile Heatsink
| N/A
|
| N/A
|
| N/A
| You might want to use fanctl to control the fan while keeping your CPU cool https://github.com/tuxd3v/fanctl
| https://pine64.com/?product=fan-for-rockpro64-20mm-mid-profile-heatsink
|-
| HDMI output 4K@60Hz
|
|
|
|
|
|
|
|-
| PCIe 2.1
|
|
|
|
|
|
|
|-
| Real Time Clock (RTC) battery backup
|
|
|
|
|
|
| https://store.pine64.org/?product=rtc-backup-battery-cr-battery
|-
| Boot from USB/PXE
|
|
|
|
|
|
|
|}

RockChip themselves have tables of supported features at 4.4 and mainline kernel versions [https://opensource.rock-chips.com/wiki_Status_Matrix in their wiki here.]

= Board Information, Schematics and Certifications =
* Board Dimensions: 133mm x 80mm x 19mm
* Input Power: +12V @3A/5A with 5.5mm/2.1mm Type M Barrel type DC connector
* [https://files.pine64.org/doc/rockpro64/rockpro64_v21-SCH.pdf ROCKPro64 Schematic v2.1 (Second Batch Production Release)]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-top.dxf ROCKPro64 v2.1 Board Top Outline in AutoCad DXF format]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-bottom.dxf ROCKPro64 v2.1 Board Bottom Outline in AutoCad DXF format]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-top.pdf ROCKPro64 v2.1 Board Top Outline in PDF format]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-bottom.pdf ROCKPro64 v2.1 Board Bottom Outline in PDF format]
* [https://files.pine64.org/doc/rockpro64/rockpro64_v20-SCH.pdf ROCKPro64 Schematic v2.0 (Pilot Production Release)]
** [https://files.pine64.org/doc/rockpro64/ROCKPRo64%20Engineering%20Change%20Notice%2020180628RP01.pdf Engineering Change Notice for v2.0 to turn on 3.3V power on PCIe]
* [https://files.pine64.org/doc/rockpro64/rockpro64_wifi_ap6359SA.pdf ROCKPro64 AP6359SA Wifi/BT Schematic]
* [https://files.pine64.org/doc/rockpro64/Rockpro64%20Pi-2%20Connector%20ver0.2.png ROCKPro64 Pi-2 Pin assignment and definition]
* [https://files.pine64.org/doc/rockpro64/RockPro-3D-model.zip ROCKPro64 3D model]

* Certifications:
** Disclaimer: Please note that PINE64 SBC is not a "final" product and in general certification is not necessary. However, PINE64 still submit the SBC for FCC, CE, and ROHS certification and obtain the certificates to proof that SBC board is capable on passing the testing. Please note a final commercial product needs to performs its owns testing and obtains its owns certificates.
** [https://files.pine64.org/doc/cert/ROCKPro64%20FCC%20SDOC%20Certificate.pdf ROCKPro64 FCC Certificate]
** [https://files.pine64.org/doc/cert/ROCKPro64%20CE-EMC%20Certificate.pdf ROCKPro64 CE Certificate]
** [https://files.pine64.org/doc/cert/ROCKPro64%20ROHS%20%20SEC180529404001E%20Report.pdf ROCK64 RoHS Report]

= Datasheets for Components and Peripherals =
* Rockchip RK3399 SoC information:
** [https://www.rock-chips.com/a/en/products/RK33_Series/2016/0419/758.html Rockchip RK3399 SoC Brief]
** [https://opensource.rock-chips.com/images/2/28/Rockchip_RK3399_Datasheet_V1.8-20180529.pdf Rockchip RK3399 Datasheet V1.8]
** [https://opensource.rock-chips.com/images/e/ee/Rockchip_RK3399TRM_V1.4_Part1-20170408.pdf Rockchip RK3399 Technical Reference Manual part 1]
** [https://files.pine64.org/doc/datasheet/rockpro64/RK808%20datasheet%20V0.8.pdf Rockchip RK808 Datasheet V0.8]
* LPDDR4 (200 Balls) SDRAM:
** [https://files.pine64.org/doc/datasheet/rockpro64/SM512M32Z01MD2BNP(200BALL).pdf Micron LPDDR4 Mobile LPDDR4 Datasheet]
* eMMC information:
** [https://files.pine64.org/doc/rock64/PINE64_eMMC_Module_20170719.pdf PINE64 eMMC module schematic]
** [https://files.pine64.org/doc/rock64/usb%20emmc%20module%20adapter%20v2.pdf PINE64 USB adapter for eMMC module V2 schematic]
** [https://files.pine64.org/doc/rock64/USB%20adapter%20for%20eMMC%20module%20PCB.tar PINE64 USB adapter for eMMC module PCB in JPEG]
** [https://files.pine64.org/doc/datasheet/pine64/E-00517%20FORESEE_eMMC_NCEMAM8B-16G%20SPEC.pdf 16GB Foresee eMMC Datasheet]
** [https://files.pine64.org/doc/datasheet/pine64/SDINADF4-16-128GB-H%20data%20sheet%20v1.13.pdf 32GB/64GB/128GB SanDisk eMMC Datasheet]
* SPI NOR Flash information:
** [https://files.pine64.org/doc/datasheet/pine64/w25q128jv%20spi%20revc%2011162016.pdf WinBond 128Mb SPI Flash Datasheet]
** [https://files.pine64.org/doc/datasheet/pine64/GD25Q128C-Rev2.5.pdf GigaDevice 128Mb SPI Flash Datasheet]
* Heatsink related info:
** [https://files.pine64.org/doc/datasheet/rockpro64/Rockpro%20Passive%20Heatsink%20Spec.jpg ROCKPro64 Passive Heatsink Dimension Drawing]
** [https://files.pine64.org/doc/datasheet/rockpro64/LMS-TC150%20Silicon%20Thermal%20Pad.pdf Heatsink Thermal Pad Specification]
* Wireless related info:
** [https://files.pine64.org/doc/datasheet/rockpro64/AP6256%20datasheet_V1.3_12202017.pdf AMPAK AP6256 11AC WiFi + Bluetooth5.0 Datasheet]]
* Ethernet related info:
** [https://files.pine64.org/doc/datasheet/rock64/RTL8211F-CG-Realtek.pdf Realtek RTL8211F 10/100/1000M Ethernet Transceiver Datasheet]
* Peripheral related info:
** [https://files.pine64.org/doc/datasheet/rockpro64/ASM1061_Data%20Sheet_R1_8.pdf asmedia ASM1061 PCIe SATA 2.0 Datasheet]
* Remote control button mapping
** [https://files.pine64.org/doc/Pine%20A64%20Schematic/remote-wit-logo.jpg Official Remote Control for the PINE64 Button Mapping]
* Audio Codec (ES8316) (Under Board)
** [https://everest-semi.com/pdf/ES8316%20PB.pdf Everest ES8316 Audio Codec]

= Useful articles and blog posts =

If you want to dive in to the ecosystem, here's a short list of various articles and blog posts that can help you set up your soft- or hardware development environment.

* [https://stikonas.eu/wordpress/2019/09/15/blobless-boot-with-rockpro64/ Blobless boot with RockPro64 by Andrius Štikonas]

* [https://marcin.juszkiewicz.com.pl/2020/06/17/ebbr-on-rockpro64/ EBBR on RockPro64 by Marcin Juszkiewicz]

= The NAS Case for the ROCKPro64 =
[[file:NASCaseMain.png|thumb|right|Front View of the PINE64 NAS Case for the ROCKPro64]]
Please [[NASCase | follow this this link]] for '''detailed instructions on how to assemble the ROCKPro64 NAS Case'''.

The NAS Case instructions also contains detailed information about:
*what the NAS Case ships with
*What additional things you need to purchase for your NAS Case
*What optional things you can consider purchasing for your NAS build
*What OS Image we recommend you use for your NAS build
*IO accessibility after installing the ROCKPro64 into the NAS Case
*[https://files.pine64.org/doc/rockpro64/ROCKPro64%20NAS%20Case%20Exploded%20View%20Diagram.pdf NAS Case Exploded View]
*[https://files.pine64.org/doc/rockpro64/NAS%20Case%20Drawing.dwg NAS Case Drawing]

= Other Resources =
* [https://forum.pine64.org/forumdisplay.php?fid=98 ROCKPro64 Forum]
* [https://pine64.com/?post_type=product Pine64 shop]
* [https://github.com/rockchip-linux Rockchip Linux GitHub Repo]
* [https://opensource.rock-chips.com/ Rockchip Open Source Wiki]
* ExplainingComputers have a video review [https://www.youtube.com/watch?v=CeoNHGFN_30 of the RockPro64 here, including linux first boot.]

[[Category:ROCKPro64]] [[Category:Rockchip RK3399]]

NAS Case

2021-03-08T09:44:54Z

AlephNull: Clarify that currently shipping heatsinks may not include both thermal paste and a pad. Clarify that current SATA adapters may not include eSATA ports.

The PINE64 NAS Case is intended for either a Network Attached Storage (NAS) or Desktop application, but it can also be used in a number of other server capacities. It is built from precision-cut and powder-coated aluminum.

An exploded view of the NAS Case, illustrating how all the components come together, can be found [http://files.pine64.org/doc/rockpro64/ROCKPro64%20NAS%20Case%20Exploded%20View%20Diagram.pdf here]. Please refer back to this PDF document during assembly to verify correct orientation of individual components.
[[file:NASCaseMain.png|400px|thumb|right|Front View of the PINE64 NAS Case for the ROCKPro64]]

==What does the NAS Case house?==
[[File:NAS_Case_internals.jpg|200px|thumb|left|Internal Layout of the NAS Case]]

The NAS Case can house the following components:
*A ROCKPro64 Single Board Computer (SBC) with a tall, mid-size or slim/ no heatsink
*A PCIe to dual SATA adapter or a different low-profile PCIe card, e.g. an NVMe adapter
*Either two 3.5” OR two 2.5” HDDs / SSDs; combination of any two sized drives is accepted
*A 80mm fan with a Ph 2-Pin connector
*Up to three SMA antennas, two of which can be attached to the WiFi/ BT module

==What comes in the box?==
When you purchase the NAS Case from the PINE store the following items are shipped to you:
*The NAS Case itself, which consists of a top and a bottom half as well as an internal HDD SSD mount.
*Two SATA cables
*A custom power cable capable of powering two 2.5” or 3.5” HDDs /SSDs
*The required screws, fittings and a LED relay

==What other bare-minimum things do I need for a NAS build?==
[[File:PCIetoSATA.png|200px|thumb|right|You will need the PCIe to SATA adapter from the PINE64 store to connect your disks to your ROCKPro64 board]]
To assemble a functional NAS in the NAS Case you will require a number of additional parts.
With the exception of HDDs/SSDs, everything you need for a complete build can be purchased from the PINE store:
*A ROCKPro64 2GB or 4GB board
*A 12V 5A power supply
*A PCIe to dual SATA adapter
*One or two 2.5”/ 3.5” HDDs (not sold in the PINE store).
*A class 10 micro SD card

You can purchase all the aforementioned items in the [https://www.pine64.org/?post_type=product PINE64 store]

==What other things should I consider buying for a NAS build in the NAS Case?==
There are a few other things which you may wish to consider purchasing for your NAS. These peripherals, while not necessary from an operational standpoint, may contribute to the longevity and stability of your NAS’ operation OR expand it with additional functionality:
* An eMMC module
* An eMMC to USB 2.0 adapter
* A tall heatsink (N.B. Any of the three available heatsinks will fit in the NAS Case)
* An 80mm fan
* The WiFi / BT module

==Which software should I use?==
[[File:OMVGUI.png|200px|thumb|left|The OMV WebGUI is easy to understand but also very robust. It offers easy installation of plugins, system administration and overview of available services]]
If you are intending to build a home or small company NAS, then we strongly recommend you use [http://wiki.pine64.org/index.php/ROCKPro64_Software_Release#OpenMediaVault Open Media Vault (OMV)]. OMV is an open source NAS solution that makes setting up user accounts, network shares and services a breeze. It also simplifies installing additional features (called plugins), such as: PLEX media server; Remote Desktop; Encryption; RSync; etc.

Its worth noting that Nextcloud, or other similar Cloud storage solutions, can also be easily installed alongside the OMV OS Image.

Administration and monitoring of OMV is done via an advanced WebGUI, which also allows for updating and upgrading the ROCKPro64.
To learn more about OMV please visit [https://www.openmediavault.org/ their website].

To download the latest OMV build OR one of the numerous available Linux Distribution OS Images please visit the [https://wiki.pine64.org/index.php/ROCKPro64_Software_Release ROCKPro64 OS download section].

==Step-by-Step Assembly Instructions==

If you prefer a video tutorial or just want an overview of the process before you start [http://www.youtube.com/watch?v=_UeeklKo0Og check out this instructional video].

===Step 1. Preparation of the NAS Case for Installation===
Remove the top of the NAS Case. It is held together by two screws on either side with the exception of the bottom (left, right, top and back). Once done, the top of the case should lift right off without any resistance.

The next step is to remove the HDD/SSD holding bracket, which is screwed into the bottom of the case. Flip the bottom over and undo the screws which hold the bracket in place.

You should now be left with a bare case ready for installation of the necessary components.

===Step 2. Installing the ROCKPro64 into the NAS Case===
[[File:ROCKPro64inNASCase.jpg|300px|thumb|right|Correct Placement of the ROCKPro64 in the empty case, with Ethernet; Power; and HDMI at the back of the NAS Case]]
[[File:FrontIO.png|300px|thumb|left|Front IO with IR and LED relay installed]]
Make sure nothing is plugged into your ROCKPro64 - including a micro SD card.
If you intend to use a heatsink with your board then please install it now before proceeding. If you bought the heatsink from the Pine64 store it comes with thermal paste and/or a thermal pad. You can use one or the other (not both!). The thermal pad is easier to apply but the thermal paste should be better at cooling if properly applied.

Place your ROCKPro64 into the case with USB 2.0 and 3.0/C ports facing the front of the case. It should fit snugly and align with the port cut-outs in the case. Do not attempt at installing the board at an angle; insert it while holding it level and lowering it into the case.

Secure the board with 4x screws included in the see-through bag. Make sure that the board is held firmly in the case but do not overtighten the screws.

In the see-through bag you will also find a small semi-opaque plastic cylinder. This is the LED light lead and it should be installed from the outside of the case into the hole right over the reset (RST) switch. Simply press it into the hole until it sits tight.

If you wish to install an IRx receiver into your case then you should also place it into the IR socket at this stage. It should align with the cutout right above the power (PWR) switch.

===Step 3 PCIe to SATA adapter and Cabling===
[[File:DC_Location.jpg|200px|thumb|left|DC header on the ROCKPro64 for the power cable]]
[[File:PCIeFittedSATAsockets.png|200px|thumb|right|PCIe to SATA installed. Note the SATA connection orientation]]
With the board in place it's time to set up the PCIe to SATA adapter and do the cabling necessary to attach HDDs / SSDs.

Place the SATA Adapter into the PCIe slot on the ROCKPro64 board so that the holding bracket of the adapter faces the back of the case. In the back of the case there is a cutout for the PCIe adapter; some
variants of the PCIe dual SATA adapter can be configured for eSATA if need be, and the eSATA ports are accessible in the back of the case. By default, the internal SATA connectors are active on the adapter.

Secure the PCIe dual SATA Adapter with a single screw at the top of the bracket, in the back of the NAS Case.

This is the right time to plug in the SATA and custom power cable. The SATA cables plug into the ports on the top or front of the adapter while the power cable plugs into DC header located on the board - just below the power jack, to the left of the Ethernet port (when viewed from front).

Have the cables hang outside the case or to the side for now so that they do not get in the way until they are needed.

===Step 4. Installing HDDs / SSDs into the Holding Bracket===
[[File:Bracket_Orientation.png|300px|thumb|left|Bracket Orientation in the NAS Case]]
The next step is to install HDDs/ SSDs into their holding bracket; 2.5” drives need to be installed at the very bottom of the bracket while 3.5” drives are at the top of the the bracket.

For 2.5” drives make sure that the drives are oriented up and their SATA and power ports face the front of the NAS Case.

For 3.5” HDDs, make sure they are oriented up and their SATA and power ports face the right side of the NAS Case (towards the fan mounting location).

Each drive you mount in the holding bracket requires 4x screws which come supplied in the see-through bag. Make sure the drives are held in place firmly but do not over-tighten the screws.

Once the holding bracket is assembled and you have your drives mounted, please set it aside and proceed to the next step.

===Step 5. Installing Extras (eMMC; WiFi BT module + SMA Antennas; 80mm Fan)===
[[File:80mmfan.png|200px|thumb|right|The 80mm fan is a worthwhile addition to the NAS Case build]]
If you have additional peripherals, such as an eMMC or WiFi/BT module as well as the 80mm fan, then now is the right time to install them. If you have '''none of the above''', please '''proceed to step 6''' of this guide.

The eMMC and WiFi/BT modules are fitted into their respective placements on the ROCKPro64 board - please consult the diagram for their correct installation.

If you intend to use external u.FL to SMA antennas in the NAS Case then this is also the time to install them into the case. In the back section of the case at the very top you will find three cut-outs where the SMA antennas can be fitted. Don’t plug the u.FL leads antenna leads into the WiFi/BT module just yet - instead wait until after the disk holding bracket is installed into the case (step 6).

The fan should be mounted on the right-hand side of the case. We suggest that the fan is oriented for negative pressure, blowing air out of the case rather than taking air in. For best cable management results, have the fan power lead face the front of the case so that it can easily be routed to its header located next to GPIO pins on the ROCKPro64.
The fan should be secured using 4x long screws (that fasten into bolts) which can be found in the see-through bag supplied with the NAS Case.
Plug in the fan at this stage of the installation and route the cable at the bottom of the front of the case.

===Step 6. Installing the HDD / SSD Bracket and Routing Cables===
[[File:NASCAsewithdrives.jpg|300px|thumb|right|Complete assembly of the NAS Case]]
[[File:TopViewAssembly.png|300px|thumb|right|Top view of a complete NAS Case Assembly]]
Installing the HDD/SSD bracket into the case and wiring it up is the last step before closing up the case.

Place the bracket with the disks installed (from step 4) into the case. The bracket should line up with the guiding bolts and screw holes at the bottom of the case. The section of the bracket that holds 3.5” HDDs needs to face the left side of the case (when viewed from front) and should overhang the ROCKPro64 board slightly. The 3.5” SATA and power ports should face the right side of the case - where the fan mounts, while 2.5” SATA and power ports should face the front of the case.

With the bracket aligned, flip the bottom of the case over while holding the bracket in place. Screw it into place using 4x Phillips head screws that came included with the NAS Case.

The last thing remaining before the NAS Case can be screwed shut is routing SATA and power cables:
For 3.5” HDDs we suggest routing power and SATA cables underneath the drives, where 2.5” HDDs/SSDs would otherwise reside.

For 2.5” disks you have plenty of routing options as there is much space available. The most obvious route is straight over the disks, where the 3.5” HDDs would reside.

===Step 7. Closing the NAS Case and Powering On your NAS===

Almost there. All that's left to do is to screw together the NAS Case. Screw in the top front screws first followed by screws on either side of the case. Do the back screws last. There, you are done.

To power on your new NAS Case and HDDs all you need to do is to plug in power and Ethernet (This is obviously assuming that you are intending to use it as a NAS or a headless server).

==IO accessibility when the NAS Case is assembled==

When the NAS Case is assembled and screwed shut these ROCKPro64 IO ports remain accessible:
* Micro SD slot
* USB 2.0
* USB 3.0 and USB type C
* Power and Reset switches
* The headphone and microphone jack
* Gigabit Ethernet port
* HDMI

[[Category:ROCKPro64]]

User:AlephNull

2021-01-23T00:16:23Z

AlephNull: Created page with "I'm a FreeBSD developer/committer with an interest in ARM and RISC-V. I am interested in improving FreeBSD support for Pine64 devices."

I'm a FreeBSD developer/committer with an interest in ARM and RISC-V. I am interested in improving FreeBSD support for Pine64 devices.