Can someone make a build for orange pi zero 3?

Hardware Questions and Recommendations
42

Why? The Zero 2W is a repackage of the Zero 3 into a different form factor by OrangePi, doesn’t it make more sense to pool resources towards fixing them both?

43

If you're 100% sure it's the same device fine by me

44

strange because the bootloader should be working. This was confirmed with the manjaro image

45

@wigyori
I tried to make a backport to the existing version and it required a large number of patches https://github.com/iuncuim/openwrt/commit/13ea9ec57372f8c26b3eb4bab3122103d56e54a7
I think it would be better to upgrade the u-boot version.
I checked the available patches, they are not in version 2023.10, so applying them should not cause problems for existing devices

46

thx @iuncuim ，my 4gb zero3 works

1 Like
47

There is also an "official" release for OpenWRT: http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-Zero-3.html

Where is the difference to this manually build release?

48

Was loaded at 6 December 2023. It is quite possible that it is based on my work posted in November.

update: I looked, the kernel has the same 6.1.62 version, so most likely the “official relese” is based on mine.

2 Likes
49

thank you for your support! ist there a guide to build it with your patches?

50

You can cherry-pick first two patches from here (cf34cc57a6fb41be0a35bbe0fcb3a5db4e739f17 and 71702aea669e6eea228ec390e7eccdc8f21796aa): https://github.com/iuncuim/openwrt/commits/master-opizero3/
Then select the device to build with menuconfig

1 Like
51
52

Did anyone consider trying to add it to mainline U-Boot via config flag, like Xunlong U-Boot does, so no dynamic detection is needed? Not great to have multiple images for the two variants, but at least mainline U-Boot can be used without patch.

53

If we are talking about 1.5GB memory, then this is not difficult to do.
@PjV already reported that his board booted normally.

54

I didn’t post it anywhere since it’s a fairly simple modification, but the option with two defconfigs doesn’t look acceptable for mainline

55

Yes, that one I meant. I also have a report that it works fine. Indeed, an own/edited defconfig would still be required, but having the flag implemented allows at build which boots on 1.5G, without patching actual driver files. But I cannot estimate whether this would be an acceptable addition, and you are right, that in the end it does not make so much difference whether to patch the defconfig only, or dram_sun50i_h616.c only to hardcode the size = ... * 3 / 4 for a build.

56

We can add a second defconfig for the version with 1.5GB of memory, it's not difficult. But we would like to be able to determine the amount of memory at startup time. It would be easier if one of the developers had this version, but as a rule everyone chooses the version with 4GB of memory.
If the opportunity arises, I will buy the version with 1.5G memory. But I don't have much motivation to do this just to finalize the DRAM driver and then forget about this device

57

We have a hand full of users with the 1.5G variant, one of which was building the bootloader with the * 3 / 4 patch and says it is working. But surely those are not much, compared to 1/2/4G variants, indeed. I am currently in Shenzhen close to Xunlong office. If they find time to meet later today, I can check whether they have a sample of this board at hand, but surely they ship out the devices from elsewhere.

... okay, I'll get one and can test the patch myself the next days.

If detecting the memory size at startup time was possible, we would not need a second defconfig, if I understand correctly? That would be best, of course. But I have no experience in Linux and U-Boot code development, hence wouldn't know where to start other than what I see form your patches for the LPDDR3 boards.

58

Nice.
You can also use this patch, it prevents cases where the memory size is determined incorrectly

59

Hi
I am really new to the OpenWRT world!

I have bought an OrangePi Zero 3 (2gb variant) because the site of the producer is officially compatible with OpenWRT.
I have installed the image on the producer site (probably the same posted here as I read) but I have no WiFi section and I can't install some package for kernel incompatibility.

I want to install wireguard client.

60

because the seller/manufacturer lied to you.

61

Now I am so sad T.T
Since when do manufacturers lie to us to sell more devices?