0AD - 3D RTS

Cave Story - Pixel Art Metroidvania

Dr Robotnik's Ring Racers - Kart Racer

Dune Legacy - RTS

Endless Sky - Space Sandbox

Flare - Fantasy RPG

Freeciv - Strategy

Freecol - Strategy

GZDoom - Doom Engine for Mods & Total Conversions

Hedgewars - Worms "Homage"

Neverball - Monkeyball "Homage"

Neverputt - Miniputt Golf Game

Open Fodder - FOSS Engine for "Cannon Fodder"

OpenRA - FOSS RTS Engine for "Tiberian Dawn", "Red Alert" & "Dune 2000"

Open TTD - Transit Management Sim

OpenTyrian - FOSS Engine for Top-Down Shmup "Tyrian"

Perfect Dark - PC Port of N64 Game with Keyboard/Mouse Support

Pico-8 - Indie Pixel Art Gaming & Development Platform

Pingus - Lemmings "Homage"

ScummVM - FOSS Engine for Classic Point & Click Games

Sonic Robo Blast 2 - 3D Platformer

The Ur-Quan Masters - FOSS Port of Space Sandbox "Star Control II"

Xonotic - Arena Shooter FPS

There are other games I have not yet personally tried like OpenHV, SuperTuxKart, other emulators etc but if anyone can confirm they work reasonably well on the Pinebook Pro then please let the rest of us know. All ScummVM games I've tried from King's Quest I to Grim Fandango work perfectly. However GZDoom will struggle with especially demanding modern Doom mods like Trenchfoot, Auger Zenith, Inquisitor III, Godless Nite etc. but most like Aliens: Eradication, Ashes 2063/Afterglow, Brutal Doom, Castlevania: Simon's Destiny, Irontusk's Diablo 3D, Revenge of the Triad etc run just fine.

Tow Boot

I had already installed an older version of Tow Boot, but i updated it to 2023.07-007 

This is a simple process. Write out the spi.installer.img to an sd card (i used dd). Insert the sd card in to the slot on the side of the pinebook. Start the system. Follow the prompts. Shut down the system. Remove the sd card. Power on the system and hit "Esc" to see the Tow Boot menus and verify the version has been updated in the "Firmware Console" by typing "version"

A major change appears to be that Tow Boot has inherited a minimum viable EFI interface from U-Boot. This allows generic efi arm images to boot, but because the efi configuration is stored in the efi partition rather than spi flash, tools like efibootmgr don't work. Read more here in github

(I don't think its worth trying to run without Tow Boot installed on the spi, despite the limited efi)

Install Armbian

I downloaded the Cinnamon Debian version listed on the Pinebook Pro page - the exact file was Armbian_25.2.1_Uefi-arm64_bookworm_current_6.12.13_cinnamon-backported-mesa_desktop.img.xz

I then unxz'd that file and dd the image to the sd card.

Insert the sd card in to the pinebook and power on. Armbian boots!

Install works as normal, but you will notice that efibootmgr commands are failing in the install script although they are non fatal at this stage. This is due to the Tow Boot efi limitations mentioned above.

Unfortunately, Armbian will install the grub efi binary as /EFI/Armbian/grubaa64.efi and failing to add a boot entry, the system will fail to boot.

You have two options.

The first is to copy /EFI/Armbian/grubaa64.efi to default location /EFI/BOOT/BOOTAA64.EFI - this is also perhaps the safest in the short term.

(note that on the installer sd card the file is located at /EFI/BOOT/BOOTAA64.EFI). You may need to manually mount the new EFI partition on the mmc and copy the file - do this before rebooting the system so the system remains bootable. If you don't there is no need to panic, adding a boot entry to Tow Boot's efi is very simple from its menus as i will now describe...

The second is to add a boot entry in the Tow Boot menus.

Contrary to the github issue linked above, it seems that in Tow Boot the "efidebug" command has been replaced with a more convenient set of commands to manage boot options.

Power on your pinebook pro, press "Esc" to see the Tow Boot menu and go in to "Firmware Console". Type "eficonfig" and use the convenient menu to add a new boot entry - not that the tow boot console has tab completion which is very convenient. In "eficonfig" hit enter on "Add Boot Option", set "Description" to "Armbian", hit enter on "File" then "Select File" then "mmc 0:1" and find the Armbian/grubaa64.efi file. Then "Save" (initrd and optional data left empty). Then "Change Boot Order" and move the new Armbian entry to the top with -/+ keys then Save. Exit "eficonfig" and continue with a normal boot by typing "bootefi bootmgr"

I suggest do both, and once the system is booting from the new boot entry you can remove the BOOTAA64.EFI file as good hygiene

I also observed that the Tow Boot menu does freeze up occasionally and the only solution is to press the power button. Also you do seem to need to press keys slowly.

Minor issue at log in

I observed that for a brief period the keyboard doesn't work at the log in prompt. 

The speakers give their normal tick sound and the cursor stops flashing - which presents like the system has frozen. I found that pressing the power button causes the system to gracefully shut down - so the system hasn't locked up. 

Be patient and a moment or two later, the cursor starts flashing again and the keyboard works. I dont know what is causing this behavior but perhaps someone else is interested to dive in to it.

Apt update and beyond

With the system booted and logged in, i ran updates and rebooted. Things continued to work properly

I see there were Pinebook-Pro-specific install images for older version of Armbian, but there doesn't appear to be any for more recent versions, and currently, the download page points to (non-machine-specific?) UEFI install images.  Is this a transition that was discussed/announced, and can I read the discussion/announcement in archives somewhere?

Also, does anyone have any installation/testing reports?  Is 25.02 known to work on the Pinebook Pro?

I've tried a few different times to create a Armbian SDCard for my Pinebook Pro.  I've only had one success, one one of my early attempts.  Unfortunately, I did not take very good notes, and I've lost track of which downloaded image file I used to create it.  I still have the successfully-created SDCard, and it still works, but I haven't been able to create another.  When I inspect the contents of the good SDCard, it appears to be 24.8.1, and it boots via GRUB, but I'm not sure if it was made from a PinebookPro-specific image or a UEFI image.

There's plenty more testing I could do on my own -- my supply of SDCards is running low, and I should buy a few more, and in an assortment of sizes (successful SDCard was 32GB, some of the most recent attempts (which failed) were to a 256GB SDcard)

Today I pulled down the 25.2.1/6.12.16 update. On booting in Grub, I now get a message "Loading Device Tree Blob...", followed by "Error: not a regular file Press any key to continue". The boot then continues after a bit, and system seems to work fine from a user perspective after that (posting this from the machine). But there are some rockchip-pcie, rk3399-dmc-freq and brcmf errors in the armbianmonitor output (attached url) .

I'm an Armbian noob, so dunno if the errors were there on the previous version. The 25.2.1 install re-wrote the grub entries so I don't have the previous kernel to boot into to do any debugging, but it used to boot cleanly before the update.  Wondering if there is a known situation here, before I dig into the whole dtb thing. Thanks!

unfortunatelly I post again, because of the latest problem with broken install of initramfs .... The system is unable to write it to uboot and gives the error about unsupported architecure. Every standard commands are probed, without result. it comes always the same error.

Quote

update-initramfs: Generating /boot/initrd.img-6.6.2-edge-rockchip64
update-initramfs: Armbian: Converting to u-boot format: /boot/uInitrd-6.6.2-edge
-rockchip64

Invalid architecture, supported are:
    alpha            Alpha
    arc              ARC
    arm              ARM
    arm64            AArch64
    avr32            AVR32
    blackfin         Blackfin
    ia64             IA64
    invalid          Invalid ARCH
    m68k             M68K
    microblaze       MicroBlaze
    mips             MIPS
    mips64           MIPS 64 Bit
    nds32            NDS32
    nios2            NIOS II
    or1k             OpenRISC 1000
    powerpc          PowerPC
    riscv            RISC-V
    s390             IBM S390
    sandbox          Sandbox
    sh               SuperH
    sparc            SPARC
    sparc64          SPARC 64 Bit
    x86              Intel x86
    x86_64           AMD x86_64
    xtensa           Xtensa

Error: Invalid architecture
Usage: mkimage -l image
          -l ==> list image header information
       mkimage [-x] -A arch -O os -T type -C comp -a addr -e ep -n name -d data_
file[:data_file...] image
          -A ==> set architecture to 'arch'
          -O ==> set operating system to 'os'
          -T ==> set image type to 'type'
          -C ==> set compression type 'comp'
          -a ==> set load address to 'addr' (hex)
          -e ==> set entry point to 'ep' (hex)
          -n ==> set image name to 'name'
          -d ==> use image data from 'datafile'
          -x ==> set XIP (execute in place)
       mkimage [-D dtc_options] [-f fit-image.its|-f auto|-F] [-b <dtb> [-b <dtb
>]] [-E] [-B size] [-i <ramdisk.cpio.gz>] fit-image
           <dtb> file is used with -f auto, it may occur multiple times.
          -D => set all options for device tree compiler
          -f => input filename for FIT source
          -i => input filename for ramdisk file
          -E => place data outside of the FIT structure
          -B => align size in hex for FIT structure and header
Signing / verified boot options: [-k keydir] [-K dtb] [ -c <comment>] [-p addr]
[-r] [-N engine]
          -k => set directory containing private keys
          -K => write public keys to this .dtb file
          -G => use this signing key (in lieu of -k)
          -c => add comment in signature node
          -F => re-sign existing FIT image
          -p => place external data at a static position
          -r => mark keys used as 'required' in dtb
          -N => openssl engine to use for signing
       mkimage -V ==> print version information and exit
Use '-T list' to see a list of available image types
run-parts: /etc/initramfs/post-update.d//99-uboot exited with return code 1
dpkg: error processing package initramfs-tools (--configure):
 installed initramfs-tools package post-installation script subprocess returned
error exit status 1
Errors were encountered while processing:
 initramfs-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)

Regards,

Dianne.

 

bootloop.txt

Finally I managed to install bullseye by using a buster image, deactivtion kernel upgrade and removed the armbian.list from /etc/apt/

Then I changed source list from buster to bullseye

apt update

apt upgrade -y

apt full-upgrade -y

thats it.

And i  is really a shame to fool the community by uploading untested software.

But after I upgrade the system with apt update & upgrade, the next time the machine is booted and SD card is selected, armbian won't boot anymore 😞

The upgrade seem to have broken something. I tried it twice, the second time freezed the kernel-upgrades in the armbian-config tool prior to upgrading it. Didn't help. Manjaro from EMMC still boots ok.

Attached is a screenshot of the failed boot process, after I selected SD card to boot on the Tow Boot menu.

And since then I have not been able to get it to boot Armbian.  It came from the factory with Manjaro, which for me being a Debian guy, might as well be useless.  So the PBP sat around collecting dust.

Since then I have tried a few times to get it to work.  I read many forum posts, tried some things.  I won't document all that in detail.

In this post, I will continue from where I left off here.  However to summarize, that was about comparing DTB/DTS files to Kali, which supposedly works.  That may become useful later, but I don't think that's the main problem.

I think that the main problem is that this new batch came from the factory with no bootloader flashed to the included SPI flash chip.  This is a problem on PineBook Pro because the RK3399 has a kind of weird boot order: SPI, eMMC, SD card.  Therefore, if you just put in some SD card you flashed, it still boots from the factory Manjaro from the eMMC.  Whatever bootloader they are using also apparently will not recognize an otherwise working Armbian image on an SD card.

Now, because of the weird boot situation, there is supposed to be a switch to turn off eMMC.  However this did not work for me.  Which means one of 2 things:

1. The switch does not work.  I read at least one other person saying this.  Also on the new revision, it's in a slightly different place than the old revision (may be a clue, maybe not).
2. I simply had a bad Armbian image (which I had burned to sd card) that would not boot for whatever reason.[0]

But let's put that aside for a moment.  As I still think the main problem is the (empty) SPI.  And that will be the easiest/best path forward.

I confirmed the 'blank SPI' theory 2 different ways.  First, as mentioned in a follow-up to the linked post (4 paragraphs above):

As Martijn Braam states here:

Quote

But the Pinebook Pro has a similar boot configuration, and thus a similar problem. Some time after the PinePhone Pro was shipped, it was time for a new Pinebook Pro batch, and this discussion started again. The same arguments were re-iterated by all sides all over again, and the discussion went nowhere. PINE64 representatives went so far as to say, quote, "people who want [an SPI chip] can just solder one on". This batch of Pinebook Pros has ended up shipping without Tow-Boot flashed.

Of course, I like to beat a horse until it's really dead be thorough in my investigations, so today I wasted a lot of time[1] verifying that this indeed was the case.  I did so by dd'ing the /dev/mtd0 block device into a file[2].  When I examined the file, it contained all FF, and also it is about 16 MiB in size.  To me this confirms that indeed, the SPI on the new batch comes from the factory empty.

So what is next?  I keep reading that the only people who had success first had to install something like tow-boot to the SPI.  That will be my next step.  But before I flashed anything to SPI, I wanted to see what really came from the factory (which I did above).

I will continue to document my progress whenever time allows for me to work on this.

[0] Once I got the bootloader situation sorted, I later used this same image (on the SD card) to boot and install Armbian, so I do not think this was the case.

[1] In the end the solution was simple.  But first I wasted a lot of time trying to get rkdeveloptool working in Manjaro on the PBP.  Only to realize it's intended to be used from a second machine to read the SPI flash via USB in maskrom mode.  Anyway, lesson learned.

[2] I tried to attach it but maybe it's too big.

Armbian 24.5.1 Noble Gnome + trunk MESA/VPU
Kernel: 6.6.31, Size: 1.3GB, Release date: May 25, 2024

on my PBP (sd card).

What does not work:

- Sound

- HDMI Monitor on PB dock

Thank you

Referring to https://forum.armbian.com/topic/32667-usb-c-port-doesnt-work-on-pinebook-pro-after-the-latest-update-on-kernel-662/ USB -C is not working. I also tried 6.7.4-edge with no success. Looking for a solution G??gle found this: https://www.linuxquestions.org/questions/slackware-arm-108/pinebook-pro-usb-c-port-not-working-after-kernel-upgrade-4175732886/#google_vignette referring to Megi`s 6.7 kernel. The link was outdated, but the base worked and had versions 6.8 and 6.9.

Tried both with a lot of success: USB-C working and the HDMI monitor output as well as Gigabit Ethernet work like a charm again.  😄

The only small issue remaining: Sound is not working (no analog or digital.)

armbianmonitor: https://paste.armbian.com/mamocolodo

(I had a small issue following Megi`s Readme: The board.dtb should replace rk3399-pinebook-pro.dtb in one of the existing dtb trees. I used dtb-6.7.4-edge-rockchip64.)

any ideas about the sound issue are greatly appreciated.

Sepp

as already mentioned in topic USB C port doesn't work after upgrading to the latest kernel 6.6.2 .

The previous problem with not working left usb 3 port persist no more. Everything is fine. As I remember , before update the usb c port has worked with the adapter and the devices like mouse, usb flash etc. Now it doesn't work any more, furthermore it gives no signal of life. There is 0 amps current measured, also dmesg -W gives no output at all after plugging in the device.

PS: I was unable to upload the report file, also the service paste.armbian.com doesn't work at the moment.

I got a problem after new update of armbian firmware through your own module (script). The left USB port on pinebook pro has  stoped working at all. Before that was occasionaly after 6 -7 boot ups only one time not working  (it is used for mouse). Now after x rebooting it doesnt work at all. The right USB port works without problems. On the left, also USB flash drive doesn't work. No idea, what could it be? Before, as already said, it has worked in 90%. Before firmware upgrade.

Because that essentially bricked my PBP. I have the little adapter to connect the emmc to a usd slot, and using balena etcher to write to that isn't it either. 

the uboot in that image prevents booting from sd automatically as well, and i didn't find any uboot documentation that made it clear how to manually boot from sd, though i did hook up a serial console. This is what it said. The LED never turned green, the display flashes once but displays no images or text. 

Quote

U-Boot TPL 2021.07-armbian (Feb 27 2022 - 08:51:28)
Channel 0: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
Channel 1: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
256Bstride
lpddr4_set_rate: change freq to 400000000 mhz 0, 1
lpddr4_set_rate: change freq to 800000000 mhz 1, 0
Trying to boot from BOOTROM
Returning to boot ROM...

U-Boot SPL 2021.07-armbian (Feb 27 2022 - 08:51:28 +0000)
Trying to boot from MMC1
NOTICE: BL31: v2.5(release):c1588782-dirty
NOTICE: BL31: Built : 08:51:19, Feb 27 2022


U-Boot 2021.07-armbian (Feb 27 2022 - 08:51:28 +0000)

SoC: Rockchip rk3399
Reset cause: POR
Model: Pine64 Pinebook Pro
DRAM:  3.9 GiB
PMIC:  RK808
MMC:  mmc@fe310000: 2, mmc@fe320000: 1, sdhci@fe330000: 0
Loading Environment from SPIFlash... SF: Detected gd25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
*** Warning - bad CRC, using default environment

In:    serial
Out:  serial
Err:  serial
Model: Pine64 Pinebook Pro
Net:  No ethernet found.
starting USB...
Bus usb@fe380000: USB EHCI 1.00
Bus usb@fe3a0000: USB OHCI 1.0
Bus usb@fe3c0000: USB EHCI 1.00
Bus usb@fe3e0000: USB OHCI 1.0
Bus dwc3: usb maximum-speed not found
Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
Bus dwc3: usb maximum-speed not found
Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
scanning bus usb@fe380000 for devices... 1 USB Device(s) found
scanning bus usb@fe3a0000 for devices... 2 USB Device(s) found
scanning bus usb@fe3c0000 for devices... 3 USB Device(s) found
scanning bus usb@fe3e0000 for devices... 1 USB Device(s) found
scanning bus dwc3 for devices... 1 USB Device(s) found
scanning bus dwc3 for devices... 1 USB Device(s) found
      scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot:  0

Device 0: unknown device
Card did not respond to voltage select! : -110
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
3185 bytes read in 20 ms (155.3 KiB/s)
## Executing script at 00500000
Boot script loaded from mmc 0
157 bytes read in 15 ms (9.8 KiB/s)
14235892 bytes read in 637 ms (21.3 MiB/s)
30083584 bytes read in 1311 ms (21.9 MiB/s)
82621 bytes read in 38 ms (2.1 MiB/s)
2698 bytes read in 32 ms (82 KiB/s)
Applying kernel provided DT fixup script (rockchip-fixup.scr)
## Executing script at 09000000
Moving Image from 0x2080000 to 0x2200000, end=3f50000
## Loading init Ramdisk from Legacy Image at 06000000 ...
  Image Name:  uInitrd
  Image Type:  AArch64 Linux RAMDisk Image (gzip compressed)
  Data Size:    14235828 Bytes = 13.6 MiB
  Load Address: 00000000
  Entry Point:  00000000
  Verifying Checksum ... OK
## Flattened Device Tree blob at 01f00000
  Booting using the fdt blob at 0x1f00000

If I use the UUID provided in the Armbian-install then I can boot from emm but it ends up mounting and running from the SD partition.

Is there any code that can be inserted into the /boot/armbianEnv.txt file that would provide better diagnostics?  To me it appears as if the emm partitions UUID is not available at boot time.

Thanks,

Carl

bluetooth stopped working

uname -a
Linux pinebook 5.15.76-rockchip64 #22.08.8 SMP PREEMPT Sun Oct 30 10:57:32 CET 2022 aarch64 GNU/Linux

dmesg | grep Bluetooth
[    9.863147] Bluetooth: Core ver 2.22
[    9.863249] Bluetooth: HCI device and connection manager initialized
[    9.863261] Bluetooth: HCI socket layer initialized
[    9.863266] Bluetooth: L2CAP socket layer initialized
[    9.863276] Bluetooth: SCO socket layer initialized
[    9.972130] Bluetooth: HCI UART driver ver 2.3
[    9.972144] Bluetooth: HCI UART protocol H4 registered
[    9.972147] Bluetooth: HCI UART protocol BCSP registered
[    9.972218] Bluetooth: HCI UART protocol LL registered
[    9.972222] Bluetooth: HCI UART protocol ATH3K registered
[    9.972261] Bluetooth: HCI UART protocol Three-wire (H5) registered
[    9.972460] Bluetooth: HCI UART protocol Intel registered
[    9.972609] Bluetooth: HCI UART protocol Broadcom registered
[    9.972646] Bluetooth: HCI UART protocol QCA registered
[    9.972649] Bluetooth: HCI UART protocol AG6XX registered
[    9.972688] Bluetooth: HCI UART protocol Marvell registered
[   12.322372] Bluetooth: hci0: command 0xfc18 tx timeout
[   20.450331] Bluetooth: hci0: BCM: failed to write update baudrate (-110)
[   20.450363] Bluetooth: hci0: Failed to set baudrate
[   20.799400] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   20.799435] Bluetooth: BNEP filters: protocol multicast
[   20.799461] Bluetooth: BNEP socket layer initialized

blueman-manager
blueman-manager 14.32.28 ERROR    Manager:147 on_dbus_name_appeared: Default adapter not found,
blueman-manager 14.32.28 ERROR    Manager:151 on_dbus_name_appeared: No adapter(s) found, exitin

stopped working after last system update

I don't really have a question, but just wanted to report I tried out the generic UEFI arm64 image on a Pinebook Pro, and it installed emmc and booted just fine!

This was possible because I had installed Tow-Boot to the SPI flash, which supports UEFI booting.

I had tried using the Pinebook Pro build of armbian, which worked fine when booting off the sdcard, but installing it to the emmc wasn't working.

I'm using Tow-Boot 2021.10 then arbmian image Armbian_22.08.7_Uefi-arm64_jammy_current_5.15.74 .

There's a few rough edges in the grub menu, but it boots the OS off the emmc just fine.

Should the be mentioned on the Pinebook Pro page? Personally, having Tow-Boot installed to SPI is all around a much more "normal" laptop experience, so it seems like a good idea in general.

$ iperf3 -c 192.168.0.34
Connecting to host 192.168.0.34, port 5201
[  5] local 192.168.0.33 port 48140 connected to 192.168.0.34 port 5201
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  41.7 MBytes   350 Mbits/sec    0    298 KBytes 

(More thread only made results worst)

While the same DUB-1312 plugged in my amd64 ubuntu computer achieve 950Mb/s easly (capped by the other testing device (an odroid-hc1)).

Same thing for a random usb 3.1 key I have laying around (so its very unlikely a problem with the ethernet over usb driver).

It seems to me that the usb 3 port is only being used with usb 2.

Am I the only with this issue ?

cmake -DHAVE_DRM='ON' -DCMAKE_BUILD_TYPE:STRING='Release' -DCMAKE_INSTALL_PREFIX:PATH='/usr' \ -DRKPLATFORM:BOOL='ON' -Wno-dev \ -DAVSD_TEST:BOOL='OFF' -DH264D_TEST:BOOL='OFF' -DH265D_TEST:BOOL='OFF' -DJPEGD_TEST:BOOL='OFF' \ -DMPI_DEC_TEST:BOOL='OFF' -DMPI_ENC_TEST:BOOL='OFF' -DMPI_RC2_TEST:BOOL='OFF' \ -DMPI_RC_TEST:BOOL='OFF' -DMPI_TEST:BOOL='OFF' -DMPP_BUFFER_TEST:BOOL='OFF' \ -DMPP_ENV_TEST:BOOL='OFF' -DMPP_INFO_TEST:BOOL='OFF' -DMPP_LOG_TEST:BOOL='OFF' \ -DMPP_MEM_TEST:BOOL='OFF' -DMPP_PACKET_TEST:BOOL='OFF' -DMPP_PLATFORM_TEST:BOOL='OFF' \ -DMPP_TASK_TEST:BOOL='OFF' -DMPP_THREAD_TEST:BOOL='OFF' -DVP9D_TEST:BOOL='OFF' \ -DVPU_API_TEST:BOOL='OFF' .. 
make -j$THREADS
sudo make install

ffmpeg build:
 

./configure --prefix=/usr --enable-gpl --enable-version3 --enable-nonfree --enable-static --enable-gmp \
        --enable-gnutls --enable-libass --enable-libbluray --enable-libcdio --enable-libfdk-aac \
        --enable-libfreetype --enable-libmp3lame --enable-libtheora --enable-libvorbis --enable-libx264 \
        --enable-libxcb --enable-opencl --enable-libdrm --arch='armv8-a+crc+crypto' \
        --cpu='cortex-a72.cortex-a53' --enable-rkmpp --enable-lto --enable-hardcoded-tables \
        --disable-debug
make -j$THREADS
sudo make install
sudo ldconfig

error:

sudo ffmpeg -benchmark -vcodec h264_rkmpp -i demo.mkv -f null -
ffmpeg version 4.2 Copyright (c) 2000-2019 the FFmpeg developers
  built with gcc 9.1.0 (GCC)
  configuration: --prefix=/usr --enable-gpl --enable-version3 --enable-nonfree --enable-static --enable-gmp --enable-gnutls --enable-libass --enable-libbluray --enable-libcdio --enable-libfdk-aac --enable-libfreetype --enable-libmp3lame --enable-libtheora --enable-libvorbis --enable-libx264 --enable-libxcb --enable-opencl --enable-libdrm --arch=armv8-a+crc+crypto --cpu=cortex-a72.cortex-a53 --enable-rkmpp --enable-lto --enable-hardcoded-tables --disable-debug 
  libavutil      56. 31.100 / 56. 31.100
  libavcodec     58. 54.100 / 58. 54.100
  libavformat    58. 29.100 / 58. 29.100
  libavdevice    58.  8.100 / 58.  8.100
  libavfilter     7. 57.100 /  7. 57.100
  libswscale      5.  5.100 /  5.  5.100
  libswresample   3.  5.100 /  3.  5.100
  libpostproc    55.  5.100 / 55.  5.100
Input #0, matroska,webm, from 'demo.mkv':
  Metadata:
    COMPATIBLE_BRANDS: iso6avc1mp41
    MAJOR_BRAND     : dash
    MINOR_VERSION   : 0
    ENCODER         : Lavf58.29.100
  Duration: 00:05:13.80, start: -0.007000, bitrate: 2887 kb/s
    Stream #0:0: Video: h264 (High), yuv420p(tv, bt709, progressive), 1920x1080 [SAR 1:1 DAR 16:9], 29.97 fps, 29.97 tbr, 1k tbn, 59.94 tbc (default)
    Metadata:
      HANDLER_NAME    : ISO Media file produced by Google Inc.
      DURATION        : 00:05:13.780000000
    Stream #0:1(eng): Audio: opus, 48000 Hz, stereo, fltp (default)
    Metadata:
      DURATION        : 00:05:13.801000000
mpi: mpp version: 
hal_h264d_api: Assertion vcodec_type & ((0x00000200) | (0x00000001) | (0x00000002)) failed at hal_h264d_init:119
hal_h264d_api: hal_h264d_init hard mode error, value=0
hal_h264d_api: Assertion 0 failed at hal_h264d_init:169
mpp_device: mpp_device_init failed to find device for coding 0 type 7
hal_h264d_api: p_hal->vpu_socket <= 0
mpp_hal: mpp_hal_init hal h264d_rkdec init failed ret -2
mpp_hal: mpp_hal_init could not found coding type 7
mpp_dec: mpp_dec_init could not init hal
mpp_rt: NOT found ion allocator
mpp_rt: found drm allocator
mpp: error found on mpp initialization
mpp: WARNING: setup buffer group before decoder init
mpp: command 310002 param 0xaaab0831a360 ret -1
[h264_rkmpp @ 0xaaab0833b720] Failed to assign buffer group (code = -1)
[h264_rkmpp @ 0xaaab0833b720] Failed to initialize RKMPP decoder.
Stream mapping:
  Stream #0:0 -> #0:0 (h264 (h264_rkmpp) -> wrapped_avframe (native))
  Stream #0:1 -> #0:1 (opus (native) -> pcm_s16le (native))
Error while opening decoder for input stream #0:0 : Unknown error occurred
bench: maxrss=23880kB