Hi all, Thanks for the response here's where I'm at.
Summary: CM3588-Plus (RK3588): OpenBSD 7.8 RAMDISK boots via u-boot-rk3588/EFI, stalls after ohci0 attach; vendor DT differs for Plus. Details: I’m testing OpenBSD/arm64 on a FriendlyElec CM3588-Plus (RK3588, 32GB). I can boot the OpenBSD 7.8 RAMDISK kernel via SD card using OpenBSD’s u-boot-rk3588 package and EFI (BOOTAA64.EFI), but the kernel consistently stalls during early device attach. Hardware Board: FriendlyElec CM3588-Plus SoC: RK3588 RAM: 32GB Serial console: UART2 (serial@feb50000), 1,500,000 8N1 (DT stdout-path uses serial2:1500000n8) Boot path / versions SD card: miniroot78.img (dd) U-Boot: u-boot-rk3588 (U-Boot 2025.07; boots via bootflow scan / efi_mgr) EFI loader: OpenBSD/arm64 BOOTAA64 1.22 Kernel: OpenBSD 7.8 (RAMDISK) #38 ... Boot log excerpt shows normal early init (PSCI/GIC/EFI, memory, SCMI, clock, GPIO, etc.) then USB host attach, then stall. Last lines printed: xhci0 at mainbus0, xHCI 1.10 usb0 at xhci0: USB revision 3.0 uhub0 at usb0 configuration 1 interface 0 "Generic xHCI root hub" ... ehci0 at mainbus0 usb1 at ehci0: USB revision 2.0 uhub1 at usb1 configuration 1 interface 0 "Generic EHCI root hub" ... ohci0 at mainbus0 After this: no further output on serial no panic/backtrace no watchdog reset UKC attempt I booted with UKC (boot -c) and issued: disable rkusbphy0 disable rkusbphy1 disable rkusbphy2 disable rkusbphy3 disable dwc3 disable usbdrd quit UKC produced no confirmation output, and the same devices still attached (rkusbphy0-3, xhci0/ehci0/ohci0) and stalled at the same point. DTB / board variant note || doubts OpenBSD provides rk3588-friendlyelec-cm3588-nas.dtb (dtb-6.14 / 7.8). However FriendlyElec’s vendor kernel uses different DT sources for CM3588 vs CM3588-Plus: CM3588: rk3588-nanopi6-rev09.dts CM3588-Plus: rk3588-nanopi6-rev06.dts Diffing OpenBSD cm3588-nas DT against the vendor CM3588-Plus DT shows substantial USB-related differences (DWC3 node structure/compatibles, clocks/clock-names, power-domain phandles, explicit reset lines, EHCI/OHCI companion+PHY wiring), so the shipped DTB may not match CM3588-Plus USB/PHY/power wiring. (????) I can provide full serial logs and the relevant DT diff hunks if needed. (after a very long or deal not sure if I bricked the device or not last night but I plan on keep hitting this thing until (hopefully until it runs). Best Regards Tiago. Sent with Proton Mail secure email. On Thursday, 8 January 2026 at 06:09, Mike Larkin <[email protected]> wrote: > On Wed, Jan 07, 2026 at 05:02:24PM +0000, 0x4E0x650x6F wrote: > > > Hi All, > > > > I finally decided to migrate to OpenBSD recently, > > and I was thinking if i could also use openbsd > > on CM3588 Plus (its a NAS board), uses rockchip > > rk3588. > > I noticed that a device with the same chip is > > supported I trying to find any documentation / help > > that could give me some guidance. > > > > I would be willing to assist to the best of my abilities, > > I have a device that is not in active use that, > > i could use as a test platform. > > > > Best Regards > > Tiago Carvalho. > > > Looks like a generic cm3588 board, you could try the rock5a DTB or something > similar. probably would get you reasonably far then tweak. > > unless you already have the DTB, say, from linux... > > -ml
