I want to know if I can have a video player for H264 working on my Debian Buster (from armbian.com).

I've tested mpv with the command:

Hello,

Do you know any usb-c dock do you think would be good for the pinebook pro?
One with dp or hdmi out + some usb2 and usb3 type A + charging + ethernet would be nice if working well on Linux.

For those who would rather discuss the August Update in the forum rather than blog comments, here's the place to do it.

August Update blog post is here.

Hello,
I am new here and new to PCB designs, but I am curious as to the cost and difficulty of making a printed motherboard/CPU.
Is there a place where I can get the gerber / BRD files to design / print my own PINE board or ROCK board?

Hi, Is vulkan supported on rockpro64?
I am using rockpro64 with Ubuntu18 image (Not latest one).

I am trying to build one project that requires Vulkan support for gpu acceleration.
Are there drivers for Vulkan in rockpro? Is latest image have that?
Thanks

I download ROCKPro64_20190417_stock_android_9.0_emmcboot.img and flash it to emmc.

My board stop booting at u-boot.

Please look at below boot message and guide me how to fix this issue.




DDR Version 1.19 20190305
In
channel 0
CS = 0
MR0=0x98
MR4=0x2
MR5=0xFF
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 1
CS = 0
MR0=0x98
MR4=0x1
MR5=0xFF
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 0 training pass!
channel 1 training pass!
change freq to 400MHz 0,1
channel 0
CS = 0
MR0=0x98
MR4=0x2
MR5=0xFF
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 1
CS = 0
MR0=0x98
MR4=0x1
MR5=0xFF
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 0 training pass!
channel 1 training pass!
change freq to 800MHz 1,0
Channel 0: LPDDR4,800MHz
Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=16 Size=1024MB
Channel 1: LPDDR4,800MHz
Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=16 Size=1024MB
256B stride
ch 0 ddrconfig = 0x101, ddrsize = 0x20
ch 1 ddrconfig = 0x101, ddrsize = 0x20
pmugrf_os_reg[2] = 0x3281F281, stride = 0x9
OUT
Boot1: 2019-03-14, version: 1.19
CPUId = 0x0
ChipType = 0x10, 237
SdmmcInit=2 0
BootCapSize=100000
UserCapSize=59640MB
FwPartOffset=2000 , 100000
mmc0:cmd8,20
mmc0:cmd5,20
mmc0:cmd55,20
mmc0:cmd1,20
mmc0:cmd8,20
mmc0:cmd5,20
mmc0:cmd55,20
mmc0:cmd1,20
mmc0:cmd8,20
mmc0:cmd5,20
mmc0:cmd55,20
mmc0:cmd1,20
SdmmcInit=0 1
StorageInit ok = 70323
SecureMode = 0
SecureInit read PBA: 0x4
SecureInit read PBA: 0x404
SecureInit read PBA: 0x804
SecureInit read PBA: 0xc04
SecureInit read PBA: 0x1004
SecureInit read PBA: 0x1404
SecureInit read PBA: 0x1804
SecureInit read PBA: 0x1c04
SecureInit ret = 0, SecureMode = 0
atags_set_bootdev: ret0)
GPT part:  0, name:            uboot, start:0x4000, size:0x2000
GPT part:  1, name:            trust, start:0x6000, size:0x2000
GPT part:  2, name:             misc, start:0x8000, size:0x2000
GPT part:  3, name:         resource, start:0xa000, size:0x8000
GPT part:  4, name:           kernel, start:0x12000, size:0x10000
GPT part:  5, name:              dtb, start:0x22000, size:0x2000
GPT part:  6, name:             dtbo, start:0x24000, size:0x2000
GPT part:  7, name:           vbmeta, start:0x26000, size:0x800
GPT part:  8, name:             boot, start:0x26800, size:0x10000
GPT part:  9, name:         recovery, start:0x36800, size:0x20000
GPT part: 10, name:           backup, start:0x56800, size:0x38000
GPT part: 11, name:         security, start:0x8e800, size:0x2000
GPT part: 12, name:            cache, start:0x90800, size:0x100000
GPT part: 13, name:           system, start:0x190800, size:0x500000
GPT part: 14, name:         metadata, start:0x690800, size:0x8000
GPT part: 15, name:           vendor, start:0x698800, size:0x100000
GPT part: 16, name:              oem, start:0x798800, size:0x100000
GPT part: 17, name:              frp, start:0x898800, size:0x400
GPT part: 18, name:         userdata, start:0x898c00, size:0x6be33df
find part:uboot OK. first_lba:0x4000.
find part:trust OK. first_lba:0x6000.
LoadTrust Addr:0x6000
No find bl30.bin
Load uboot, ReadLba = 4000
Load OK, addr=0x200000, size=0xe1b90
RunBL31 0x10000
NOTICE:  BL31: v1.3(debug):370ab80
NOTICE:  BL31: Built : 09:23:41, Mar  4 2019
NOTICE:  BL31: Rockchip release version: v1.1
INFO:    GICv3 with legacy support detected. ARM GICV3 driver initialized in EL3
INFO:    Using opteed sec cpu_context!
INFO:    boot cpu mask: 0
INFO:    plat_rockchip_pmu_init(1181): pd status 3e
INFO:    BL31: Initializing runtime services
INFO:    BL31: Initializing BL32
INF [0x0] TEE-CORE:init_primary_helper:337: Initializing (1.1.0-195-g8f090d20 #6 Fri Dec  7 06:11:20 UTC 2018 aarch64)

INF [0x0] TEE-CORE:init_primary_helper:338: Release version: 1.2

INF [0x0] TEE-CORE:init_teecore:83: teecore inits done
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x200000
INFO:    SPSR = 0x3c9


U-Boot 2017.09-02833-g5b99639 (Apr 16 2019 - 14:29:24 +0800)

Model: Rockchip RK3399 Evaluation Board
PreSerial: 2
DRAM:  2 GiB
Sysmem: init
Relocation Offset is: 7dbe3000
Using default environment

dwmmc@fe320000: 1, sdhci@fe330000: 0
Bootdev(atags): mmc 0
sdhci_transfer_data: Transfer data timeout
sdhci_transfer_data: Transfer data timeout

Hi,

I received my RockPro64 with 4GB about 2 weeks ago, and this weekend, decided to assemble it in its case.

My question is about the boot sequence:  When I apply power from the power supply I purchased with it, the green power LED lights next to the plug, then the two lights on the ethernet port light and the yellow one flashes with the traffic from the switch.

There is *never* any output to either the HDMI monitor (1080p) or the 4k TV I also attached it to. (Although the TV seems to recognize that there is an HDMI device attached).  I tried two devices in case there was a problem, although both work fine with other things attached to the same inputs.

Should there be any output at boot time indicating that the board is alive, (POST, Diagnostics, anything) even if I have a problem with the boot image?

Just trying to figure out what I need to troubleshoot :-)

Thanks

Gerry

As the Thread Subject says, it died.  It's been happily running for a couple years now, and it looks like it went down night before last.

Now when I say "died", it's not totally dead, it just refuses to boot into Linux.  The console was non-responsive, so I reset it, and it hung during the boot process.  After that, I tried multiple different SD cards, and a couple different USB drives, as well as unplugging everything from the board (Ethernet & USB).  It repeatedly hangs at various points during the boot process every time, never getting through the whole boot process.

I have U-Boot 2017.09-rockchip-ayufan-1062-gbb4886a528 (Jun 19 2019 - 19:41:42 +0000) programmed into the SPI Flash, and even tried reprogramming that.

I wrote this post looking for some hardware diagnostics I could run from U-Boot, since that's the only thing that boots reliably.  I was suspecting either a DRAM failure, or something in the CPU itself.  I searched around with Google, but didn't find anything Rock64 specific in the diagnostics category.

Now for the happy ending.  After a day and a half of trying different things, after typing up this post, I looked at the board again trying to think of anything else to try, when I realized I had not tried a different power supply.  I did a quick search and found another 5V supply, plugged it in, and viola, it booted to the rock64 login prompt!!

What an ordeal.  So for the record, it you see strange behavior, even after a couple years, don't forget to try another power supply.

For the technically curious, the supply I've been using is a 5V/2A switcher style supply.  I measured it's output with a DMM, and with no load, it was 5.7VDC.  When connected to the Rock64, I saw it drop below 4.4VDC while trying to boot.

I checked the power draw of the Rock64 with only a 8GB Sony USB stick plugged into the USB3.0 port and the Ethernet cable connected, and it's sitting at 0.274A booted to the login prompt.  While booting, I never saw it go above 0.6A.

Now to put everything back as it was.  I'm glad this ordeal is over.   

I have tried several devices (mouse and jump drives) in left USB port, with no function at all (although it seems to be powering the mouse laser, with flickering). This is after installing latest stable (supported) Armbian.

The right USB port functions normally.

The left port seemed to work with the initial Android OS, though Android was unable to read the Linux image on that USB drive.

I did install the 'mini firmware package' using Armbian-config -> [System and third-party software] -> [Mini] (if that is relevant).

Thanks for any help regaining the lost USB port.

Any of the pine64 products separate the memory bus/channel and the Networking / USB bus? Or do none of the products reuse the bus for both purposes?
Thanks.