Files
UniXNU/docs/devices/orangepi5.md
2026-11-10 14:20:18 +00:00

134 KiB

Orange Pi 5 (Rockchip RK3588S)

Ken-u/UniXNU-orangepi5

Orange Pi 5 (Rockchip RK3588S) with an HDMI display and an M.2 NVMe drive, running the iPadOS 17.7.11 userland on a source-built XNU, started from edk2-rk3588 firmware (uefi-orangepi5). Shared SoC support is in UniXNU-rk3588-common, which the EVB10 port already proved on hardware. Observed on the board (2026-11-03..05): U-Boot starts the firmware from the NVMe ESP; NVMe root and persistent Data mount; SpringBoard and Mali Metal compose over HDMI0 through the shared RK3588 VOP2 direct scanout (iommu paging, no CPU GOP copy). Network and audio drivers are not started yet; DVFS is not hooked; physical USB input is not brought up (a software HID digitizer stand-in is linked).

Source record: porting.toml, 729ba25f4d67225ff3853ba1e435b95af97e59e3.

This page is generated from the device record.

Area Status
Configuration host-verified
Firmware and boot device-verified
CPU and interrupts implemented
Memory and DMA device-verified
Storage and root device-verified
Display device-verified
Input device-verified
GPU device-verified
Network device-verified
Audio planned
Power implemented
Image assembly device-verified
Diagnostics device-verified

Configuration

host-verified

Hardware and dependencies

  • ARM64 profile, rk3588 SoC source pinned in feeds.toml, iPadOS 17.7.11 build 21H461 profile, orangepi5_defconfig.

Configuration

  • board.soc_source = rk3588; board.os_profile = ipados-17.7.11-21H461; schema_version = 2.
  • orangepi5_defconfig is the console kernel with NVMe storage and the Mali driver linked (inert without mali=N): no display, no RAM disk, no UFS; orangepi5_display_defconfig, the configuration of the image, adds CONFIG_XNU_NATIVE_LEGACY_DISPLAY=y and the link stubs (scripts/build-orangepi5-kernel.sh builds the two in that order); the trust-cache runtime and the code-signing hash cache stay on.
  • [adt.defaults.u32] carries sleep-disabled = 1 and vmm-present = 1, which the EVB10 port found necessary for watchdogd.

Procedure

  • From the UniXNU checkout run ./unixnu defconfig orangepi5_defconfig -D ../UniXNU-orangepi5, then ./unixnu fetch, ./unixnu status --json and ./unixnu tree with the same -D.
  • scripts/build-orangepi5-kernel.sh runs the kernel build; it needs the environment of the machine that builds (.env) and CMake 3.19.6 or newer.

Development findings

  • Resolution is host-verified: defconfig, fetch, status --json and tree complete against the pinned SoC repository.
  • The UniXNU bootstrap pass builds AvailabilityVersions with CMake; the distribution CMake of Ubuntu 20.04 is 3.16 and fails, so the build script puts /usr/local/bin first.
  • The kernel now carries the NVMe driver: board.toml archives build-orangepi5-drivers.py Rk3588Nvme and bind-nvme-storage.py, the defconfig force-loads libRk3588Nvme.a, and the build script verifies the bound addresses against the kernel (18 addresses inside the audited IOStorageFamily).
  • board.toml [userdata] is the layout of the 128 GB drive: userdata at LBA 526336..134744063 behind a 256 MiB ESP at LBA 2048; the boot arguments are the EVB10 ones with the storage names of the NVMe driver (nvme=4, nvme-root-trust=1, nvme-data-size=2048, nvme-data-persist=1).
  • board.toml payload.dram_size and payload.adt.owned_memory_size are 0xF8000000 (3.875 GiB, in the 4 GiB bank at 0x100000000) now, the window measured on the board (memory area, evidence/device-memory-20261103.txt); the old 4 GiB and 2 GiB values were EVB10 placeholders.
  • The kernel is built in two passes now and carries the GOP-backed legacy display (board.toml archive build-orangepi5-display.py, component GopFramebuffer, the offline-legacy-* and sheng-* arguments; evidence/host-display-build-20261103.txt) and the Mali-G610 driver (archives build-mali-firmware.py and build-orangepi5-drivers.py Mali, libMali.a force-loaded by both defconfigs, no mali argument in the list; evidence/host-gpu-build-20261103.txt). Both link on the host.
  • board.toml now defaults mali=8 mali-metal=1 evb10-gpu-addon=1, rk3588-vop-direct=1 with esmart=2/vp=2/fence=1, opi5-hid-input and sheng-touch-hid, and thin-bezel=1; feeds.toml pins UniXNU-rk3588-common at b5f5d94 (Rk3588VopDirect). Observed on the board with that list (evidence/device-vop-direct-20261105.txt).
  • board.toml now also defaults rk3588-dvfs=6 and opi5-usb=5 (DVFS governors + OHCI HID) and rk3588-gpu=0 (GPU governor off, see the power area); the kernel argument list is 772 bytes.
  • board.toml also defaults mali-wallpaper-fit=1 (the Metal plugin fits the disc-shaped lock screen wallpaper to the 16:9 panel; gpu area, evidence/device-wallpaper-20261105.txt); the kernel argument list is 793 bytes.
  • board.toml boots with mali-sched-wait=2 (811 bytes of kernel command line): ten of ten SplashBoard launch pictures whole in two boots, two to four bad of five without it (evidence/device-snapshots-20261106.txt, runs d28-d34).
  • board.toml builds build-rk3588-vdec.py (the SoC repository's Rk3588Vdec archive with this board's DMA window, package/Rk3588VdecBoard.cpp); no boot argument was added to the defaults: the video decoder self-test runs only with rk3588-vdec=N (docs/media.md, evidence/device-vdec-20261107.txt).
  • board.toml builds build-rk3588-venc.py (the SoC repository's Rk3588Venc archive with this board's DMA window, package/Rk3588VencBoard.cpp, force-loaded by orangepi5_display_defconfig); no boot argument was added to the defaults: the video encoder self-test runs only with rk3588-venc=N (docs/media.md, evidence/device-venc-20261108.txt).
  • feeds.toml pins the SoC repository at 7281615, which has the AppleAVE2 service of the encoder archive (boot argument rk3588-venc-ave2=N, not in the defaults; it logs the calls, answers Start with kernel-made IOSurfaces and four frames in flight, and dumps the first YUV requests; docs/media.md, evidence/device-ave2-abi-20261108.txt).
  • feeds.toml pins the SoC repository at c0b78e3, which has the encoder core for H.264 and H.265 behind the AppleAVE2 service (boot arguments rk3588-venc=6 and rk3588-venc-ave2-encode=2, not in the defaults; its core/ compiles 63 files of the pinned MPP and takes two more by #include, fetched by tree hash and never copied into a repository; docs/media.md, evidence/device-venc-core-20261109.txt, evidence/device-venc-core-h265-20261109.txt).

Completion criteria

  • Every source pin resolves, ./unixnu status lists the intended patch order, and the defconfig materialises.

Current limits

  • Network and audio still have no driver; the GPU governor is off by default; a keyboard is not attached yet; the default menu entry is still xnu-probe.

Next action

  • DEFAULT_ENTRY=xnu MENU_TIMEOUT=3 rewrite of esp.img; Ethernet or Wi-Fi.

Evidence

Firmware and boot

device-verified

Hardware and dependencies

  • edk2-rk3588 firmware built by uefi-orangepi5 (an SPI NOR image with TF-A at EL3, OP-TEE and the UEFI volume, or the UEFI volume alone as a launcher image), UEFI GOP frame buffer on HDMI0.
  • A U-Boot in the SPI NOR supplied by the board's owner. Reported from its console (not observed from here): kernel_addr_r=0x00400000, fdt_addr_r=0x08300000, boot_targets=mmc1 mmc0 nvme scsi usb pxe dhcp spi, and a working ums.

Configuration

  • board.toml has no [firmware] section: the unixnu firmware step builds Mu-Silicium, and this board boots edk2-rk3588 built by uefi-orangepi5.
  • payload.loader = firmware: DarwinBoot is inside the firmware volume and reads the payload from the ESP of the NVMe drive, found through NvmExpressDxe.
  • The board has no SD card, so the firmware is not flashed: boot.scr on the ESP makes U-Boot load uefi-launcher.img (a stub with the volume inside) at 0xa000000 and booti it; the stub copies the volume to 0x200000 and jumps to its reset vector target (0x1400) at EL2. The volume is built with RK_NOR_FLASH_ENABLE=FALSE (build.sh -L), so edk2 does not write the SPI that holds U-Boot.

Procedure

  • Build the volume (uefi-orangepi5 build.sh -L), the bundle (tools/board/make-bundle.sh puts uefi-launcher.img and boot.scr on the ESP) and the disk files (tools/board/make-disk-image.sh). Put the drive on a Mac with U-Boot's ums, write head.img, tail.img, the zeroed Data header and esp.img with dd, then power-cycle: U-Boot runs boot.scr. With an SD card the firmware can go into the SPI NOR instead (tools/board/spi-flash.sh, Maskrom when /proc/mtd does not list the flash). All of it is in uefi-orangepi5/docs/first-boot.md.

Development findings

  • Observed on the board (evidence/device-first-boot-20261103.txt, sections 1 to 3 and 6): the SPI NOR U-Boot (v5-gc507c92ef837-261013) scans the NVMe, finds /boot.scr and runs it; the stub copies the volume to 0x200000 and jumps to 0x1400 at EL2 (booti left it where it was loaded); the UEFI banner follows 0.04 s after the jump; the firmware reports 4 x 2048 MB = 8192 MB of RAM, brings the PCIe link up again after U-Boot used the drive (x1, 2.5 GT/s), reads kernel.macho and its companions from the ESP of the NVMe drive, and DarwinBoot hands the kernel over with the GOP frame buffer 0xE7AC0000 (640x480, row 2560). The device tree U-Boot hands over reaches edk2 as x0 (one harmless 'Bad transfer list signature 0xEDFE0DD0' line).
  • The board's U-Boot counts the entries of a script image up to a word of 0xffffffff, not up to 0 as mkimage writes: boot.scr as mkimage writes it printed "Unknown command '<garbage>'" because the text was taken from behind the end of the file. With [length, 0xffffffff] as the size table iminfo lists one image and source runs the text (checked with small images in RAM, then with the real boot.scr, which now starts the launcher by itself, also after the restart that follows a kernel panic). tools/board/make-bootscr.py writes that by default and --table-end 0 gives the mkimage layout.
  • The UniXNU menu takes keys from the serial port: serial-capture.py --send 'menu: shown' text:1 picked the xnu entry (menu: key 1, booting 0) in the 10 s countdown.
  • HDMI0 shows the kernel log: the xnu-hdmi entry (vc_mirror=1) copies it to the GOP frame buffer (video base 0xE7AC0000, 640x480, row 2560) and the person at the board saw text scrolling on the monitor (evidence/device-hdmi-watchdog-20261103.txt; not photographed, so colours, position and readability are not recorded). The xnu and xnu-probe entries leave the monitor black after the menu, as designed.
  • A kernel panic restarts the board at once (the next U-Boot banner 0.97 s after the panic line); the hardware watchdog path was run once: after the kernel's wdt-kick feeder stopped (1800 s), the board was reset and ran by itself again, the adapter dropping off the bus at 11:49 (the 89 s were due 11:49:33). The reset itself was not seen on the serial line, so that it was the watchdog is an inference from the time. The launcher arms the DW watchdog, UniXNUBootWdtDxe takes over, and the kernel's wdt-kick feeder kept the board up for the 400 s from the hand-off to the end of the xnu capture.
  • The firmware builds on the host with the GPU rail set to 0.75 V and the hardware watchdog driver of uefi-orangepi5 armed (the board has no remote power switch, so a hung kernel must end in a watchdog reset).
  • The firmware image is a bundle member (nor.img) built by uefi-orangepi5 tools/board/make-bundle.sh; spi-flash.sh was checked for its /proc/mtd parsing only, it has not touched a flash.
  • Host-verified for the launcher: the stub's instructions are identical to the EVB10 stub that ran on a board (only strings and the text_offset field differ); the entry offset read from the volume's reset vector is 0x1400 for the EVB10 and both Orange Pi 5 volumes; boot.scr written with --table-end 0 is byte for byte what mkimage -T script writes; the ESP with both files passes fsck.vfat and reads back identical; make-disk-image.sh runs nvme-install.py with read-back into a 128 GB sparse file.
  • The ESP can be updated from the serial console, with no second computer: at the U-Boot prompt uboot-put.py (UniXNU-rk3588-common tools/board) sends a file with YMODEM, fatwrite puts it on the ESP, fatload and crc32 read it back (all numbers hex). uefi-launcher.img (5251560 bytes) takes about 40 s at 1.5 Mbaud; the launcher, kernel.macho.adt and unixnu.toml were replaced that way for the memory runs and verified by crc32 (evidence/device-memory-20261103.txt, section 7). The firmware logs its UEFI memory map (UniXNUMemMapDxe, uefi-orangepi5 e35d303) before the menu and at ExitBootServices.
  • Two firmware fixes came out of the memory work (uefi-orangepi5 dc08d7c and e1ac136; memory area, evidence/device-memory-20261103.txt, sections 5 and 6): the ACPI tables are linked with -Wl,--sort-section=name so the table, not clang's ReferenceAcpiTable pointer, is first in Pptt.acpi (observed on the board: all eight tables install, the 'Couldn't locate ACPI DSDT' line is gone, no more AcpiTableDxe abort in the builds that had one) and PcdImageLargeAddressLoad is FALSE (RtkUndiDxe loads at 0xE7CFB000 instead of its linked 0x180000000).

Completion criteria

  • Firmware enters DarwinBoot, publishes the GOP frame buffer and finds the NVMe ESP.

Current limits

  • The HDMI picture is a text mirror only (no display driver; the monitor was reported as scrolling text, nothing more); the SPI NOR route (nor.img) has not run; the U-Boot is the owner's build, known by its console, its environment and what it did in the runs above.
  • The first runs started from the U-Boot prompt by 'reset' typed on the serial console; a power-on from cold (BootROM to U-Boot) is the same path but was not captured.
  • The USB serial adapter drops off the bus at every board reset and returns under another name; captures need its /dev/serial/by-id path (BOARD_SERIAL_DEV).

Next action

  • Capture the watchdog reset on a line that survives it (by-id path) to confirm the 89 s; once the runs are good, make xnu the default (DEFAULT_ENTRY=xnu MENU_TIMEOUT=3 tools/board/make-bundle.sh) and write the new esp.img.

Evidence

CPU and interrupts

implemented

Components: ArmCpu, ArmDTPlatform.

Hardware and dependencies

  • Four Cortex-A55 and four Cortex-A76 at affinities 0x000 to 0x700, GICv3 at 0xfe600000, 24 MHz architected timer, PSCI over SMC: the same cluster layout and GIC as the EVB10, since the RK3588S is the RK3588 without some interfaces.

Configuration

  • The CPU, GIC and PSCI nodes come from the SoC dtsi (rk3588-common dts/rk3588.dtsi); the board DTS enables nothing extra.
  • Kernel arguments sheng-smp=1, armcpu-self-ipi=1, armcpu-mmio-sgi=0 and cpumask=31 are the ones of the EVB10 port.

Procedure

  • Compile dts/orangepi5.dts through ./unixnu tree and inspect /cpus, /psci and /arm-io/intc in the generated device tree.
  • Boot and read the per-core entry lines on the serial console.

Development findings

  • The CPU path is shared with the EVB10 and unchanged here; the EVB10 record documents the EL2 to EL1 drop of secondary cores and the Darwin assembler caveat.
  • Whether the Orange Pi 5 firmware leaves the same state is not yet observed.

Completion criteria

  • Every enabled core reaches its entry checkpoint and receives timer and inter-processor interrupts.

Current limits

  • No CPU frequency governor yet; the DVFS rail table of the EVB10 (RK8602 at I2C0 0x42 and 0x43, RK806 BUCK1 and BUCK2) matches the Orange Pi 5 and will be reused with the power area.

Next action

  • Boot the console kernel and compare the per-core lines with the EVB10 log.

Evidence

Memory and DMA

device-verified

Hardware and dependencies

  • The board of this port has 8 GiB of LPDDR4x. The firmware (edk2-rk3588 as built by uefi-orangepi5) maps it as the lower bank below 0xf0000000 (3.75 GiB, cut by OP-TEE, TF-A and the firmware's own allocations) and the 4 GiB bank from 0x100000000; U-Boot also reports 256 MiB at 0x2f0000000 that edk2 does not map.

Configuration

  • payload.adt.owned_memory_size = 0xF8000000 (3.875 GiB): DarwinBoot takes that many contiguous bytes from one run of free memory of the UEFI map, first fit. With the firmware as built here that is the 4 GiB run at 0x100000000: the window is pa 0x10007C000 to 0x1F807C000 and 127 MiB of the run stay free behind it.
  • The memory node of dts/orangepi5.dts (memory@100000000, 3.875 GiB) and payload.dram_size = 0xF8000000 follow the window; the kernel does not read the node.
  • Firmware side (uefi-orangepi5): the link order of the ACPI tables (dc08d7c) and PcdImageLargeAddressLoad = FALSE (e1ac136), which keep the 4 GiB bank in one piece; without them the longest run is 2.6 GiB.

Procedure

  • Read the memory map the firmware prints (UniXNUMemMapDxe: before the menu and at ExitBootServices) and take the largest run of free memory (4096 MiB at 0x100000000 on this firmware); set owned_memory_size below it with margin (2 MiB steps), rebuild the payload (REBUILD=1 tools/board/make-bundle.sh) and write kernel.macho.adt to the ESP (through U-Boot: uboot-put.py, fatwrite, crc32). DarwinBoot prints 'boot refused: Out of Resources' when no run is long enough, and the UniXNU menu then waits for a key (5 restarts the board).

Development findings

  • Observed with the firmware as first built (evidence/device-memory-20261103.txt, section 1): free runs 0x7F0000 + 124 MiB, 0x9400000 + 849 MiB and 0x40000000 + 2674 MiB (the largest, up to 0xE72DA000) in the lower bank, 0x100000000 + 2048 MiB and 0x180024000 + 2047 MiB above it.
  • The upper bank was cut at 0x180000000 by RtkUndiDxe.efi (prebuilt Realtek UNDI driver of edk2-non-osi, ImageBase 0x180000000, 0x24000 bytes): DxeCore loads an image at its linked address when that is free because PcdImageLargeAddressLoad is TRUE (host reading of the PE header and of Image.c; the log shows the load at 0x180000000). So no run above 4 GiB was longer than 2 GiB, and window requests of 3.5 GiB (0xE0000000) and of sizes between 2.75 and 3 GiB were refused ('DARWINBOOT: boot refused: Out of Resources'); 2.5 GiB (0xA0000000) booted (memC, memH, memI: pa 0x4007C000, 626169 to 626173 free pages against 497587 with the 2 GiB window, launchd 'Early boot complete' 30 s after the hand-off, no panic in 400 s; section 4).
  • The two ways tried to get the upper bank in one piece (-D NETWORK_ENABLE=FALSE; PcdImageLargeAddressLoad=FALSE) stopped the firmware before the menu with a data abort in AcpiTableDxe (FAR 0xFFFFFFF0, 0xAFAFAFAF in the registers; memG, memJ). Cause of the broken ACPI install, found on the host (section 5): Pptt.aslc compiled with clang has an 8-byte ReferenceAcpiTable pointer in .data.rel.ro in front of the table in .data, GenFw -c copies the sections in the order the linker gives, so Pptt.acpi began with 8 stray bytes; the firmware read a sixth table with a garbage signature and length 0, its install failed, SPCR and DSDT were never installed. Linking the ACPI tables with -Wl,--sort-section=name puts the table first (reproduced by hand: the first bytes are 'PPTT' with the flag, 40 02 00 00 00 00 00 00 'PPTT' without). Observed after dc08d7c: all eight tables install (memK); the memJ configuration (PcdImageLargeAddressLoad=FALSE, window 0xE0000000) plus the fix no longer aborts (memL). Which line of AcpiTableDxe reads the freed memory was not traced; the memG build was not repeated with the fix.
  • With both firmware changes the 4 GiB above 0x100000000 is one run of 4096 MiB (memL map, section 6) and the kernel boots from a window there: 3.5 GiB (memL: pa 0x10007C000, 884604 free pages), 4094 MiB (memM: 1013320 free pages) and the committed 3.875 GiB (memN: pa 0x10007C000, args 0x1040C4000, 981518 free pages, 3968 MiB 'loader code' run with 127 MiB free behind it); each reaches launchd 'Early boot complete' 30 s after the hand-off with no panic, for 150 s (memL, memM) and 400 s (memN) of feeding. The kernel has run above 4 GiB on this port since memL.
  • The ADT generator takes one range and DarwinBoot one window, and nothing in the kernel sources of this tree reads dram-base or dram-size from /chosen (host reading), so the lower bank (3.75 GiB, 2.6 GiB free) and the upper one cannot both be given to the kernel; the 256 MiB at 0x2f0000000 are not mapped by edk2.

Completion criteria

  • The kernel reports the memory it owns and the ADT memory ranges match the firmware map.

Current limits

  • The kernel owns 3.875 GiB of the 8 GiB: the lower bank (3.75 GiB, 2.6 GiB of it free) and the 256 MiB at 0x2f0000000 are unused (one window, one ADT range).
  • The window leaves 127 MiB in the run. A firmware change that splits the upper bank again (a prebuilt driver with a fixed load address, PcdImageLargeAddressLoad back to TRUE) makes DarwinBoot refuse the boot and the board waits in the menu for a key; the MEMMAP lines show the runs before the menu.
  • Which of the captures memA, memB, memD and memE had which size was not written down; the refusals and the sizes tried are recorded, the pairing is not.
  • SpringBoard did not start in the longest run (memN, 400 s), so the effect of the larger window on the later boot was not measured. The committed unixnu.toml itself (default entry xnu-probe, wdt-kick=1800) was not booted with this window: memN used entry xnu and wdt-kick=400.

Next action

  • None for the window itself. Watch the MEMMAP lines whenever a firmware driver is added or a PCD changes, and test that the contents of Data survive a reboot (storage area).

Evidence

Storage and root

device-verified

Components: AppleKeyStoreState.

Hardware and dependencies

  • M.2 M-key slot on PCIe 2.0 x1 (pcie2x1l2 through combphy0_ps, reset GPIO3_D1, 3.3 V enable GPIO0_PC5), a 128 GB NVMe drive for the ESP, the root image and the Data volume; the eMMC socket and the microSD slot are left unused.

Configuration

  • board.toml [userdata]: an ESP of 256 MiB at LBA 2048 and a 64 GiB userdata partition at LBA 526336..134744063, with the OS and SystemOS windows at its start and the Data window (1 MiB header + 2 GiB container) at its end.
  • dts/orangepi5.dts exports /arm-io/pcie-nvme (compatible unixnu,rk3588-pcie-nvme, no reg, no interrupts) and keeps the pcie@fe190000 node disabled; patches/xnu/orangepi5-nvme-personality.patch matches NativeNvme to it.
  • Boot arguments nvme=4, nvme-root-trust=1, nvme-data-size=2048, nvme-data-persist=1; probe-only runs use nvme=1.

Procedure

  • Write GPT, ESP (payload) and userdata to the drive with uefi-orangepi5 tools/board/nvme-install.py from a Linux booted on the board, then boot; the driver publishes the OS and SystemOS windows read-only and the Data window writable.

Development findings

  • package/Rk3588Nvme follows the EVB10 eMMC driver above the controller (GPT scan, SHNGROOT root image, Data window, kernel hooks, watchdog feeder, PMGR nub) and has its own host: PCIe bring-up from the state edk2-rk3588 leaves, a polled NVMe controller core (reset, admin queue, identify, one I/O queue pair, PRP transfers through a contiguous bounce window, writes only inside the Data window).
  • Host-verified: the NVMe core and the GPT reader against a controller model behind a non-coherent cache (seven mutations of the core are caught), the root manifest reader, the BAR window classification (four mutations caught), the driver compiled with -Werror and bound to the original IOBlockStorageDevice (190 slots, 11 imports), the kernel link and its bound-address check, and the installer's GPT through the driver's own reader.
  • Observed on the board (evidence/device-first-boot-20261103.txt, sections 4 and 6): the PCIe controller addresses derived from the sources of edk2-rk3588 are right (APB 0xfe190000, DBI 0xa41000000, CFG0 0xa36500000: vendor 0x126f device 0x2263 class 0x10802 at 00:00.0, LTSSM L0); the drive is a Silicon Motion NE-128 with 250069680 512-byte blocks; the controller is enabled as the firmware leaves it and the driver resets and initialises it; GPT and the SHNGROOT header are read; the probe reads 4096 blocks twice with the same CRC at 72 MiB/s, 0 retries, 0 failures; the OS (5796 MiB) and SystemOS (3150 MiB) windows are published and the root device is accepted; the Data window is formatted at the first boot (64 MiB zeroed, 9216 KiB seed, 534 ms) and published writable (650 write calls, 0 failures); launchd starts 29 s after the hand-off and the kernel runs the 400 s until the capture ends without a panic.
  • Found on the board and fixed (b1d3c18f): BAR0 is a 64-bit non-prefetchable BAR that edk2 places in the 32-bit window (bus 0xf0000000, CPU 0xa38000000); the first version of the driver took every 64-bit BAR for the 64-bit window and refused it. The run that carried the fix logged "BAR0 0xf0000000 (64-bit, not prefetchable) is at CPU address 0xa38000000" and everything after it worked.
  • The link: the firmware (2.5 GT/s) and the kernel (link status Gen1 x1) see Gen1 where U-Boot reported Gen2 x1 for its own link-up; the driver does not retrain the link.
  • The kernel patches of the EVB10 call two Mali hooks (mali_gpu_addon, mali_test_file); the driver defines weak versions that answer none until a display archive is linked.
  • Design debts: the storage code is duplicated between Rk3588Emmc and Rk3588Nvme (a fix to the shared parts goes into both); the headers Gpt.h, RootManifest.h and StorageCommon.h are copies with the namespace renamed; the first round keeps the 2 GiB Data container of the existing seed.
  • Second and later boots (evidence/device-memory-20261103.txt, section 8): the Data window's header is found again ('version 1 state 2 ... formatted 1 times') and Data mounts writable on /dev/disk3s1, the OS window as the read-only root, with the new ADT of the memory change (memory node memory@40000000, 2.5 GiB window); the driver does not read the memory node.
  • scripts/build-orangepi5-drivers.py also builds the display objects and the Mali driver now (components NativeLegacyDisplay, NativeGOPPresenter, NativeKeyStoreEvents, Mali); the Rk3588Nvme entry and its bind step are unchanged and the bound-address check still passes on the two-pass kernel (18 addresses inside the audited IOStorageFamily, evidence/host-display-build-20261103.txt and host-gpu-build-20261103.txt).
  • When wdt-kick expires, NativeNvme also writes CRU_GLB_SRST_FST (0xFDB9) so the board soft-resets to U-Boot if the hardware watchdog does not fire (observed while deploying the VOP kernel).
  • scripts/build-orangepi5-drivers.py gained the Opi5Usb component (a new entry in COMPONENTS); the NVMe component is unchanged and the NVMe root and Data volumes mounted in every boot of the 2026-11-05 runs (launchd reached Early boot complete, evidence/device-usb-dvfs-20261105.txt).
  • The watchdog-kick thread of the NVMe package polls the serial console: three Ctrl-C within 2 s (or the end of the wdt-kick time) make it call haltRestart(kPERestartCPU); on the board the first byte of a burst of 30 Ctrl-C (0.1 s apart, tools/board/console-reset.sh) is followed by the U-Boot prompt about 4 s later, which replaced waiting for the 89 s watchdog in every flash of the runs in evidence/device-mouse-gpu-20261105.txt.

Completion criteria

  • The kernel mounts the root and Data volumes from the NVMe drive and launchd starts.

Current limits

  • Boots after the first (hdmi3, memH, memI) found the Data window's header ('formatted 1 times') and mounted it writable without formatting; that contents written in one boot are read in the next, long write loads and the cache handling under them were not checked.
  • The probe's 72 MiB/s is below what the Gen1 x1 link can carry; whether the link or the polled bounce-window reads limit it was not measured.
  • Only 512-byte logical blocks are supported.

Next action

  • Write a marker file to Data, reboot and read it back, then measure the read speed with a larger probe (nvme-probe=N) and decide whether the link or the driver limits it.

Evidence

Display

device-verified

Components: GopFramebuffer.

Hardware and dependencies

  • HDMI0 from VOP2 (firmware VP2 + Esmart2, 1920x1080p60), the UEFI GOP frame buffer as the boot surface, monitor mode from EDID.

Configuration

  • offline-legacy-* / sheng-* bind IOMobileFramebufferLegacy to NativeLegacyDisplay (package/Opi5Display, force primary and IOMFBDisplayRefresh at sheng-vsync>=60).
  • rk3588-vop-direct=1 uses UniXNU-rk3588-common Rk3588VopDirect: VOP IOMMU identity maps compositor surfaces and Esmart2 fetches them (rk3588-vop-esmart=2 rk3588-vop-vp=2); rk3588-vop-fence=1 waits for Mali before the flip. GOP CPU blit remains the fallback when iommu init fails.

Procedure

  • Build the two-pass display kernel, esp-put kernel/ADT/unixnu.toml, boot entry xnu, read opi5: display and rk3588: vop-direct lines.

Development findings

  • Firmware HDMI0 / GOP hand-off as in evidence/device-display-firmware-20261103.txt.
  • GOP CPU copy path reached SpringBoard on the board (landscape 1920x1080) but cost about 53 ms per 8294400-byte frame.
  • Shared VOP2 direct scanout (SoC b5f5d94) fixed page-table allocation for owned RAM above 4 GiB (40-bit IOMMU PA). On the board (evidence/device-vop-direct-20261105.txt, kernel crc32 6612adcc): vop direct iommu 1, flips 24, copy fallbacks 0, CPU copies 0; SpringBoard stayed up with Mali Metal.
  • legacy_late_probe_body now also starts USB (opi5_usb_start) and the DVFS governors (rk3588_dvfs_start) before mali_start, and the display defconfig force-loads libRk3588Dvfs.a and libOpi5Usb.a; with that kernel SpringBoard still started in every boot (evidence/device-usb-dvfs-20261105.txt, serial only, nobody looked at the monitor).
  • UniXNU e2fdae4 (2026-11-06): AppleKeyStoreState wraps keys in software and needs native_aks_device_id(); package/KeyStoreProbe.cpp returns /chosen unique-chip-id + chip-id (12 bytes), and the OS asked for it 59.7 s after boot (evb10: aks: software key wrapping, device identity 12 bytes). The same run configuration as before the update gave the same launch pictures, no signal 11, no panic over 710 s (evidence/device-unixnu-update-20261106.txt).
  • LegacyDisplayProbe.cpp calls rk3588_vdec_start() after rk3588_xhci_start() and configs/orangepi5_display_defconfig force-loads libRk3588Vdec.a; without an rk3588-vdec argument the call returns at once, and the vd3 run (rk3588-vdec=4) left the display, Mali and USB lines as before (docs/media.md).
  • The display kernel also links the video encoder (libRk3588Venc.a force-loaded by orangepi5_display_defconfig, rk3588_venc_start() called from package/LegacyDisplayProbe.cpp after rk3588_rga_start()); it stays off unless rk3588-venc=N is given, and the vc4 boot (encoder test on) still shows the display working at t+660 s: swap ok 34 rej 0, 33 VOP direct flips, Mali vkpipe failed=0 (evidence/device-venc-20261108.txt).

Completion criteria

  • The kernel draws the boot screen on the HDMI monitor and SpringBoard appears.

Current limits

  • Person at the monitor has not re-confirmed the picture after the VOP switch (serial only).
  • Flips stop once the lock screen is static; fence often waits on GPU work at first swaps.
  • The governors that this probe starts run with the GPU governor off by default (power area).

Next action

  • Ask for a look at HDMI after VOP; measure frame rate under a gesture.

Evidence

Input

device-verified

Hardware and dependencies

  • No on-board digitizer; USB-A ports on OHCI companions (0xfc840000 / 0xfc8c0000); Type-C power GPIO3 PC0; USB 3 xHCI controllers at 0xfc000000 (xhci0) and 0xfcd00000 (xhci2).

Configuration

  • opi5-hid=1 loads IOHIDFamily; opi5-hid-input / sheng-touch-hid start NativeHidInput; opi5-usb=5 starts the polled OHCI host and feeds the boot-protocol keyboard and the report-protocol mouse (layout read from its report descriptor; opi5-usb-boot-mouse=1 keeps the boot protocol, which has no wheel) into NativeHidInput via native_usb_* mailbox.
  • rk3588-xhci=N (default 0, not in board.toml) starts the SoC repo's polled xHCI driver on the two DWC3 controllers with this board's table (package/Rk3588XhciBoard.cpp: registers, DMA windows 0x64000000 / 0x64100000, a HID sink into the same native_usb_* mailbox): 1 look, 2 start and watch ports, 3 enumerate, 4 hubs, 5 HID boot keyboards and mice.

Procedure

  • Boot with a USB 2.0 keyboard or mouse in a Type-A port (docs/usb.md) and read the opi5: usb: and opi5: hid: mouse lines; moving the mouse raises mouse_seq and hid_total in the poll line and the type 17 count of the event driver. Without a person: opi5-mouse-demo=SECS opi5-mouse-click=1|2|3 in the kernel arguments and a screenshot of the HDMI output.

Development findings

  • Both OHCI controllers start (rev 0x10, HcControl operational) behind powered EHCI ports; a Logitech mouse (046d:c077, low speed) on the second host (OHCI 0xfc8c0000) is enumerated, its boot interface configured and polled, and mouse reports are counted when the mouse moves (3275 and 705 in two 10 s windows; evidence/device-usb-dvfs-20261105.txt).
  • The mouse is an IOHIDDevice of its own (Generic Desktop / Mouse, not built in) and the kernel IOHIDEventDriver takes it through a personality added with gIOCatalogue->addDrivers (Transport USB, usage pairs (1,1) and (1,2), score 0x500; the DriverKit AppleUserHIDEventDriver does not start here): every report becomes a Pointer event (pers1: 1244 of 1244, real3: 10778 of 10778, type 17). A kernel-made mouse walk shows the grey iPadOS pointer on the lock screen in screenshots taken with screentools (demo1), and a person moving the mouse confirmed that it works (real3).
  • The wheel did not work because the mouse was put into the HID boot protocol (three bytes: buttons, X, Y). NativeUsb now reads the report descriptor, package/Opi5Usb/MouseReport.h finds the buttons, X, Y and wheel fields (host test tests/test-mouse-report.cpp), and SET_PROTOCOL 1 is sent: the serial shows "mouse report protocol: id -1, 4 bytes, ... wheel@24/8" and proto=1. A person moved the mouse and turned the wheel in wh10: 46 wheel counts, 46 Scroll events (type 6), 405 Pointer events for 403 reports with motion, and the person said the wheel works (evidence/device-mouse-wheel-20261106.txt).
  • Wheel counts injected by the kernel (opi5-mouse-wheel=1..5) become Scroll events but scrolled nothing on the screen in ten runs; the real wheel on the same kernel works, so the injected path only tests the kernel half and the reason is unknown.
  • The USB driver accumulates the movement of all reports between two flushes (the first version kept only the newest report of each 8 ms tick: 523 of 3086 reached handleReport). The kernel restarts the board on three Ctrl-C from the serial console (watchdog-kick thread), which the flashing loop of these runs uses (evidence/device-mouse-gpu-20261105.txt).
  • The first OHCI code could not reset the controllers (wrong register offsets) and its DMA pool in Device memory faulted in bzero; the pool is Normal non-cacheable memory below 4 GiB now (0x62000000 / 0x62010000, ml_io_map_wcomb).
  • The software digitizer stand-in remains for SpringBoard; USB keyboard and mouse reports go through the same IOHIDDevice (a boot mouse collection was added to its descriptor).
  • Scripted touch without a person (opi5-touch-script=SECS, opi5-touch-id=N; scripts/gen-opi5-touch-script.py writes the git-ignored opi5_touch_script.inc): two unlock swipes (the first after the boot is often lost, a third opens the App Switcher), dock taps open Photos, Messages, App Store, Settings and Safari, a flick Home goes Home when the finger rests 32 ms on its first point before it moves; used for the launch picture runs d20-d39.
  • An xHCI host driver (UniXNU-rk3588-common scripts/data/Rk3588Xhci, rk3588-xhci=N) is built into the display kernel, off by default. Host-verified: the driver code runs against a strict model of an xHC and its devices (5287 checks, 25 tests: enumeration and HID at every speed, hubs behind hubs, unplugging, stalls, a silent device, ring wraps, slot exhaustion; sanitizers on; seven mutations of the driver each make it fail) and the kernel builds with -Werror (evidence/host-xhci-20261106.txt). On the board both controllers reset and start with rk3588-xhci=5 (xHCI 1.10, 64 slots, 64 byte contexts, 2 ports, USB 3 on port 2; one run of 1500 s without a panic, the committed code read for 150 s) and the OHCI mouse path unchanged; nothing was plugged into either controller, so no enumeration, hub or HID traffic has run on hardware (evidence/device-xhci-start-20261106.txt). xhci2 is SuperSpeed only (its USB 2 lines go to EHCI per the edk2 ACPI table), so a USB 2 device or a USB 3 hub's USB 2 half is seen by the OHCI side, not by xHCI.

Completion criteria

  • A USB keyboard or mouse reaches IOHIDEventDriver through NativeHidInput and a pointer shows on the monitor.

Current limits

  • No keyboard was attached, a click opening an app was not checked, the wheel was confirmed by a person without a record of which screen scrolled, in which direction or how fast, and the pointer was not watched by a person after the GPU fix (the fix run had no one at the mouse); one run with a person moving the mouse had backboardd exit with signal 11 at 96 s (real3, old Mali code, cause unknown); no hubs on the OHCI side; the xHCI driver has run on hardware only as far as starting the controllers (no device was attached; which connector is on which controller is unknown); no EHCI, so high speed USB 2 devices (a USB 2 camera or hub) are not seen; polled, no interrupts.

Next action

  • Plug in a keyboard and type; click to open an app and scroll a list with a person at the mouse (note the screen and the direction); find out whether the backboardd exit of real3 comes from early pointer input; then, with a person at the board, plug a SuperSpeed device into a blue port and run rk3588-xhci=3 (then 4 with a USB 3 hub), and find the connector of xhci0 for rk3588-xhci=5 with a keyboard or mouse.

Evidence

GPU

device-verified

Components: GopFramebuffer.

Hardware and dependencies

  • Mali-G610 at 0xfb000000, supply RK806 BUCK1 (vdd_gpu_s0), PanVK on Mesa and metal2vulkan from the EVB10 port.

Configuration

  • package/Mali linked; board.toml defaults mali=8 mali-metal=1 evb10-gpu-addon=1; uefi-orangepi5 make-bundle.sh switches to the owner trust cache and carries NativeMaliMetal.addon when those args are set.

Procedure

  • Boot the display+VOP kernel with mali=8 mali-metal=1; read mali: lines and SpringBoard composition.

Development findings

  • On the board with mali=8 mali-metal=1 (same runs as the VOP evidence): mali user status shows SpringBoard and poster extensions composing (vkpipe failed=0); VOP flips the Metal surfaces without a CPU copy.
  • The GPU stopped for good 80 to 400 s after boot (a person at the mouse: the pointer and the lock screen clock froze, MMU page fault in the address space of backboardd at address 0, then the CSG firmware stopped answering TERMINATE). In all ten serial logs with such a fault (7 Orange Pi 5, 3 EVB10) it comes within 0.5 s after the restart of a group that had run before: the driver evicted idle groups with TERMINATE and restarted them with START and zeroed suspend buffer and queue pages, so the persistent CS registers that PanVK sets in the first job only were zero. package/Mali 7b8aa39 evicts with CSG SUSPEND and restarts with RESUME and keeps the queue pages and suspend buffers per group; on the board (gpu5, no mouse, 855 s) the same restart (group 1 at 309.0 s) does not fault, with no suspend failure, no STALL line, no backboardd exit and no panic, and the swap counter keeps counting (evidence/device-mouse-gpu-20261105.txt).
  • The cause is concluded from the timing, the address 0 and from the same event passing after the change; the CS registers of a restarted group were not read.
  • The black ellipse on the lock screen is not a layer format or compositing fault: J120.HEIC is a 3416x3416 two-plane YCbCr disc and SpringBoard lays it out as a 1798x2338 quad for a 4:3 screen in portrait, so a 16:9 landscape panel gets a 61 pixel black strip at each side and the picture stretched into an ellipse (dump of the draws on the board). package MaliMetal b165316 adds mali-wallpaper-fit=1 (default in board.toml): the frontend replaces that quad and its antialiasing fringe by a square that holds the viewport; on the board (wp1) the lock screen covers the whole panel without the black ellipse (evidence/device-wallpaper-20261105.txt).
  • The backboardd exit with signal 11 (real3, 96 s, a person at the mouse) was a read through a freed object in objc_msgSend called from the Metal plugin: the table of held IOSurface imports kept an unretained IOSurfaceRef while Core Animation hands a new wrapper for the same surface every frame. MaliMetal b1c580f makes the entry retain it; the idle lock screen then ran about 25 minutes without a backboardd or SpringBoard exit (dump1, dump2, wp1). The cause is concluded from the crash registers and the code, not reproduced on demand.
  • First launch of an app: the black blocks were the launch pictures SplashBoard keeps (made once, by an older stack, then reused) and, once those are replaced, new ones read before the GPU had finished (half empty or cut in 2 to 4 of 5 per boot). The plugin replaces the old pictures once per Data volume (marker file) and, with mali-sched-wait=2, the render server delivers scheduled when the GPU is done: ten of ten pictures whole in two boots, no black rectangle in the first-launch frames of five apps, no SpringBoard exit in 12 boots (d28-d39).
  • Video decoder bring-up (UniXNU-rk3588-common Rk3588Vdec, rk3588-vdec=N, off by default, docs/media.md): on the board (run vd3) the driver's own PMU sequence powers the VDPU and RKVDEC0 domains, the clocks land at 750 / 594 MHz, the block reads ID 0x53813f05 with its IOMMU in bypass, and four H.264 traces recorded from unmodified Rockchip MPP on a host (CABAC, CAVLC, B pictures at 320x240, CABAC at 1280x720) were replayed 50 times each: 2000 of 2000 jobs finish with status 0x107 and every output picture's CRC-32 equals libavc's decoded picture (50 to 100 us per 320x240 picture, 0.6 ms per 720p picture). The first run panicked because the 16 MiB DMA window was mapped with ml_io_map_wcomb and XNU's io_submap is 8 MiB; it is mapped through IOMemoryDescriptor now. Host test: 7071 checks against a model of the block's registers with the sanitizers, five mutations of the player each fail it (evidence/host-vdec-20261107.txt, evidence/device-vdec-20261107.txt).
  • H.265 on the same block (run vd4: every trace once, vd5: 30 passes; evidence/device-vdec-hevc-20261107.txt): six more traces recorded from MPP's h265 parser and vdpu34x register generator with libhevc reference pictures that equal the picture hash SEI of each stream (320x240 plain, B pyramid with reordering and non-reference B pictures, default scaling matrices, deblocking off, WPP entry points, and 1280x720) were replayed and every picture's CRC-32 equals libhevc's: 10 of 10 traces ok, 3000 of 3000 jobs in the 30-pass run, status 0x107, 50 to 57 us per 320x240 picture and 0.49 ms per 720p picture, no kernel panic. No driver change was needed (same power, clocks and DMA window; only the register image differs). On the host two faults of the recording shim had to be fixed: it answered the hardware ID query with a made-up value, so MPP used its older register layout (it takes the vdpu34x H.265 path only for 0x53813f05, the ID the board reads), and it lacked a lock, so a job of a B-pyramid recording went missing (evidence/host-vdec-hevc-20261107.txt; host test now 10483 checks, 0 failed).
  • AppleD5500 interface read from the original kext and the VideoToolbox plug-in (static, evidence/host-d5500-abi-20261107.txt, docs/media.md): the kext carries Imagination's host decoder code (parameter sets, slice headers, reference lists, DPB) and the user client has eight structure-only external methods (CreateDecoder 0x110/0x48, DestroyDecoder, DecodeFrameFig 0x858/0x410, MapPixelBuffer, UnmapPixelBuffer, SetCryptSession, two unnamed), so a kernel replacement on rkvdec2 needs its own parser and DPB in front of the replayable register generation; nothing of it ran on the board.
  • Way A for the iPadOS side of the video decoder was chosen (docs/media.md, plan only): the AppleD5500 service + user client (eight selectors; selector 7 SetCallback = asynchronous frame results) on top of MPP's own H.264 parser and vdpu34x register generator running in the kernel. Host measurement (evidence/host-mpp-kernel-port-20261107.txt): the ten parser files compile with the kernel's flags against a libc shim (only libc declarations missing), and parser plus generator need about 120 helper names from the rest of MPP; nothing was linked into a kernel or run on the board at that point (the next entries are the work that followed).
  • AppleD5500 service and user client over that core, driven by iPadOS's own VideoToolbox (rk3588-vdec=7, evb10-exec=2; evidence/device-vdec-d5500-20261107.txt, docs/media.md): a signed tool run as launchd's job com.apple.ptpd (its trust cache entry needs launch-constraint category 7) asks for a hardware-required H.264 VTDecompressionSession on the four embedded streams; H264H8.videodecoder finds the AppleD5500 service, creates the decoder (the avcC extradata sits in the ring buffer at offset 0), sends length-prefixed frames and reads asynchronous completions and 0x410-byte result records; every returned NV12 picture's CRC-32 equals the reference decoder's: 248 of 248 sessions (vt29: 15 passes, vt30: 16 passes, up to 727 s after boot, two boots), no panic. The first runs (vt25, vt26) failed from 70 to 150 s on in three ways (extradata all zero, one 64-byte line of a frame zero, then every picture flagged as an error): the cause is the batch path of the pmap, which never cleans or invalidates the data cache when pages become non-cacheable (the write-combined IOSurface ring), so a later write-back of a dirty line puts zeros or old data over the owner's stores; patches/xnu/rk3588-wc-batch-flush.patch in the SoC series adds the flush (vt26 without it: 8 of 24 sessions right; with it 24 of 24 in vt28, 248 of 248 in vt29 and vt30). The cause is concluded from the source of this XNU and from the failures stopping after the change, not from a cache dump.
  • Where a frame's time went (runs vt31 - vt34, evidence/device-vdec-perf-20261107.txt): the 25 to 28 ms (320x240) and 300 ms (720p) a frame took through the service were its own default-on diagnostic, a CRC-32 of every picture read twice a byte at a time through uncached memory (about 100 ns a byte, 99 % of the frame); it now runs only at rk3588-vdec-d5500-log=2. Without it a frame is about 0.3 ms (320x240) and 2.2 ms (720p) in the service (the block 0.07 and 0.65 ms from start to interrupt, the CPU copy into the surface 0.07 and 1.2 ms), and a ten-picture VideoToolbox session takes 158 ms and 1.45 s instead of 400 ms and 4.25 s; the rest of that was the test tool reading each pixel buffer byte by byte (101 to 107 ns a byte), which it now copies out with memcpy first: 49 ms and 147 ms a session. The mpp_buf_slot assertion at the B-frame stream's DestroyDecoder (14 of 14 sessions in vt31) is gone since vdec_core_destroy resets the core first (none in 96 B-frame sessions of vt32 - vt34, whose 128-session runs all passed; the probe was changed in the same step). The 485 us of 'prepare' per frame is most likely the default log lines (an inference, never run with them off).
  • RGA3 copy of the decoded picture into the output surface (UniXNU-rk3588-common Rk3588Rga, rk3588-rga=5, off by default, docs/media.md, evidence/host-rga-20261107.txt, evidence/device-rga-20261107.txt): RGA3 core 0 with its Rockchip IOMMU reaches every page of an IOSurface (RGA2 cannot, it has a 32-bit table); on the board the block reads version 0x30076831, the IOMMU walks scattered 40-bit pages, six picture shapes copy byte-identically with the IOMMU off and on, a copy to an unmapped address stops with an error bit and a page fault and the next copy after a reset is right. It does about 3.8 pixels per clock (720p 326 us at 750 MHz, the setting found at boot, the default). Through VideoToolbox the 720p frame in the service fell from 2241 to 1319 us (the copy from 1227 to 339 us) and every picture's CRC-32 stayed the reference decoder's: 128 of 128 sessions in the 396 MHz run and in the final configuration, every picture through the block, none by the CPU, no failure; one other boot lost a session to videocodecd killed by SIGKILL before any picture (not the block's, described in the evidence file). Host: 4357 checks against strict models with the sanitizers, 32 mutants all killed.
  • More H.264 streams in the video decoder's self-test (UniXNU-rk3588-common 2ef3e31, evidence/host-vdec-h264-streams-20261107.txt, evidence/device-vdec-h264-streams-20261107.txt): thirteen High profile streams made with x264 (CABAC / CAVLC with the 8x8 transform, JVT scaling matrices, four slices, MBAFF, MBAFF with slices, frame_mbs_only_flag 0, six references with a B pyramid, P-only, IDR-only, a 312x234 crop, 720p, 1080p) decode bit-exactly on the Orange Pi 5 in all three paths: the replay of MPP's register images (23 of 23 traces), the in-kernel core (17 of 17 streams, 1.7 ms per 1080p picture on the block) and VideoToolbox through AppleD5500 with the RGA3 copy (16 passes of two rounds over 17 streams: 544 runs, 0 failed, the cropped streams at their visible size). The decoder's DMA window is 64 MiB now (a 1080p trace needs 34 MiB) and the RGA3's window moved to 0x69000000. The first failing job on the board (a wrong expected CRC: x264 pads an interlaced 240-row picture to 256 rows and crops it, the block writes the padded one) found a bug that no earlier run could: the driver's recovery pulsed SOFTRST_CON(20), which are the DDR controller's reset lines (ids 320 to 323 in the vendor header; the block's are SOFTRST_CON(40) bits 2 to 9), and the board stopped until its watchdog reset it 89 s later, on every boot of four runs; fixed (UniXNU-rk3588-common 16f4b7a) and exercised on purpose with rk3588-vdec-reset-test=1 (a failing job, the reset, then 23 of 23 traces again). Not covered: H.264 PAFF, High 10 / 4:2:2, streams with errors, a block that is really stuck (the reset ran on a healthy one), H.265 behind AppleD5500.
  • The in-kernel core also runs MPP's H.265 parser (h265d) and vdpu34x H.265 register generator: six libhevc streams (I/P, B pyramid with reordering, default scaling matrices, deblocking off, WPP entry points, 320x240 and 1280x720) give the recorded register images on the host (UniXNU-rk3588-common 4b366f5, tests/run-core.sh 52692 checks, 0 failed, fed whole and in 4093/1000/7 byte pieces) and 10 of 10 pictures each with the reference's CRC-32 on the board (rk3588-vdec=5, 23 of 23 streams). MPP's own splitter overwrote the first four bytes of a handed-out frame when a start code was cut by the end of an input piece (one stream, 1000-byte pieces), so the core cuts access units itself with MPP's rule; two of four mutations of that cutter survive (multi-slice and prefix-SEI cases no stream covers).
  • H.265 behind AppleD5500, through VideoToolbox's own hardware decoder (UniXNU-rk3588-common b12daa3, evidence/host-d5500-hevc-20261108.txt, evidence/device-vdec-d5500-hevc-20261108.txt, docs/media.md): the plug-in registers its HEVC decoder classes only when the first AppleD5500 service has the boolean property HEVCSupported (read from the disassembly of H264H8Register / AppleD5500CheckPlatform), which the service now sets (rk3588-vdec-hevc=0 turns it off). On the board (run vh1, rk3588-vdec=7 rk3588-rga=5, 16 passes of 46 sessions, 641 s) VTIsHardwareDecodeSupported(HEVC) is 1 and 736 sessions (192 of them H.265: six streams, 320x240 and 1280x720) all returned pictures with the reference decoders' CRC-32, no failed frame, every picture through the RGA3, no panic; the plug-in makes the same calls for both codecs (codec word 3 instead of 2, extradata = length-prefixed VPS/SPS/PPS, frames length-prefixed), a frame is 289 us (320x240) and 1158 us (720p) in the service. The service tells the codec from the extradata (D5500Stream.h, host test tests/run-d5500.sh: 6489 checks over 23 streams in five extradata layouts and three framings, three mutants killed, one survivor listed) and ends each call's access unit with a delimiter so the core's H.265 cutter emits it at once; an H.265 unit carries the pts of the call that held its first slice segment (it carried the call before's).
  • Zero-copy decoding into the VideoToolbox output surface looked into (docs/media.md, evidence/device-vdec-d5500-hevc-20261108.txt): in all 736 sessions of vh1 the plug-in maps one output surface per decoder (MapPixelBuffer twice: the ring and one picture surface) and names the same output slot in every DecodeFrameFig, so it is a staging surface read once per picture, not a pool of reference pictures; the decoder's DPB would still have to be a second picture, so the rkvdec2 IOMMU bring-up was not started (an inference from the call pattern, nothing tried on the board).
  • Video encoder (2026-11-08, rk3588-venc=4, hardware): RKVENC0 (VEPU580, ID 0x50603312) is powered (VENC0 domain was off), clocked (aclk 500 MHz, core 750 MHz) and replays twelve recorded H.264/H.265 encode jobs from unmodified MPP 9b56348; every job ends with status 0x1, 20 passes give the same stream, 158 to 172 us per frame at 320x240, 443 us at 640x360, 1.72 ms at 720p, and the twelve streams decode on the host with libavc/libhevc, every picture, luma PSNR 37.0 to 45.9 dB (P pictures included). The vendor safe reset times out on this block (ignored, reset lines pulsed). No iPadOS user of the encoder.
  • Video encoder through VideoToolbox (2026-11-08, ave28..ave30, hardware): with the finished-frame fields the plug-in's handler reads (found by running it on the host with tools/ave_emu.py: header bit count at record +0x5528, the parameter block's slice list with byte +0x20c = 0, the frame type at record +0x5b34) the H.264 VTCompressionSession of the test program delivers 5 of 5 samples; with rk3588-venc-ave2-encode=1 the application's NV12 pixel buffer goes through RKVENC0 (a recorded trace of the same size supplies the job, fixed quantizer and GOP, 0.45 ms per 640x360 frame), the IDR samples are sync samples and libavc decodes all five at PSNR Y 42-44 dB (tools/check-vt-enc.py). The H.265 plug-in (same code base) is served the same way from the H.265 trace (codec = word +0x10 of the Open struct) and its 5 of 5 samples decode with libhevc at PSNR Y 44-45 dB (ave32, two passes of both codecs, no panic); no rate control, no sizes without a trace.
  • Video encoder core (2026-11-09, vt4, hardware): MPP's H.264 encoder (controller, rate control, slice and parameter-set writers, hal_h264e_vepu580: 54 files of the pinned MPP, unmodified; an earlier version of this text said 60, which counted comment lines) runs in the kernel behind a shim (UniXNU-rk3588-common f5f0e6f, e5fd097, 6e80526); rk3588-venc=6 encodes nine self-test recipes on the block (planar and NV12, 176x144 to 1920x1080, fixed quantizer and constant bit rate) and all nine decode on the host, 41 pictures, luma PSNR 24.7 to 43.4 dB, above a floor that follows the quantizer; with rk3588-venc-ave2-encode=2 the hardware-required H.264 VTCompressionSessions of the test program are served from the core: any size (480x270 with coded height 272, 640x360, 1920x1080), the bit rate (+0x1b0), the maximum key-frame interval (+0x1c4) and the frame rate (+0x1dc) read from the Prepare/Start descriptor, every sample delivered in both passes, the key-frame session with its three sync samples, libavc decodes everything at 41 to 56 dB, 0.8 ms a 640x360 picture (0.72 ms on the block) and 4.2 ms at 1080p, 3.2 KB of the 16 KB kernel stack on the core thread, 1500 s without a panic. On the host the core equals MPP's own register images on its six H.264 recordings and passes 887 checks with the sanitizers (evidence/host-venc-core-20261109.txt, evidence/device-venc-core-20261109.txt). H.265 was added the same day, see the next finding.
  • Video encoder core, H.265 (2026-11-09, h2, hardware): hal_h265e_vepu580 and MPP's h265e codec files (63 files compiled, two #included, pinned commit, unmodified) run in the same core (UniXNU-rk3588-common 54c3bc1, fedaecf); rk3588-venc=6 now has sixteen self-test recipes and all sixteen decode on the host (the seven H.265 ones with libhevc: 3 to 8 pictures each, luma PSNR 28.9 to 43.1 dB, above a floor that follows the quantizer, 0.36 ms for 176x144 to 4.1 ms for 1080p on the block); with rk3588-venc-ave2-encode=2 the five hardware-required H.265 VTCompressionSessions of the test program (640x360 default, 1 Mbit/s with a key frame every 7, 3 Mbit/s every 12, 1920x1080, 480x270) are served from the core, with the settings from the descriptor (+0x1b0, +0x1c4; +0x1dc is 0 in the H.265 plug-in when the application sets no frame rate, the service gives the core 30), every sample delivered in both passes with the same byte counts, the key-frame session has its three sync samples, libhevc decodes everything at 47 to 56 dB, 0.84 ms a 640x360 picture (0.75 ms on the block), 4.2 ms at 1080p, 3.3 KB of the 16 KB kernel stack, 1500 s without a panic. The streams are 4 to 25 % smaller than H.264's at the same settings. The H.265 recordings made on 2026-11-08 were wrong (the recording shim let MPP's read-backs lag behind the jobs and the encoder coded IDR pictures where P was due; mechanism not traced) and were remade with VENC_TRACE_DELIVER=job; on the host the core equals MPP's register images on all twelve recordings and passes 1794 checks with the sanitizers; two mutants of the core are not caught and are explained (hal_h265e_vepu580 does not read hw:qbias_arr; our pictures have one tile) (evidence/host-venc-core-h265-20261109.txt, evidence/device-venc-core-h265-20261109.txt).
  • Real-time encoding through VideoToolbox (UniXNU-rk3588-common 969e04b, 168f742): the AppleAVE2 stub slept 300 ms in each call (a diagnostic of the first runs; with rk3588-venc-ave2=3, which keeps it, every session ran at 3.1 to 3.2 pictures a second, 306 to 316 ms a sample at 640x360 and 1920x1080 alike); without it the plug-in's receiver was still copying frame N out of slot 0 when frame N+1 was written, so the stub now writes the slot of each frame into word +0x3a8 of the plug-in's request record (found by running the plug-in's frame-done code on the host with unicorn: tools/ave_slot.py; the earlier notes had +0x46c, which nothing reads; the original driver initialises the word to -1 and assigns a slot before it answers) round robin over eight sets (twice the four frames in flight Start announces). On the board (runs sp7 and sp9, the same kernel, rk3588-venc-ave2=1) the speed sessions of the test program deliver a sample every 1.37 to 1.80 ms at 640x360 (557 to 729 pictures a second, H.264 and H.265) and every 7.1 to 9.2 ms at 1920x1080 (109 to 140 a second), the first sample 178 to 424 ms after the first call, 0 errors, the same stream byte counts as with the sleep, the five dumped sessions of each codec (among them 16 samples over the eight slots twice) decode with libavc / libhevc at 41 to 56 dB luma, and sp9 ran 1500 s without a panic (the encoder was busy only in the first 210 s). The block takes 0.7 and 4.2 ms of those times; the rest was not split. Logging every call (=2) costs about 3 ms a 640x360 picture (evidence/host-venc-realtime-20261109.txt, evidence/device-venc-realtime-20261109.txt).

Completion criteria

  • Mali composition runs on the Orange Pi 5.

Current limits

  • The CSG SUSPEND/RESUME fix ran for one 14 minute boot without a person at the mouse and was not run on the EVB10 (its package/Mali checkout is older); only idle groups are evicted, a busy one was never suspended; after the poster wave the clock digits of the lock screen show horizontal dashes and the buffer pool is nearly full (cause not investigated), the wallpaper fit puts a fixed square, so SpringBoard zoom and parallax animations of the wallpaper are not followed, and the home screen and App Library were not looked at with it; the held-import fix has not run with a person opening apps for a long session; frame rate under gesture not measured on this board; GPU rail/clock may still be the firmware default (~198 MHz) unless DVFS or mali-npll is set; 5 GHz Wi-Fi and audio unrelated.
  • The wallpaper card carousel of the lock screen (long press) is laid out wrong with and without mali-sched-wait=2 and mali-wallpaper-fit=0 (not investigated); the lock screen flicker did not reproduce in 195 s runs; the sceneID snapshot pictures stay 0 bytes; no 600 s soak with mali-sched-wait=2 and no gesture frame rate with it; not run on the EVB10.
  • The video decoder's only user is the test tool: no App has decoded a frame with it. What ran through VideoToolbox is 17 H.264 streams (Main and High profile, B frames and a B pyramid, scaling matrices, several slices, MBAFF, 1080p) and 6 H.265 streams (Main profile, 8 bit, 4:2:0, one slice per picture, 320x240 and 1280x720); the pictures are compared as a set, so the display order and an end-of-stream flush are not checked (with one access unit per call the core's flush leaves the last picture of display order of t320_bframes in the parser, 9 of 10 shown, not investigated). The RGA3 copy is off by default; with the CPU copy the copy of a picture into the surface at 720p of a picture into the surface (1.2 ms) is larger than the block's own 0.65 ms; the cost of the default log lines was not measured, the encrypted path is refused without a test of what VideoToolbox does then, the reset of the block on an error status was never exercised, and the service runs the core on one thread, one job at a time. Completion is polled, the IOMMU is bypassed, one decode core runs, and the clocks are a little below the vendor's. The pmap patch is in the shared SoC series but was run on the Orange Pi 5 only. The captures vt28 (749 s) and vt29 (716 s) ended when the serial adapter of the board host re-enumerated (together with the reset controller's ACM device, so possibly a USB event of the host rather than a board restart; not looked at), vt30 did not lose it. H.265 was run for six single-slice 8-bit streams only (no multi-slice, tiles, Main10, CRA, prefix SEI or AUD: libhevc's encoder cannot make them), 720p at most, and only through the test tool.
  • The encoder core ran only the test program: no rate-control result against hard content (the test picture compresses so well that no session reached its bit rate; the quantizer does follow the rate), no H.265 Main10, several slices or tiles (the core has one slice and one tile), no key-frame request or bit-rate change from the application in mid-stream, strides of 16 only, nothing above 1080p; real-time use was measured only on easy synthetic pictures (no session reaches its bit rate) with the test program as the only application, nothing captures or displays the pictures, and the original driver's slot allocation and number of frames in flight are not known beyond a call site.

Next action

  • A longer run with a person at the mouse after the fix; bump the EVB10 package/Mali and run it there; the digit dashes after the wave; the home screen and App Library under mali-wallpaper-fit=1; gesture frame measurement; optional mali-npll / DVFS for higher clocks.
  • Video decoder: H.264 PAFF, High 10 / 4:2:2 and error streams, H.265 Main10 / slices / tiles / CRA; decoding straight into the surface (the RGA3 copy is done, 0.34 ms at 720p; a direct write looks pointless, see the findings); the interrupt, the IOMMU and the vendor clock rates; a real App playing a video (the test tool is the only user); run the pmap patch on the EVB10 and see whether the lock-screen clock digits stop showing dashes.
  • Video encoder: AppleAVE2 — H.264 and H.265 pictures of the application's pixel buffers come out of RKVENC0 through VideoToolbox at any size and at the application's bit rate and key-frame interval (the encoder core, MPP's own encoders in the kernel); next: the plug-in's key-frame and bit-rate requests, rate control against hard content, a long run of continuous encoding; H.265 Main10, several slices and tiles; interrupts, the IOMMU, RKVENC1.

Evidence

Network

device-verified

Hardware and dependencies

  • GMAC1 of the RK3588S (Synopsys DesignWare EQoS 5.10a, register block 0xfe1c0000, 32-bit DMA) with RGMII to a Motorcomm YT8531 PHY (MDIO address 0, ID 0x4f51e91b) behind the Gigabit Ethernet connector; the firmware's GmacPlatformDxe sets the pins, the RGMII mode and clock, the transmit delay and the PHY up before the kernel; the chip's OTP (0xfecc0000) gives the MAC address the way the firmware derives it. The on-board Wi-Fi and Bluetooth module and USB Ethernet adapters are not covered.

Configuration

  • opi5-eth=1 identifies the controller and the PHY and follows the link for a minute; opi5-eth=2 runs the controller and tests it with a DHCP exchange, an ARP request and four pings of its own; opi5-eth=3 gives the OS the interface en0 and its IOKit entries (IONetworkStack, controller, interface). Not in board.toml (the kernel line stays 811 bytes): add it with EXTRA_KERNEL_ARGS, because a network makes the system download until the 2 GiB Data window is full. Probes: opi5-eth-builtin=0, opi5-eth-filter=0x..., opi5-eth-flap=N (docs/network.md). board.toml archives build-orangepi5-eth.py, configs/orangepi5_display_defconfig force-loads libOpi5Eth.a and the display probe starts it.

Procedure

  • Plug a cable into the Ethernet port, build the kernel (scripts/build-orangepi5-kernel.sh), make the bundle with EXTRA_KERNEL_ARGS="opi5-eth=3" (REBUILD=1 DEFAULT_ENTRY=xnu MENU_TIMEOUT=3 tools/board/make-bundle.sh), write the ESP with rockusb and capture the serial console: opi5: eth: lines (identity, link, statistics every 10 s) and opi5: eth-net: lines (the stack opened, DHCP, en0 address, per-kind counters). opi5-eth=2 first when the controller itself is in doubt (the self-test needs no OS).

Development findings

  • Host-verified: the pure parts (the MAC address derivation from the OTP, the PHY link resolution, the checksum, the queue size field) pass tests/test-eth.cpp; NativeEth.cpp and EthNet.cpp compile with the kernel's recorded flags and -Werror, are archived (the network side's static initializer made external, the code checked unchanged) and link into the display kernel (evidence/host-ethernet-build-20261106.txt).
  • Observed on the board (evidence/device-ethernet-20261106.txt): GMAC1 is EQOS 0x51, the PHY ID 0x4f51e91b, the MAC address computed from the OTP equals the one the firmware wrote into the address registers, the link comes up at 1000 Mbit/s full duplex, the controller's self-test gets a DHCP lease in 4 ms, the router's unicast ARP reply and 4 of 4 pings, and with opi5-eth=3 iPadOS makes a service for en0, takes a DHCP lease (and renews it at T1), sets its clock, answers 93 DNS queries and 279 of 279 TCP connection attempts and takes 179 MB of TCP payload in 380 s with no controller error, no ring full and no buffer shortage.
  • Found on the board and fixed: the address registers were written low word first and the controller then received every broadcast and multicast frame but no unicast frame to its own address (0 of 9178 in 150 s), so the router's ARP reply and the OS's DHCP offer (no broadcast flag) never arrived; written high word first, low word last, as the Linux driver does, unicast arrived at once.
  • The link follows the PHY: a probe (opi5-eth-flap=60) powered the PHY down 15 times in 981 s and the driver went down and up 15 times at 1000 Mbit/s full, the system kept its address and its traffic; by a mistake of the probe the PHY ran one capture at 10 Mbit/s half duplex and the driver followed it with no error.
  • The OS makes the service for en0 itself (the interface is IOBuiltin, which is the default of opi5-eth-builtin; the other value was not tried); the network stack is opened about 57 s after the boot, the first DHCP discover follows 5 s later.
  • The DMA pool is 1 MiB at physical 0x63000000 (the controller addresses 32 bits and the kernel window is above 4 GiB), Normal non-cacheable, so there is no cache maintenance; the receive ring is polled (a 1 ms sleep when idle) and the transmit ring is filled from the OS's output function under a mutex.

Completion criteria

  • A wired interface en0 that the OS configures by DHCP and uses for TCP and DNS, whose link follows the cable.

Current limits

  • No person plugged or unplugged the cable (a PHY power-down probe stands in), looked at the Settings app, or measured throughput with a tool; 100 Mbit/s was never negotiated and IPv6 addresses were not checked; no interrupts (polled), no checksum/TSO/VLAN offload, no jumbo frames; off by default because of the Data window filling up with the OS's downloads; only the first MAC of this board's OTP was seen; the Wi-Fi and Bluetooth module and USB Ethernet are not done.

Next action

  • Have a person look at Settings with the cable in and pull and re-plug it; measure throughput with a tool on the LAN; decide whether opi5-eth=3 becomes a default once the Data window problem is handled (a bigger Data container or keeping the OS from downloading); then the Wi-Fi/Bluetooth module (identify it on the board first) or USB Ethernet.

Evidence

Audio

planned

Hardware and dependencies

  • ES8388 codec on I2C6 at 0x10 with I2S1 (3.5 mm jack) and HDMI audio on I2S5.

Configuration

  • Not configured.

Procedure

  • None in the first rounds.

Development findings

  • The EVB10 audio driver targets another codec; only the I2S controller part is shared.

Completion criteria

  • Out of the first milestones.

Current limits

  • No audio in the first rounds.

Next action

  • Port the I2S path after the display works.

Evidence

Power

implemented

Hardware and dependencies

  • RK806 PMIC on SPI (BUCK1 GPU, BUCK2 little cores), RK8602 and RK8603 at 0x42 and 0x43 on I2C0 for the big cores, HYM8563 RTC at I2C6 0x51, a PWM fan header, no remote power switch.

Configuration

  • package/Rk3588DvfsBoard.cpp is the rail table for UniXNU-rk3588-common Rk3588Dvfs; board.toml builds build-rk3588-dvfs.py with it and defaults rk3588-dvfs=6 with rk3588-gpu=0 (GPU governor off); orangepi5_display_defconfig force-loads libRk3588Dvfs.a; LegacyDisplayProbe calls rk3588_dvfs_start() before mali_start(). Activity boost reads native_touch_hid_reports and native_usb_hid_reports.

Procedure

  • Boot with the display kernel; read rk3588-dvfs: lines. Probes: EXTRA_KERNEL_ARGS rk3588-dvfs=1..5 / 7..10 as in docs/power.md and UniXNU-evb10/docs/power.md.

Development findings

  • Read on the board, not assumed: SCMI lists 408..1800 MHz (little) and 408..2400 MHz (big) and answers error 102 for the DDR clock; RK806 BUCK1 750 mV (GPU), BUCK2 950 mV (little); RK8602 0x42 and RK8603 0x43 on I2C0 both 1000 mV, die id 10; the firmware starts the big cores at 2400 MHz / 1000 mV. The CPU governors move frequency and voltage with the load (30 to 100 changes per 10 s while SpringBoard starts, 1200 MHz / 675 mV when idle), the thermal sensors read 50 to 65 C and peaked at 79.4 C, no throttling.
  • With the GPU governor on, the board reset itself without a message in five of seven boots, 58 to 61 s after the kernel started and in the first seconds of Mali work (not the watchdog, not a panic, not PSCI); with rk3588-gpu=0 four boots (244 s, then 185 s three times, the watchdog ending those by design) did not. The governor lowers the GPU rail from 750 mV to 675 mV at the 198 MHz the Mali driver already uses; that is the untested candidate. board.toml therefore defaults rk3588-gpu=0.
  • CRU GLB_RST_ST reads 0 after silent resets, watchdog resets and panics alike, so it cannot name a reset reason here.
  • Soft reset via CRU_GLB_SRST_FST after wdt-kick remains in NativeNvme.

Completion criteria

  • The governors start and print rk3588-dvfs: gov lines.

Current limits

  • The GPU governor is off and the reset with it on is not explained; the CPU governors ran four boots of at most 244 s, not a long soak. No power meter. DDR clock unmanaged.

Next action

  • A 600 s soak with rk3588-gpu=0; add a voltage floor argument to the GPU governor (SoC repository) and test 750 mV with the governor on.

Evidence

Image assembly

device-verified

Components: XnuPrelink, DarwinBoot, SoftwareAES.

Hardware and dependencies

  • Kernel from orangepi5_defconfig with the NVMe driver, the original trust cache bundle, the 2 GiB Data seed and unixnu.toml of the payload, the 256 MiB OPI5ESP payload volume that goes on the NVMe ESP, the 9.4 GB root image.

Configuration

  • payload.loader = firmware: the loader is part of the firmware volume of uefi-orangepi5, so the payload carries no loader image.

Procedure

  • unixnu build kernel, then uefi-orangepi5 tools/board/make-bundle.sh (unixnu build payload, the power-off menu entry removed, bundle with the firmware image and the root image); nvme-install.py writes the ESP of the drive.

Development findings

  • The SoC patch rk3588-root-trust.patch makes bsd_init.c call native_emmc_root_trusted; the NVMe driver defines it, so the stub patch of the console kernel is gone.
  • The five EVB10 kernel patches (exit trace, mmap grant, thread sample, userland mounts, vc mirror) are vendored with their source commit; the NVMe personality patch is the board's own.
  • The payload assembles on the host (payload.img 256 MiB, ADT with the pcie-nvme node) and the board started it (evidence/device-first-boot-20261103.txt): the firmware read kernel.macho, its ADT and trust cache from the NVMe ESP, DarwinBoot handed the kernel over, the driver bound to the original IOBlockStorageDevice and the kernel booted to launchd. The ADT memory values were placeholders in those runs; they are the measured ones now (memory area).
  • The package gained PcieWindows.h and its host test (tests/test-pcie-windows.cpp) after the first run showed the BAR in the 32-bit window; the kernel was rebuilt and the bound-address check still passes (18 addresses inside the audited IOStorageFamily, kernel.macho sha256 178d2e1f...).
  • The SoC repository is pinned in feeds.toml; local.toml can point at a checkout during development.
  • The kernel is now built in two passes (configs/orangepi5_defconfig, then orangepi5_display_defconfig) and the payload comes from the second one: package/LegacyDisplayProbe.cpp, KeyStoreProbe.cpp and LinkStubs.c are the display pass's device code, tools/board/make-bundle.sh of uefi-orangepi5 selects the kernel by KERNEL_CONFIG (default the display kernel), and board.toml carries the display archive, the GopFramebuffer component and the offline-legacy-* / sheng-* arguments (553 of 1000 bytes). Host-verified in evidence/host-display-build-20261103.txt; the ADT of a payload build differs from build to build while the kernel does not.
  • package/Mali is a submodule now (Ken-u/Mali, the EVB10's commit 9dd949a; the pointer is staged with the change that adds it, otherwise unixnu resets it to the index). The payload of the Mali-linked display kernel is kernel.macho 51658752 bytes crc32 7bec4f41, ADT crc32 970b5293 (the ADT differs per payload build), trust cache e3343405 and unixnu.toml fe909e88 unchanged; the ESP of the board still holds the display kernel without Mali (f7215c41, written, not verified).
  • Later esp-put (tools/board/esp-put.sh) verified kernel.macho crc32 6612adcc (VOP+Mali+HID display kernel), ADT and unixnu.toml on the NVMe ESP; make-bundle.sh carries the GPU addon and owner trust when evb10-gpu-addon=1.
  • package/Opi5Usb and package/Rk3588DvfsBoard.cpp join the package sources and board.toml archives (build-orangepi5-usb.py, build-rk3588-dvfs.py): the kernel with them links (51757056 bytes, crc32 a7b54353), was written to the NVMe ESP with uefi-orangepi5 tools/board/esp-put-delta.sh (24 of 50 1 MiB blocks sent, read-back VERIFIED) and booted to launchd and SpringBoard (evidence/device-usb-dvfs-20261105.txt).
  • The display kernel links the SoC repository's video decoder archive with its ten recorded traces (four H.264 and six H.265, about 100 to 120 KB each, compiled into the image as byte arrays; the kernel is 53055488 bytes with them); the archive step compiles with the kernel's -Werror compile record and passes the Mach-O audit (evidence/host-vdec-20261107.txt).
  • patches/xnu/opi5-launchd-test.patch (the board's own, after evb10-userland-mounts.patch) adds evb10-exec=2: the owner's program (launchd/ptpd in the test file list) is union-mounted over /usr/libexec and runs as the job com.apple.ptpd under the real launchd, which VideoToolbox needs (as init it cannot make a decoder session); a new job plist is not possible (launchd takes the system daemons from its signed cache). Its trust cache entry needs launch-constraint category 7 (make-owner-trust-bundle.py MACHO@7; category 0 was refused as a constraint violation). Ran on the board in vt25 to vt30 (evidence/device-vdec-d5500-20261107.txt); the kernel with it is 53477376 bytes, sha256 c546e9ee5e2ecaf4...
  • package/LegacyDisplayProbe.cpp now also calls rk3588_venc_start() (after rk3588_rga_start()), the entry of the video encoder self-test that runs only with rk3588-venc=N; the kernel with it builds and boots (evidence/device-venc-20261108.txt, 70434816-byte kernel.macho).

Completion criteria

  • The payload boots from the NVMe ESP through the firmware and reaches the kernel entry.

Current limits

  • The vendored EVB10 patches keep the EVB10 names and drift when the EVB10 repository changes (scripts/check-vendored-patches.sh shows it).
  • The payload was started from U-Boot through the launcher only; the SPI NOR route has not run.
  • Default menu entry is still xnu-probe.

Next action

  • DEFAULT_ENTRY=xnu MENU_TIMEOUT=3 tools/board/make-bundle.sh and rewrite esp.img.

Evidence

Diagnostics

device-verified

Hardware and dependencies

  • UART2 on the 3-pin debug header at 1.5 Mbaud 8N1; the firmware prints its own log on the same port.

Configuration

  • serial=3 and debug=0x10014e keep the kernel console on UART2 and restart after a panic.

Procedure

  • Attach a 3.3 V USB serial adapter to the debug header and capture from power-on.

Development findings

  • The serial adapter is on the board host (UART2 at 1.5 Mbaud) and the first two captures are stored as excerpts in evidence/device-first-boot-20261103.txt (the raw logs stay out of the repository).
  • uefi-orangepi5 tools/board/capture.sh and capture-remote.sh record the port with times (serial-capture.py of the SoC repository, which can also type keys after a matching line: --send); docs/first-boot.md of that repository lists the log lines that settle each step (firmware, PCIe, NVMe, GPT, root, Data, userland) and what each failure means.
  • The driver's PCIe, controller and identify lines did show which derived assumption was wrong (the BAR window) in the first log, as planned.
  • The USB serial adapter re-enumerates when the board resets: a long capture on /dev/ttyUSB0 went silent at the watchdog reset while the board kept running. serial-capture.py now stops with '# device closed' (or 'read error') when the line goes away, and capture-remote.sh takes the device from BOARD_SERIAL_DEV.
  • The firmware's memory map is in the serial log (MEMMAP lines of UniXNUMemMapDxe: before the menu, when it changes, and at ExitBootServices); capture-remote.sh can type Ctrl-C at the U-Boot banner (--send 'U-Boot v' ctrl-c,...) and stop on the prompt, so a run starts and ends without anyone at the board.
  • evidence/device-display-firmware-20261103.txt is cut from the same capture as the memory evidence (memN); the EDID dump is left out of it because it carries the monitor's serial number (the lines about the EDID stay).
  • The host records of the display and Mali builds (evidence/host-display-build-20261103.txt, host-gpu-build-20261103.txt) state which checksums were written to the ESP over U-Boot and which were verified; the file written last (the display kernel without Mali, f7215c41) is the one whose read back aborted U-Boot and is unverified.
  • evidence/device-vop-direct-20261105.txt is an excerpt of capture vop2b after esp-put verified kernel crc32 6612adcc: VOP direct iommu 1 with zero CPU copies.
  • evidence/device-usb-dvfs-20261105.txt is an excerpt of the captures usb6, usb8, usbg2, bisC and soak1 after esp-put-delta verified kernel crc32 a7b54353. A silent reset shows in the serial log as the firmware's DDR training line in the middle of the kernel log (no panic text; CRU GLB_RST_ST reads 0 after it, as after a watchdog reset), and wdt-kick=100 in the ESP unixnu.toml makes the board restart itself about every 190 s, so one capture covers several boots without anyone at the board.
  • The video decoder self-test (rk3588-vdec=N) reports on the serial console only: per-job lines 'done status 0x107 N us crc X expected X: ok' and a per-trace summary; evidence/device-vdec-20261107.txt keeps an excerpt of the vd3 capture and the checksums of the kernel and the ESP image, and docs/media.md says how to repeat the run.
  • Two more evidence files for the video decoder (2026-11-07): evidence/host-vdec-hevc-20261107.txt (six H.265 traces, how the reference pictures were checked against the stream's picture hash SEI, the two recording-shim faults) and evidence/device-vdec-hevc-20261107.txt (board runs vd4 and vd5: per-trace results, timing, image hashes, what the replay does not show); the raw serial logs stay on the board host.
  • evidence/host-d5500-abi-20261107.txt is a static reading of the AppleD5500 kext and the H264H8 video decoder plug-in (selector table with sizes, what the plug-in puts into the decode call, what is not known); no board run, the extracted shared cache used is rebuilt as described in uefi-evb10/tools/xnu-probe/symbolize/README.md.
  • evidence/host-mpp-kernel-port-20261107.txt: unresolved-symbol census of MPP's H.264 parser and vdpu34x register generator and the kernel-flags syntax check of the parser (UniXNU-rk3588-common tools/mpp-kernel-syntax-check.py, 45c0876); host only.
  • evidence/device-vdec-d5500-20261107.txt is cut from the captures vt25, vt26, vt28, vt29 and vt30 (VideoToolbox through the AppleD5500 service: the failures before the pmap cache fix, the 248 sessions after it, the end of vt29 at 716 s when the adapter re-enumerated); the raw logs stay on the board host.
  • The video encoder self-test (rk3588-venc=N) reports on the serial console only: per-job lines 'ok status 0x1 stream N bytes in N us, crc X' and a per-trace summary, and with the dump on the stream bytes as hex; evidence/device-venc-20261108.txt keeps the vc2 and vc4 numbers, the checksums of the kernel and the ESP image and the host decode of all twelve streams, evidence/host-venc-20261108.txt the host test, the mutants, how the traces were recorded and the corrupted-byte control; the raw serial logs stay on the board host.
  • evidence/device-ave2-abi-20261108.txt is cut from the captures ave1, ave10, ave11 and ave20 (the AppleAVE2 service: VideoToolbox opens a hardware H.264 compression session, the selector sequence, the plug-in's request ring, the two faults that kept the Start answer from working (the kext address slide, the frames-in-flight answer), the first YUV record, the callback still failing with -12912 after about two minutes); the raw logs stay on the board host.
  • The encoder core reports on the serial console only: rk3588-venc=6 prints each self-test recipe ('core NAME: WxH, N pictures', per picture the bytes, the quantizer, whether it is an IDR, the time in all and on the block, a CRC, and with rk3588-venc-core-dump=1 the stream as hex) and a summary with the stack depth; every core stream of a VideoToolbox session prints its settings on open and its pictures, jobs, bytes, time a picture and stack depth on close; evidence/device-venc-core-20261109.txt keeps those lines, the host decodes and the negative control, evidence/host-venc-core-20261109.txt the host test; the raw serial log stays on the board host.
  • evidence/device-venc-core-h265-20261109.txt and evidence/host-venc-core-h265-20261109.txt are the same kind for H.265: the self-test lines of the seven H.265 recipes, the H.265 core streams' open and close lines, the host decodes (libhevc) and the host test with the re-recorded H.265 traces; the first of them also corrects the readback wording of device-venc-core-20261109.txt (upgrade_tool's rl readback of the ESP never matches the image; the log is what shows which kernel ran).

Completion criteria

  • A boot log from the board is stored with the evidence.

Current limits

  • Excerpts, not the raw logs, are kept in the repository; each evidence file names the command that repeats its run.

Next action

  • Capture a cold power-on run and the second boot over the formatted Data window and add them as evidence.

Evidence