Orange pi: Difference between revisions

From 太極
Jump to navigation Jump to search
 
Line 1: Line 1:
= Orange Pi 5 family =
[https://liliputing.com/orange-pi-5-ultra-is-an-rk3588-single-board-pc-with-hdmi-input/ Orange Pi 5 Ultra is an RK3588 single-board PC with HDMI input]
= Orange pi 5 plus =
= Orange pi 5 plus =
* [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/details/Orange-Pi-5-plus.html Orange Pi 5 Plus (4GB/8GB/16GB)]
* [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/details/Orange-Pi-5-plus.html Orange Pi 5 Plus (4GB/8GB/16GB)]

Latest revision as of 13:31, 3 December 2024

Orange Pi 5 family

Orange Pi 5 Ultra is an RK3588 single-board PC with HDMI input

Orange pi 5 plus

Booting from eMMC

  • Enable to boot from eMMC is more convenient since it asks to clear SPIflash. Therefore, we can easily to switch to boot from eMMC or SD card.
    • By default SD card has a higher priority to boot than eMMC.
    • I can use eMMC as the main OS storage and use SD card to play with different OSs.
    • Even I follow the instruction to use RKDevTool to put a Linux image onto eMMC, I still cannot boot from eMMC until I clear SPIflash.
    • eMMC is /dev/mmcblk1, speed is 271 MB/s (sudo hdparm -t --direct /dev/mmcblk1p2 )
    • SD is /dev/mmcblk0, speed is 62 MB/s (sudo hdparm -t --direct /dev/mmcblk0p2 )
  • From Linux
$ ls -l /dev/mtdblock0
brw-rw---- 1 root disk 31, 0 Dec 10 06:00 /dev/mtdblock0
sudo dd bs=1M if=/dev/zero of=/dev/mmcblk1 count=1000 status=progress
sudo sync

sudo dd bs=1M if=Orangepi5plus_x.x.x_debian_bullseye_desktop_xfce_linux5.10.110.img \
  of=/dev/mmcblk1 status=progress
sudo sync
  • If you want to boot from eMMC on the Orange Pi 5 Plus, you would need to clear the /dev/mtdblock0 partition. This is because the /dev/mtdblock0 partition typically contains the bootloader, and clearing it allows you to install a new bootloader that can boot from the eMMC.
    • Here is a general guide on how you can do this: Boot Armbian from an SD card.
    • Clear the SPI flash memory by running the following command in the terminal: sudo dd if=/dev/zero of=/dev/mtdblock0 bs=1M count=1

Booting from NVME

SPI flash, non-volatile memory

  • Prime for SPI flash
    • SPI Flash in a Single Board Computer (SBC) refers to a type of flash memory that uses the Serial Peripheral Interface (SPI) for communication. This is a common type of non-volatile memory used in SBCs and other embedded systems.
    • Many embedded systems, including SBCs, use non-volatile memory to store boot code, configuration parameters, and other data that persist when the system is powered down. Common Flash technologies include Parallel or SPI NOR flash, SLC NAND, and eMMC devices.
    • In the context of system booting, the processor starts executing at the reset vector and attempts to execute the first code. Some processors have a small internal boot ROM that can be programmed at manufacturing time. The boot ROM can also detect where the bootloader was stored; for example, in an external NOR or NAND flash device.
    • If a NOR Flash device is used to store the bootloader, the processor can directly run off the Flash device. This method is commonly called eXecute In Place (XIP). If a NAND or eMMC device is used, boot code first needs to be copied to the system’s RAM. Then the processor can jump to the RAM space and execute. This method is called shadowing or Store-and-Download (SnD).
    • For example, the ROCKPro64 SBC has a 128Mbit SPI Flash, and the Odroid N2+ SBC features an 8MB SPI flash with a boot select switch and Petitboot app.
  • Orange Pi 5 
    # Put Armbian onto SD card
lsblk
sudo dd if=/dev/zero of=/dev/sdd bs=4M count=5
sudo sync
sudo dd if=Armbian*.img of=/dev/sdd bs=1M status=progress
sudo sync
lsblk
sudo eject /dev/sdd
lsblk

# Back up img files to a flash drive
sudo dd if=/dev/zero of=/dev/sdc bs=4M count=5
sudo sync
sudo fdisk /dev/sdc  # g, n, ENTER, ENTER, ENTER, w
sudo sync
sudo mkfs.ext4 /dev/sdc1
sudo sync
lsblk
mkdir hey
sudo mount /dev/sdc1 hey
sudo cp *.img hey/
sudo umount /dev/sdc1
sudo eject /dev/sdc

# Mount a flash drive, back up SPI firmware (optional)
lsblk
mkdir hey
sudo mount /dev/sda1 hey
cd hey
lsblk
sudo dd if=/dev/mtdblock0 of=orangepi5_SPI.img status=progress
sudo sync
sudo cp /usr/lib/linux-u-boot-legacy-orangepi5_23.05.0-trunk_arm64/rkspi_loader.img ./
sync

# Upgrade SPI
sudo dd if=rkspi_loader.img of=/dev/mtdblock0 status=progress
sudo sync
lsblk # look at the size of mtdblock0
    At this point, we are ready to put images (Batocera, Orange Pi OS (Droid)) onto nvme
    lsblk
sudo dd if=/dev/zero of=/dev/nvme0n1 bs=4M count=5
sudo sync
sudo dd if=batocera.img of=/dev/nvme0n1 bs=4M status=progress
sudo sync
    • How to install Android to Nvme. Orange Pi 5 5/19/2023. SPIflashTool. Boot Orange Pi OS (Droid) from NVME Ok. Boot Debian from NVME failed. Boot Armbian from SD. Run armbian-config - install/update boot loader on MTD flash. Remove SD. Boot Debian from NVME worked. Switch to Orange Pi OS (Droid) but failed. If you flash the MTD with the boot loader of a specific Linux distro, it won't work with another distro (or android for that matter).
    startx # not found, a hint was given to run 'apt install xinit'
sudo apt install xinit  # Choose ssdm
sudo reboot
    • My experience: suppose my NVME has Debian image from Orange Pi. I booted Armbian ubuntu legacy. Use armbian-config - System - Install - Install/Update the bootloader on MTD Flash. Now I can boot from NVME if there is no SD card or boot from SD card if there is no NVME.

LEDs

Onboard LED Light Test Instructions

Android OS

  • Orange Pi 5: Retroarch for Android 12 Basic Tutorial.
    • Download and install the 64bit apk from retroarch.com.
    • Open the "Files" app. There is a folder "RetroArch" created under the main folder (parallel to Alarms, Android, DCIM, Documents, Download, ...). Create a new directory called 'Roms' under RetroArch. Go ahead and create different folders for different game systems; e.g. NES, PS1, SNES. Ctrl +c/ Ctrl+v works under the "Files" app.
    • Open RetroArch again. Set up the controller under Settings: Port 1 controls. Press and hold a button. Then set up hotkeys (Menu Toggle). A = go back.
    • Import content. Box arts will be downloaded automatically.
    • Load Core. Download a core. PS (PCSX-reArmed). NES (NES/Famicon Nestopia UE), SNES (SNES/SFC Snes9x 2005), N64 (Mupen64plus - Next GLES2)
    • Select+Start to go to a quick menu.
    • Files app -> RetroArch -> System (place bios files).

Batocera

  • Batocera on an Orange Pi 5 Plus. Sound will come out from 3.5mm, not HDMI.
  • Orange Pi 5 SBC Review and Test 3/29/2023. The description part of the video has lots of links to different tests/tutorials.
    • The first boot of Batocera may take 5-10 minutes.
    • We can use any file manager and go to the IP of Orange Pi running Batocera. From there we may copy bios/roms to Batocera (batocera/share/{bios,roms}).

Armbian

  • Orange Pi 5 Plus review with Armbian (4k) 12/13/2023
    • How to build armbian
    • Use 'Disks' utility to write an image to SD card
    • Setting - Audio - 'Analog Output - HDMI0 Audio'. For some reason, this does not work. But after I inserted a USB audio adapter, that adapter worked right away and for some reason from now on the audio from HDMI0 works. Note in Armbian, the HDMI audio options are HDMI0 and HDMI1. HDMI0 is located between HDMI1 and HDMI-in on the board. The setting will be lost after we reboot Armbian.
    • Game testing
    • box64 was used to run x86_64 Linux programs (such as games) on non-x86_64 Linux systems, like ARM. H-craft, Colin McRae Rally, GTA3.
    • wine, TrackMania Nations Forever
    • RetroPie/emulationstation

Ubuntu by Joshua Riek

https://github.com/Joshua-Riek/ubuntu-rockchip/releases.

JELOS

Windows

UEFI

Tips

Retrieved from "https://wiki.taichimd.us/index.php?title=Orange_pi&oldid=40739"