Orange PI Zero2 and FreeBSD 13.2

The only difference between the H618 and the H616 is that the former has a higher CPU clock speed
The H616 device tree is also used in the OrangePi Zero 3 Linux image released by OrangePi.

I used both `sun50i-h616-orangepi-zero2.dtb` and `sun50i-h618-orangepi-zero3.dtb` on the OrangePi Zero3. There is almost no difference between the two; the only difference is that the output of `sysctl hw.fdt.model` and `sysctl hw.fdt.compatible` is different.

use sun50i-h616-orangepi-zero2.dtb:
Code: 
root@generic:~ # uname -a
FreeBSD generic 16.0-CURRENT FreeBSD 16.0-CURRENT #0 main-n285702-8e8d87856241: Tue May  5 10:36:17 UTC 2026     root@releng3.nyi.freebsd.org:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC arm64
root@generic:~ # sysctl hw.fdt.model
hw.fdt.model: OrangePi Zero2
root@generic:~ # sysctl hw.fdt.compatible
hw.fdt.compatible: xunlong,orangepi-zero2 allwinner,sun50i-h616

use sun50i-h618-orangepi-zero3.dtb:
Code: 
root@generic:~ # uname -a
FreeBSD generic 16.0-CURRENT FreeBSD 16.0-CURRENT #0 main-n285702-8e8d87856241: Tue May  5 10:36:17 UTC 2026     root@releng3.nyi.freebsd.org:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC arm64
root@generic:~ # sysctl hw.fdt.model
hw.fdt.model: OrangePi Zero3
root@generic:~ # sysctl hw.fdt.compatible
hw.fdt.compatible: xunlong,orangepi-zero3 allwinner,sun50i-h618
 
code is there, i have willpower issues to test on hw yet (opiz2w)

i submitted uboot for it to bugzilla but recent atf (arm trusted firmware) doesn't build somehow (wtf)
 
video and wifi / bluetooth most likely do not work
on the 3w probably usb works and not much else.
on the 2w 14.x should work with the patches i posted maybe with some work.
some devices from 3w may work with the code i posted for cubie a5e but not many, the soc is different.
a733 support is not yet in linux main kernel
 
tingo said:
Has anyone tried FreeBSD 15.x (or 14.x) on the Orange Pi Zero 2W or 3W yet?
Click to expand...
Not that useful but I tested OpenBSD on the OPi Zero 2w a number of months back.

CPU freq scaling worked, GPIO worked but very little chance on the fairly niche wifi chip. CDTech?

Its a fairly basic Allwinner kind of setup. So uboot and device tree files.
 
i don't like the embedded situation with things as if flapping in the wind. thanks to fragile fragmented soc world

while at amd64 literal 20 year old machines run
 
that's the issue, not getting anything 100% working. like software-hardware adhd or so

actually i think lifetime of hw and it's availability is even fine for some socs?

when did allwinner h3 come out? 12y ago apparently, and h5 10y ago. granted they are stb socs

oh hw manufacturing is business too. maybe even sw manuf is. and you like do business or you're done

but in the end there needs to me some standardized embedded hw. it feels as if it's better to just come up with good embedded amd64. make all interfaces standard and then you have nice life

but it's not that good. it's bad on amd64 too. granted, cpu works. pcie works. but you also need hw

in the end you end up with working amd64 and rest flaps in the wind. a hate it

i don't think it even matters if you use it "professionally" or not. i don't think many can afford being fully self sustained

i don't know how to fix this cupboard full of "edged" hw in fbsd

i think there's plenty of people needing some categories of embeddeds, low med and hi power with low med and hi io

unfortunately i don't have enough brainpower and money to get something done in that area. i can only buy stuff, hack it, report things, test, maybe fix a little, eventually could even sell something. the latter really needs the solid brick house and not open porch in which things hang
 
You must log in or register to reply here.
Back
Top