| Welcome, Guest |
You have to register before you can post on our site.
|
| Latest Threads |
Looking for engineer for ...
Forum: PinePhone Pro Hardware
Last Post: Andrey_voce
04-06-2026, 08:44 AM
» Replies: 0
» Views: 172
|
StarPro64 Irradium (based...
Forum: Getting Started
Last Post: mara
04-05-2026, 03:03 AM
» Replies: 19
» Views: 8,723
|
Finally got Kali working ...
Forum: General Discussion on Pinebook Pro
Last Post: qingss0
04-04-2026, 08:00 AM
» Replies: 0
» Views: 265
|
Charging problem
Forum: General Discussion on Pinebook Pro
Last Post: RicTor
04-04-2026, 07:30 AM
» Replies: 0
» Views: 121
|
Latest firmware for PineP...
Forum: PinePhone Software
Last Post: baptx
04-03-2026, 08:37 AM
» Replies: 106
» Views: 217,083
|
Updates have gotten me ex...
Forum: General Discussion on PineNote
Last Post: bills2002
04-02-2026, 05:16 PM
» Replies: 0
» Views: 222
|
Voidlinux working on eMMC
Forum: General Discussion on PineTab
Last Post: tllim
04-01-2026, 04:14 PM
» Replies: 1
» Views: 304
|
Pinecil V2 doesn’t power ...
Forum: General Discussion on Pinecil
Last Post: Juptin
03-28-2026, 02:37 AM
» Replies: 1
» Views: 2,092
|
dead Pinebook - help plea...
Forum: General Discussion on Pinebook Pro
Last Post: williamcorlin
03-26-2026, 04:22 PM
» Replies: 3
» Views: 945
|
BT PAN - we need iptables...
Forum: Mobian on PinePhone
Last Post: biketool
03-25-2026, 12:57 PM
» Replies: 1
» Views: 608
|
|
|
| Mainline U-Boot with SPI, NVMe and SATA boot support |
|
Posted by: sigmaris - 01-03-2020, 01:00 PM - Forum: General Discussion on ROCKPRO64
- Replies (108)
|
 |
Update 2020-02-01: Made a new release based on v2020.01, with added SATA AHCI boot support, and a fix for the "rockchip_dnl_key_pressed: adc_channel_single_shot fail" issue where the Recover button wasn't being read successfully.
--
After seeing @pcm720's thread on porting the RK3399 PCIe/NVMe driver from Radxa's Rock Pi 4 U-Boot version, and this guide to building U-Boot for RockPro64 with all mainline, open source components, I've copied the aforementioned PCIe driver into mainline U-Boot, fixed a bug in the driver, created some configuration for U-Boot and a build script to create U-Boot binaries for RockPro64 with SPI and NVMe boot support.
The code is available on Github and:
- is based on mainline U-Boot
- doesn't use any binary-only blobs for booting
- with support for installation to SPI flash
- with support for storing the U-Boot Environment in SPI flash (configured to store it at offset 0x3f8000 bytes, 8KBytes size)
- can insert "partition" entries in the SPI Flash device tree for Linux so that /dev/mtdX devices are created for each area of the SPI flash layout it uses (if there is a spi-nor flash node in Linux's device tree for it to stick them on)
- with support for booting Linux off an NVMe device
- with support for booting Linux off a SATA drive attached to a PCIe SATA controller (AHCI)
- also supports the normal U-Boot features of booting from eMMC/SD/USB/Network
You can see the differences between current U-Boot master and this version here.
I have tested the SPI installation, SPI environment saving & loading, USB boot, network boot, SATA boot, and NVMe boot on my RockPro64 with a Samsung 970 EVO Plus NVMe device. I don't have any other NVMe devices to test with, and I'd like to verify this works for others, so if anyone else is interested, and would like to test this build, read on. In particular I'm uncertain if this works for other NVMe devices and possibly other SPI flash chips - my RockPro64 has a Gigadevice gd25q128 chip, but I've heard some other versions may use Winbond flash chips which I haven't been able to test with.
The build script (here) has several stages and builds several different binaries. The binaries attached to this release are:
- flash_spi.img.gz - this is an image which can be un-gzipped and written to an SD card, it starts U-Boot from the SD card and then runs this script to install U-Boot to SPI Flash. The image includes flash_spi.scr and spi_combined.img. More detailed info here.
- erase_spi.img.gz - this is an image similar to flash_spi.img.gz above, but instead it erases your SPI Flash using this script.
- flash_spi.scr - this is the compiled script to install U-Boot to SPI flash, it's not useful except for certain specific scenarios (if you want to make your own install SD-card). It is included in flash_spi.img.gz.
- mmc_idbloader.img - this is the image containing the TPL+SPL of U-Boot compiled for eMMC/SD card install, it should be written to eMMC or SD card at offset 64 sectors.
- mmc_u-boot.itb - this is the image containing U-Boot proper compiled for eMMC/SD card install, it should be written to eMMC or SD card at offset 16384 sectors.
- spi_idbloader.img - this is the image containing the TPL+SPL of U-Boot compiled for SPI Flash install, it should be written to SPI flash at offset 0, but for writing I recommend using spi_combined.img instead - see below.
- spi_u-boot.itb - this is the image containing U-Boot proper compiled for SPI Flash install, it should be written to SPI flash at offset 0x60000 bytes, but for writing I recommend using spi_combined.img instead - see below.
- spi_combined.img - this contains spi_idbloader.img, padding, and then spi_u-boot.itb at offset 0x60000 bytes, this can be written to SPI flash starting at offset 0 and will write spi_idbloader.img and spi_u-boot.itb at the correct locations.
For testing it - you'll need to have a serial / UART console available so that you can see log messages and interact with U-Boot that way - there is no HDMI or keyboard support in U-Boot.
Also, I strongly recommend *not* trying to flash it to SPI at first, since SPI is first in the RK3399 boot order, so if you flash something there and it doesn't work, your board is useless until you temporarily disable SPI to recover it.
Instead, first as a test just write mmc_idbloader.img and mmc_u-boot.itb to a spare SD card, remove / disable eMMC and SPI if you are currently booting off them, and test the NVMe boot functionality by booting off SD card, interrupting U-boot at the "Hit any key to stop autoboot" stage, and then entering: run bootcmd_nvme0 at the U-Boot => prompt to scan the NVMe device for bootable files and boot from it. On your NVMe drive, you just need something U-Boot can boot, e.g. a root partition with a /boot/extlinux/extlinux.conf or /boot/boot.scr telling it how to load the kernel, initrd and FDT file.
Then, if testing using a spare SD card works successfully, try installing to SPI, making sure you have a way to recover by disabling SPI temporarily if needed.
Some caveats: I've seen it mentioned that the PCIe driver for RK3399 from the Rock Pi 4 U-Boot is somewhat buggy, and looking at the code it seems like some PCIe features are missing or deliberately disabled; there is no support for more than one PCI device and no support for any other type of device apart from NVMe (so no PCI SATA adapter support at the moment, sorry). I don't know enough about the RK3399 PCIe controller to be able to find any more bugs from reading the code, but they might be there. Update: this is now using an updated PCIe driver from Patrick Wildt, based on OpenBSD's driver, and now does support PCI SATA adapters that implement the AHCI standard.
Also, if you're not sure what "write mmc_idbloader.img to eMMC or SD card at offset 64 sectors." means or how to do that, I recommend not trying this at all until some other folks have verified that it works, and it's packaged in an easier to use format.
|
|
|
|
| Kodi on Manjaro |
|
Posted by: brent.thierens - 01-03-2020, 12:14 PM - Forum: Linux on Pinebook Pro
- Replies (12)
|
 |
Hi
I am trying to run Kodi on Manjaro Linux. After compiling, Kodi runs, but video playback is very slow (1-2 FPS). The same video plays just fine with mpv player or smplayer. I used the PKGBUILD from the x64 Kodi, Kodi-git didn't like custom compile flags.
I tried compiling with the options provided in the default PKGBUILD. I also edited it to include
Code: -DX11_RENDERING_SYSTEM=GLES
that didn't help. I also added flags for
Code: -DENABLE_GL=OFF
-DENABLE_GLES=ON
-DENABLE_VAAPI=OFF
-DENABLE_VDPAU=OFF
didn't make a difference.
Given the fact that ffmpeg seems to handle the video just fine (mpv is a frontend for ffmpeg, right?), I also tried compiling with
Code: -DWITH_FFMPEG=SHARED
to use the ffmpeg from the system, but no luck.
I tried using it on Manjaro, my last tests were with the Panfrost driver active. I also tried once with GL4ES. In order to speed up the build, I only compiled kodi-x11, not kodi-gbm or kodi-wayland.
Worth to mention: on Debian Kodi works fine (although it's a much older version).
|
|
|
|
| PBR running hot |
|
Posted by: brzegorz - 01-03-2020, 10:53 AM - Forum: General Discussion on Pinebook Pro
- Replies (10)
|
 |
Hi,
I've just received the Pinebook Pro. I'm running the stock system. I've updated the kernel, the packages and keyboard firmware. Pinebook runs at 50 Celsius when doing only light browsing with the Powersave governor. Playing a 720p60 YT video pushes the CPU Temperature to 60-65 Celsius range. The laptop is particularly hot at the bottom beneath the Escape key, especially if I hold it on my laps. What should I do? The laptop is plugged with the supplied charger. Performance is choppy, the cursor stutters.
P.S. The temperature is 50 even when idling.
Thanks,
brzegorz
|
|
|
|
Idea, smart display, and TV box? |
|
Posted by: mzs.112000 - 01-02-2020, 06:08 PM - Forum: General
- Replies (2)
|
 |
Would it be possible to build a smart display, similar to the Amazon Echo Show devices?
It would go well with the IP cameras as well. The smart display could have a MiniPCIe slot and a SIM slot so it can be used as a hotspot on 4G. Maybe using Mycroft for voice controls. With 256GB of storage, could be used as a DVR for the IP cam...
A TV box would also do well. Would be pretty simple, just a RockPro64, but in a case, with lots of storage for movies and TV shows, Kodi preinstalled and an IR receiver.
|
|
|
|
| Monitoring CPU temperature. |
|
Posted by: Faradn - 01-02-2020, 04:10 PM - Forum: General Discussion on ROCKPRO64
- Replies (1)
|
 |
SBC: Rockpro64 v2.1 4Gb
OS: ubuntu 18.04 minimal w / Mate' DE
Linux rockpro64 4.4.190-1233-rockchip-ayufan-gd3f1be0ed310 #1 SMP
Wed Aug 28 08:59:34 UTC 2019 aarch64 aarch64 aarch64 GNU/Linux
So I decidd to install my RockPro64 in the Pine64 aluminum case and I'd like to monitor
the CPU temperature. The version of htop I have -- htop 2.1.0 -- does not have a CPU temp
monitor. Armbium/Bionic 18.04 version of htop did have a temp monitor. ~~83*C.
The case is nice and toasty (...like my Odroid N2 heatsink...)
How/What can I do to monitor the CPU temp?
TIA,
/Faradn
~ Rockpro64 ~ Odroid N2 ~ Odroid XU4 ~ Pi 3B ~
|
|
|
|
| Looking to commission a new Chromium build (COMMUNITY BOUNTY) |
|
Posted by: tophneal - 01-02-2020, 03:12 PM - Forum: Chromium OS on Pinebook Pro
- Replies (86)
|
 |
Hey there, fellow Piners!
I know it's not the most popular OS option for the PBP, but I love the simplicity and features available in ChromiumOS. I currently run ayufan's R77 build on my eMMC, and it's awesome, but I'd really like to see a working Crostini, and Android apps, if possible. The initial Chromium images were ready and available by the time most started getting their PBPs, and I imagine could probably benefit from some of the improvements from other kernels, since then.
From what I can tell ayufan is pretty busy with expanding the Linux support for the PBP, so I don't want to bother him with any requests. That man has given this community a lot of software already. I know I've used a lot of his builds across several Pine devices. I've tried to take this on myself as well, but I keep finding build documentation that isn't fully up-to-date and stops my progress, Google has been blocking me from setting up the necessary APIs, and plainly: I have no idea what the hell I'm doing.
This brings me to here and now. I'd like to commission a developer to create a more featured Chromium build for the community. As stated above, I know I really want to see a build with working - Crostini
- Android apps (from what I've read I think Android apps should work if Linux Beta does) This should get easier as CrOS develops and transitions to using ARCVM.
- the built-in cam (Currently works when using setup/settings to take a profile picture, but nowhere else.)
- retain suspend functionality (most of the OS options, especially with mainline kernels, seem to have lost this) At this point, I already know we'll have to make sacrifices to maintain S3 sleep. From what I understand it's possible to use up to v5.8 for the kernel with BSP uboot, though.
- one of the modified u-boots with SD or NVMe boot priority Now the latest mrfixit2001 BSP uboot already includes the traditional and additional boot priorities. Mainline uboot also includes these, in addition to USB IIRC.
If any other users feel I left something off here, please chime in.
I'm more than happy to contribute monetarily to anyone able to take this on, in addition to any testing, and hope that other users who would enjoy this image will too.
EDIT: The money pool can be found here: https://paypal.me/pools/c/8lzjzMkXjw
EDIT2: I just purchased an ANSI model from a user, so when it arrives, I could potentially provide my ISO to any developer that would like to take this on, but doesn't have a PBP.
EDIT 3: Interested in tackling this challenge, but lack the development resources? (CrOS requires a lot of space and X86 to build.) Contact me directly, and we can discuss providing you access to one of my servers.
|
|
|
|
Pine64 logo assets (Vector Graphics) |
|
Posted by: Twix166 - 01-02-2020, 12:14 PM - Forum: General Discussion on Pinebook Pro
- Replies (6)
|
 |
Apologies if this has been discussed before but after having trawled the forum and interwebs all day, I have been unable to find a vector graphics file for the Pine64 pinecone logo. Are any assets like this available? I have seen people make wallpapers with in other threads and they have used the logo. I just can't seem to find the logo anywhere. Maybe it is somewhere really obvious but my Google-fu has left me by now.
Many thanks for any help with this.
|
|
|
|
|