Orange PI Zero2 and FreeBSD 13.2

And I guess you build it (after adding in the changed files) just like shown in post #1 in this thread?
I'm still a bit on the fence - my Opi Zero 2W doesn't have the extension board, so no RJ45 connector, and wireless isn't working yet.
 
yeah you build it about like on post #1

as for other, i think i would still prefer the diffs. if i have some time. perhaps you could put updated one to some other place than forum attachments. like you likely update it, etc. but yeah, can't keep it on 13.2 or 14, either you, me or someone else need to take this and rk as separate parts into 15, then someone needs to use it. and someone needs to be able to maintain it. or it goes bbb way or so, sadly. i mean i do keep 13.2 src here as well. so it would be easy to test. just somehow currently lack of willpower to search for usb c cable, serial and so on to get opiz2w up. among other things
 
sle123 said:
Hi All!

I am trying to run FreeBSD 13.2 on Orange PI Zero2.

1. Successfully built from sources u-boot v2023.04, put it on microSD card by command:
# dd if=u-boot-sunxi-with-spl.bin of=<mmc_card_device> bs=1k seek=8 conv=sync
Insert card into Orange PI Zero2, connect serial console to my desctop PC, turn power on.
U-boot started successfully, I got u-boot prompt "=>" on the serial console.
Click to expand...
Hi, can I get your u-boot-sunxi-with-spl.bin ?
I did try mine it's not work not show anything on first boot
 
it did not

i have code here. i tried to pick it out of covacat patch. it's too much for my brain and i need help. he gave up. we need it in current and an actual one hacking it rather than me

also asked on mailing list once

i have board, i powered it up, seemed to get into fel mode for a short time

i also tried to make uboot port, failed to compile

i have port patches too, needed to patch uboot master etc

so here's the progress

any other people wanting to share my load?

i tried irc too. surely people were there who would be happy to review if i feed them small bits of them at once. but i have problem with that because i would need to know what's right. i haven't done any hw work in that class
 
ketas said:
awesome!!! wait obsd boots on it?
Click to expand...
Yeah, OpenBSD (possibly by proxy of NetBSD) actually has very good support for SoC boards. The sunxi ones are particularly quite good, including some power management.

I used pretty much the same process as the pcduinoV2 (A10 which is actually armv7).

ZioMario said:
Actually HDMI works on this board ?
Click to expand...
Ah, didn't check, I prefer serial for this stuff.
GPIO worked well but the inbuilt WiFi chip did not work (its a weird one).
 
the later ones come with unisoc wifi chip. u-boot is easy to get working just add EFI support. other bsds and linux do not need efi to boot but freebsd does. there was a loader-u-boot but was dropped. i used to build u-boot on a linux vm and just adding efi support to the config file. you can build u-boot on a freebsd box too but doing it on linux will get you more readibily available docs that you don't need to convert to bsd (mostly the toolchain naming).
 
ketas said:
and fbsd get's rid of i386 and soon maybe armv7 too, leaving us like, how many boards? but i admit work is being done on riscv etc
Click to expand...
Still more than most other operating systems combined, so don't be too worried ;)

Potentially a bigger issue is that there isn't a single board that is 100% supported. Either Wifi, bluetooth, power management, GPU is missing. But at the same time, it is rare to use *every* bit of functionality on a board, so it is easy enough to swap the entire thing out with one that does support a specific bit of hardware needed.
 
ketas said:
i also tried to make uboot port, failed to compile

i have port patches too, needed to patch uboot master etc
Click to expand...
I'm a ports guy, I can usually get things to compile :-) Where do I get the sources? Is it just uboot -- that's only relevant to ARM-architecture(s) and may need to be cross-compiled -- or something else?

Actually, wait, there is already stand/uboot in the src-tree, why do you need a port of it?
 
i mean i got into trouble getting uboot built for that specific board. kind of need it first. you can start with templates of ports of others or you could have mine

then you need to boot something. if it's on obsd, maybe port that. but i can't. and same with fbsd code i have here that covacat did. and nevermind the forums, which are like super annoying ways to communicate. anyone irc's maybe?

also why the hell do i need linux vm. especially if we already build uboots on fbsd?

and unsure about many boards. rockchip have own issues, rpi too. allwinners have like h3 is quite good. but for 64bit, it's kind of few ones left
 
you don't need a linux vm. its just easier because all the docs you find for various boards for building target linux and you don't have to convert them to freebsd paths, toolchain naming and whatever. so it's one layer of potential problems less
but in general the official board "how to" works for freebsd if you add efi support to the u-boot build, no other changes are needed.
 
even when i do that, what happens after it? i think best path is to add proper port like for others. patch things if needed. if the whole idea is to support fbsd. also covacat, where did you code come from anyway, from other bsd's, or you wrote it off docs? anyway how to like actually get it working. if you gave up? seems pretty nice cheap hw btw. and it won't go off production any time soon i think. well i don't know eh. judging by research that's pretty nice hw. minus the unsupported wifi eh. oh i don't know. i like the nature of allwinner a bit better somehow. i actually tried to run that code but like gave up on sheer amount of workload. so i never got it booted. nevermind sorting it into chunks for reviews. anyone else wants to try? i have like one diff and one only-changed-files zip here. oh, and no knowledge of hw. despite having done embedded for 10 years and fbsd since 4.6. i would like to see it running tho, somehow. i of course tried to get it applied on current since where else should it go anyway. probably i end up deleting changes again even if i try. unsure when it would be ready at this pace eh. oh and if i get it in, i have to like blindly wonder if it would even work as i have like no way to verify it. no idea who would. you know, someone who actually writes things like that for hobby or job
 
code came from linux kernel, openbsd kernel, soc manual, android/linux board support package (BSP) but mostly from the linux kernel because it is the fastest way
porting u-boot is not much work but the rest is hard to make as a port as it needs to integrate with the kernel 13,14,15 etc.
 
you can't copy anyway as it won't compile / work. you have to adapt it. but it's faster than using manuals (which kind of suck anyway). anyway a lot of arm drivers look very similar with the linux ones. the result doesn't look like the linux driver at all. and the BSP code is not always GPL-ed (and linux drivers (sometimes) look like made from BSP code)
also a lot of stuff in /sys/contrib/device-tree/src/arm is GPL only
 
You must log in or register to reply here.
Back
Top