Welcome, Guest
You have to register before you can post on our site.

Username
  

Password
  





Search Forums



(Advanced Search)

Forum Statistics
» Members: 29,679
» Latest member: Gett1272
» Forum threads: 16,253
» Forum posts: 117,171

Full Statistics

Latest Threads
Are you interested in a n...
Forum: General Discussion on Pinebook Pro
Last Post: WEF
Yesterday, 02:33 PM
» Replies: 2
» Views: 2,975
Recycling pinephone as ho...
Forum: PinePhone Hardware
Last Post: biketool
Yesterday, 11:18 AM
» Replies: 3
» Views: 305
BT PAN - we need iptables...
Forum: Mobian on PinePhone
Last Post: biketool
Yesterday, 07:29 AM
» Replies: 0
» Views: 68
black cursos background
Forum: General Discussion on PineTab
Last Post: polrus
11-11-2025, 04:07 PM
» Replies: 0
» Views: 57
slight bumps causing phon...
Forum: PinePhone Pro Hardware
Last Post: JadenSki
11-11-2025, 02:05 PM
» Replies: 2
» Views: 112
Star64 Irradium (based on...
Forum: Getting Started
Last Post: mara
11-11-2025, 02:01 PM
» Replies: 10
» Views: 12,487
Switching cameras on PPpr...
Forum: Mobian on PinePhone
Last Post: biketool
11-11-2025, 10:44 AM
» Replies: 0
» Views: 53
Battery connector dead
Forum: PinePhone Hardware
Last Post: mdk
11-11-2025, 10:05 AM
» Replies: 3
» Views: 2,375
No touch KB after update(...
Forum: Mobian on PinePhone
Last Post: biketool
11-11-2025, 09:45 AM
» Replies: 3
» Views: 189
compass pdf link expired:...
Forum: General Discussion on PinePhone
Last Post: WhiteHexagon
11-10-2025, 12:39 PM
» Replies: 4
» Views: 313

 
Information FOSDEM 2018 Blog! New PINE64 Boards, Upcoming Hardware and Much More!
Posted by: Luke - 01-23-2018, 10:36 AM - Forum: News - Replies (2)

Welcome to the FOSDEM 2018 Blog! 

As many of you surely already know, this year we're at FOSDEM and you can find our stall in building AW. While much of this blog - as you probably expect - will feature PINE64's existing and upcoming products as well as peripherals, I will make sure to do the meetup justice by highlighting the things from the countless other projects that catch my eye. And boy am I sure there will be plenty of such things. 

Sadly, its unlikely that I will be able to cover any of the talks or lightning talks as for much of the time I will be either at the our stall or walking around checking things out. In any case, I invite you to have a read. Enjoy!  

Part 1. Pre-FOSDEM Announcement

NB. All images depict pre-production boards. Final products' appearance and features may vary from whats depicted. Posting is disabled in this thread; if you wish to discuss the Pine H64 and the RockPro64 then please head over to the [i]Pine H64 and the RockPro64 discussion thread.  [/i] 
 
We're happy to announce that we got two powerful boards coming in Q1 2018; the Pine H64 and the RockPro64.  Both boards are featured at our FOSDEM stall this year, so if you are attending make sure to drop by and check them out! The prior is a successor, or an upgrade if you like, to the Pine A64 while the latter is a powerhouse featuring a top-of-the-line Rockchip SOC for power-hungry applications.  

Here are some features shared by both boards: 

  • Both boards have the same dimensions as the original Pine A64 (133mm x 80mm x 19mm). 
  • Both support some of the existing add-ons, dongles, accessories and POTs (more info re. compatibility will follow at a later date). 
  • Both will support Android and Linux Distributions. 
  • Both feature multiple fast IO and expansion options as well as eMMC storage.  
  • Both come in variants with more than 2Gb RAM
  • Both feature 128Mb of SPI Flash
RockPro64 

The RockPro64 is the more powerful out of the two boards debuting in Q1 2018. It is based on the RK3399 hexa-core SOC consisting of a dual-core ARM Cortex-A72 and a quad-core ARM Cortex-A53. The GPU on the SOC is a quad-core Mali-T860MP4 with support for OpenGL ES1.1/2.0/3.0 and OpenCL1.2. Its one powerful board, so to keep the thermals at bay there are mounting holes for a heatsink and a header for a fan on the PCB. For those interested in the full feature set of the SOC you can read the feature specs here.

The RockPro64 offers a wide range of IO and expansion options (listed further down). The highlights of this board (in my opinion) are the USB-C - which can also be used to drive a second display (for a total of two) that can output 4K - as well as a PCIe4 connector for whatever expansion card you can imagine (e.g. a USB 3.1 PCIe 4 expansion card). In the future a PICe to NVMe adaptor will be available in our store for those who require ultra fast storage for their use-case scenarios. That said, the existing two fast USB interfaces (3.0 and C) open up a lot of possibilities in their own right when it comes to fast storage (and not only). The inclusion of SPI Flash will also make it possible to boot straight from one of the mentioned storage solutions. 
All that said, perhaps its the price that's the real highlight of this unit, as it starts at approx. $60 for the 2GB RAM variant (see all prices listed further down this post). 

The board also allows you to drive a LCD display right from the PCB (compatible with the existing LCD panel) and two cameras (the existing 5Mpixel camera module is compatible), that can be useful in embedded and robotics applications. To be precise, there are two LCD options on the board; MiPi which supports the existing LCD panel and an eDP port. So you can choose which one to use dependently on what you've already got in production or at hand. 

Its worth pointing out that we will also offer a version with the RK3399Pro SOC called Rockpro64-AI, which includes a Neural Network Processing Unit (NPU) for AI applications; "the computing performance of typical deep neural network Inception V3, ResNet34 and VGG16 models on RK3399Pro is better and improved nearly hundred times" (source). Its a piece of high performance AI hardware compatible with 8bit and 16bit AI software frameworks allowing for easy development of turnkey solutions. More information about this variant of the board will be made available closer to launch date (listed further down). 

I'm not going to write about software at this time - suffice to say that it will run the usual suspects - but the good news is that all the hard work ayufan and other devs have done in the past few months on the Rock64 will, by and large, carry over to the RockPro64. 

[Image: n8LGoSp.jpg]
(View from the top - USB 3.0 not soldered on revealing USB-C )
 
[Image: WSfnFpd.jpg]
(Front view with the - currently available - WiFi/BT module mounted. An AC and BT 4.1 module will be available in the future) 

Specs run-down:
  • 40pin GPIO header (I2C/SPI/I2S/UARTs/GPIOs)
  • 128Mb of SPI Flash
  • Heatsink mounting holes + FAN header
  • Power Button
  • Reset Button
  • Recovery Button
  • Dual Channel LPDDR4 Memory
  • Gigabit Ethernet
  • IR RX
  • eMMC
  • micro SD card bootable
  • SDIO socket for WIFI module
  • HDMI
  • eDP connector
  • MIPI connector + TP connector + backlight supply
  • 2xUSB2
  • 1xUSB3
  • 1xUSB-C (with DP)
  • PCIe4
  • parallel CSI
  • 2 x MIPI CSI
  • ES8316 Audio Codec (Headphone/MIC jack)
Pricing and availability:
  • Rockpro64 2GB board, $59.99
  • Rockpro64 4GB board, $79.99
  • Rockpro64-AI 4GB board, $99, available in November 2018
Pine H64 

[edit 31/01/2018] The Pine H64 is now available for purchase. 

The Pine H64 is based on the new Allwinner H6 SOC and is a successor to the Pine A64. It is a quad-core ARM Cortex-A53 SOC with a Mali-T720 MP2 dual-core GPU capable of 4K60 playback and HDR -- which makes it a compelling media board. It will be available in 3 different variants: 1GB, 2GB, and 3GB LPDDR4 RAM. So for those of you who always wanted a bit more RAM on your Pine A64/LTS you are bound to be happy now that such an option is available on this new unit. It will also feature 128Mb of SPI flash, that will allow it to boot off of a USB 3.0/2.0 HDD or SSD in addition to bootable micro SD cards and eMMC modules. You can find the complete feature set of the SOC here

Similarly to the RockPro64, the the Pine H64 PCB is packed with a wide range of IO and expansion options. The one that probably stands out the most to is the mini PCIe connector. The mPCIe connector opens up a number of different options for storage, WiFi cards or other expansion cards - e.g. a USB 3.1 expansion board - just to name a few obvious examples. With the Pine H64 you could conceivably support multiple fast storage mediums, turning it into a NAS or server. I'm sure people will think of other interesting applications for all this IO. Speaking of the available IO - if you already have the Pine A64 DAC POT or the BT/WiFi module, you will be happy to hear that both are compatible with this board. Similarly, as is the case with the RockPro64, the footprint is identical to the Pine A64/LTS, so if you have a purpose built enclosure or an off-the-shelf case its highly likely that the Pine H64 will fit it just fine.   

Another piece of good news is that at the end of January Allwinner will release a BSP with kernel 4.9 for the board. This means that while we all wait for mainline we will have a relatively new kernel to work on. As with the RockPro64, I am not going to write anything about software at this point other than you can obviously expect to run Android and Linux on the board.  

Summing it up, I feel that its safe to say that the Pine H64 is a worthwhile update to the Pine A64. Personally I see the inclusion of the much faster Mali-T720 MP2 and USB 3.0 as well as mPCIe as major selling points for this board; making it both viable as a media board (especially if ayufan makes one of those awesome ATV images for it) as well as a low powered NAS or a server that can drive multiple fast storage solutions. You can probably think of other awesome applications for this board as I'm sure there are plenty both for play and embedded applications. 

[Image: IbwdIb2.jpg]
(view from above)

Specs run-down:
  • microSD - bootable
  • 128Mb of SPI Flash
  • 1xUSB3.0 Host port 
  • 2xUSB2.0 Host ports
  • RTC - Real Time Clock Battery Connector
  • Wifi/BT Module Header - SDIO 3.0 and UART
  • 2x20 pins "Pi2" GPIO Header
  • mini PCIe connector
  • HDMI 2.0a (Type A)
  • 3.5mm stereo earphone/microphone plug
  • Gigabit Ethernet
  • 2x20 pins "Pi2" GPIO Header
  • eMMC 
  • IR RX
Pricing and availability:
  • Pine H64 1GB board, $25, available on January 31, 2018
  • Pine H64 2GB board, $35, available on January 31, 2018
  • Pine H64 3GB board, $45, available on January 31, 2018

Concluding the first part of this blog, I leave you with a picture of the PINE64 SBC lineup for the foreseeable future. Check back in a 5 days to read about some of the other exciting things we'll be showing at FOSDEM this year... as well as the countless other things from other Open Source and Open Hardware projects that I'll make sure to cover.  

[Image: 9PdVGm6.jpg]
 (From Left: RockPro64; Pine H64, Rock64, Pine A64-LTS; SOPine in Baseboard; Pine A64+)


  eMMC fail in 2% of flashing
Posted by: barucha - 01-23-2018, 03:13 AM - Forum: General Discussion on PINE A64-LTS / SOPINE - Replies (10)

Hi 

Is anyone know what can be the reason that the flash is warning "drive not found" or something like this after 2%-5% of lashing ?
the light is blinking on the USB2EMMC and lit constantly and that prompt with this error. 

I have test it with two different adapter and two eMMC. 

Thanks


Thumbs Up Looking for a partner to several projects
Posted by: barucha - 01-22-2018, 06:20 AM - Forum: General Discussion on PINE A64-LTS / SOPINE - No Replies

Hello guys, 

i have some developments I started, and I'm looking for some one who has VERY large
experience around Pine LTS . 

Also needed a great knowledge on Networks, perfect Linux scripts, kernel.
Programming with the GPIO, Bluetooth, Python.

Android App dev is advantage. 

Please send me email to b@mobie-market.co.il / whatup +972-54-3119110

THanks !!


  I found ADB debugging method via USB(OTG) Port
Posted by: spbrain - 01-21-2018, 07:47 PM - Forum: Android on Pine A64(+) - Replies (1)

I really needed ADB debugging via USB(OTG). But it was hard to find the right solution.
At first I was frustrated because I did not have much information about this problem.
I have tried to solve this problem in the last few days.

Through the efforts of the past, we find one way to share.

First
Modify the USB settings in the sys_config.fex file.
The port PH09 is used as an OTG cellactor, but it does not seem to have much relation with the switcher.(Using S/W Switch)

[usbc0]
usbc0_used          = 1
usb_port_type       = 2
usb_detect_type     = 1
usb_id_gpio         = port:PH09<0><1><default><default>
usb_det_vbus_gpio   = "axp_ctrl"
usb_drv_vbus_gpio   = port:power3<1><0><default><0>
usb_host_init_state = 0
usb_regulator_io    = "nocare"
usb_wakeup_suspend  = 0
;---       USB Device
usb_luns            = 3
usb_serial_unique   = 1
usb_serial_number   = "20080411"
rndis_wceis         = 1


After setting as above, boot with new build.
A Type to A Type Prepare the USB cable and connect it to the upper port.

Then issue the following command after the su command:
cat /sys/devices/soc.0/usbc0.5/usb_device
Afterwards, you can see that MTP and ADB are connected.

To use it again as a HOST, issue the following command:
cat /sys/devices/soc.0/usbc0.5/usb_host

I tested it with Android 5.1. (PINE64 LTS Version)


I originally thought that mode conversion should be done automatically using PH09 port, but it did not.
If you have a better idea, you might as well share it.


  Booting from USB
Posted by: Luke - 01-21-2018, 03:52 PM - Forum: General Discussion on ROCK64 - No Replies

There's been a couple of people asking about a 'how-to' for USB booting on the Rock64. 
There are now two sets of instructions on how to do it, which you can find here and here

[edit]The ones I wrote up on the wiki are more detailed for complete beginners while the ones on git are appropriate for those that know and understand the basics.


  Schematics of Wifi/BT module
Posted by: gamelaster - 01-21-2018, 12:51 PM - Forum: Wifi/BT Module - Replies (7)

Hello,

Is there available the schematics of Wifi/BT module?

Thank you


  Looking for linux kernel image with mptcp support (multipath-tcp) or LEDE (openWrt)
Posted by: xslite - 01-21-2018, 11:45 AM - Forum: Linux on Rock64 - No Replies

Hello,

is there any available linux kernel for ROCK64 that supports mptcp (multipath-tcp) ?

My goal is to install LEDE router software (OpenWRT) for dual link bridge aggregation.

Do you know any succesfull setup of LEDE with mpctcp module on the ROCK64 platform ?


Thanks for your feedback !

Best regads

XsLite


  Nextcloud not working with external harddrive
Posted by: floweih - 01-21-2018, 07:06 AM - Forum: General Discussion on ROCK64 - Replies (2)

hope someone can help me
I am trying to install nextcloud on my rock64. As the data directory I tried to use an external harddrive.
But there is an error when I try to use external harddrives as nextcloud data directory. When i use the
sd card as nextcloud data directory there are no probs
What I tried:
Mounting the Harddrive with fstab: UUID=a61b3225-3af0-439b-be5b-c54898b9aa46 /media/4TB           ext4    defaults        0       2
Which works for everything except nextcloud
As an alternative I tried  pmount as described on the howto for rock64. But this also doesnt work.
As OS I use debian
As nextcloud version 12.04
Any tips for nextcloud?


Greetings


  Reboot Issue with ROCK64 Linux version 4.4.77-rockchip-ayufan-141
Posted by: techyjtmb - 01-20-2018, 09:54 AM - Forum: General Discussion on ROCK64 - Replies (9)

I have a ROCK64 4GB setup and when I reboot I have a lot of trouble getting the unit stable.

Here are the errors that display on the screen:

core: dev_pm_opp_get_voltage: Invalid parameters
mali-utgard ff300000.gpu: Failed to get voltage for frequency 163840000: -34
devfreq ff300000.gpu: Couldn't update frequency transition information.

And then it goes into kernel panic mode.  I have to completely power down the unit,
remove the hdmi, ethernet, and keyboard cable, wait for 30 seconds and then it will boot.

I have tried a different power supply and plugging it in to a different power source.

I have 3 other similar ROCK64's working fine.


  Unable to flash Android TV on eMMC: rkflashtool error
Posted by: fbossi - 01-20-2018, 06:53 AM - Forum: General Discussion on ROCK64 - Replies (3)

Hello everybody,

I'm trying to flash my 64GB eMMC  with the latest Android TV build from ayufan: https://github.com/ayufan-rock64/android...3-r115.zip

I've been following this guide: http://files.pine64.org/doc/rock64/guide...o_eMMC.pdf

I'm running Arch Linux. I also tried the exact same steps on a Ubuntu 17.10 machine and I got the exact same behaviour.

Here's the output of the rkinstall script:

Code:
+ rkflashtool P
rkflashtool: info: rkflashtool v5.2
rkflashtool: info: Detected RK3328...
rkflashtool: info: interface claimed
rkflashtool: info: MASK ROM MODE
rkflashtool: info: writing flash memory at offset 0x00001c00... Done!
+ for i in uboot trust misc kernel boot recovery system
+ rkflashtool w uboot
rkflashtool: info: rkflashtool v5.2
rkflashtool: info: Detected RK3328...
rkflashtool: info: interface claimed
rkflashtool: info: MASK ROM MODE
rkflashtool: info: working with partition: uboot
rkflashtool: info: Error: 'mtdparts' not found in command line.
+ for i in uboot trust misc kernel boot recovery system
+ rkflashtool w trust
rkflashtool: info: rkflashtool v5.2
rkflashtool: info: Detected RK3328...
rkflashtool: info: interface claimed
rkflashtool: info: MASK ROM MODE
rkflashtool: info: working with partition: trust
rkflashtool: info: Error: 'mtdparts' not found in command line.
+ for i in uboot trust misc kernel boot recovery system
+ rkflashtool w misc
rkflashtool: info: rkflashtool v5.2
rkflashtool: info: Detected RK3328...
rkflashtool: info: interface claimed
rkflashtool: info: MASK ROM MODE
rkflashtool: info: working with partition: misc
rkflashtool: info: Error: 'mtdparts' not found in command line.
+ for i in uboot trust misc kernel boot recovery system
+ rkflashtool w kernel
rkflashtool: info: rkflashtool v5.2
rkflashtool: info: Detected RK3328...
rkflashtool: info: interface claimed
rkflashtool: info: MASK ROM MODE
rkflashtool: info: working with partition: kernel
rkflashtool: info: Error: 'mtdparts' not found in command line.
+ for i in uboot trust misc kernel boot recovery system
+ rkflashtool w boot
rkflashtool: info: rkflashtool v5.2
rkflashtool: info: Detected RK3328...
rkflashtool: info: interface claimed
rkflashtool: info: MASK ROM MODE
rkflashtool: info: working with partition: boot
rkflashtool: info: Error: 'mtdparts' not found in command line.
+ for i in uboot trust misc kernel boot recovery system
+ rkflashtool w recovery
rkflashtool: info: rkflashtool v5.2
rkflashtool: info: Detected RK3328...
rkflashtool: info: interface claimed
rkflashtool: info: MASK ROM MODE
rkflashtool: info: working with partition: recovery
rkflashtool: info: Error: 'mtdparts' not found in command line.
+ for i in uboot trust misc kernel boot recovery system
+ rkflashtool w system
rkflashtool: info: rkflashtool v5.2
rkflashtool: info: Detected RK3328...
rkflashtool: info: interface claimed
rkflashtool: info: MASK ROM MODE
rkflashtool: info: working with partition: system
rkflashtool: info: Error: 'mtdparts' not found in command line.
+ rkflashtool b
rkflashtool: info: rkflashtool v5.2
rkflashtool: info: Detected RK3328...
rkflashtool: info: interface claimed
rkflashtool: info: MASK ROM MODE
rkflashtool: info: rebooting device...

Please note the "Error: 'mtdparts' not found in command line" lines.

This is the output of rkflashtool n:

Code:
rkflashtool: info: rkflashtool v5.2
rkflashtool: info: Detected RK3328...
rkflashtool: info: interface claimed
rkflashtool: info: MASK ROM MODE
rkflashtool: info: Flash ID: 00 00 00 00 00
rkflashtool: info: Flash Info:
    Manufacturer: Samsung (0)
    Flash Size: 0MB
    Block Size: 0KB
    Page Size: 0KB
    ECC Bits: 0
    Access Time: 0
    Flash CS:

I have tried to boot my ROCK64 and flash the image in all the following modes:

- Loader Mode, as suggested in ayufan's guide (hold Recovery, press Reset, release Recovery after 3 seconds) and also as suggested in the SADIE script (hold Reset, hold Recovery, release Reset, release Recovery after 3 seconds). Please note that I'm NOT actualy running the SADIE script.
- Normal boot (by simply pressing the Power button)
- MASKROM boot (by pressing the Power button after short-circuiting the eMMC PINS with a jumper)

(Acually I really have no idea how to verify which mode my ROCK64 is actually booting into... Does anybody know a way? Maybe using UART?)

Regardless of what mode I'm trying to use, I ALWAYS get the same ouput for all commands (including the MASK ROM MODE line!).

Unfortunately I do not have a eMMC -> USB adapter (after reading the guides I concluded that it was not strictly necessary anymore so I did not purchase it) so I'm stuck to flashing directly on the board.

So in the end I'm stuck right now. Any help would be really appreciated.