Re: [yocto] Chance of success building "wrynose" core-image-minimal for Orange Pi 5 Pro?
"Robert P. J. Day" <[email protected]> Mon, 27 Apr 2026 11:08:15 -0400 (EDT)
| Newsgroups | org.yoctoproject.lists.yocto |
|---|---|
| Message-ID | <[email protected]> |
On Mon, 27 Apr 2026, Robert P. J. Day wrote:
>
> Even though wrynose is not officially out, a colleague handed me an
> Orange Pi 5 Pro ("Orange Pi 5 Pro 16GB LPDDR5 Rockchip RK3588S") and
> asked me to see if I could configure and build a simple image using
> layers that were as close to imminent wrynose as possible, so while
> I've just started a build in another window, can I impose to see if
> anyone can spot any flaws in what I'm doing, or perhaps say that just
> isn't going to work?
>
> First, the repos I'm using:
>
> - bitbake: branch "2.18"
> - openembedded-core: branch "wrynose"
> - meta-rockchip: branch "wrynose"
> - meta-arm: branch "master" (no wrynose branch)
>
> Relevant part of local.conf (as I don't see a machine file for the
> Pro, I'm using the one for the Plus):
>
> MACHINE = "orangepi-5-plus"
> DISTRO = "nodistro"
>
> That's pretty much it -- all the fetching succeeded and my laptop is
> chugging away building "virtual/kernel" before I move on to building
> the remaining pieces and the final image. Is this at least a
> reasonable first attempt to get a simple bootable image?
Well, that wasn't as tricky as I thought. First observation was that
trying to run a Plus image on a Pro was not the way to go -- got these
boot errors after which the boot hung:
[ 12.397294] fan53555-regulator 1-0042: FAN53555 Option[0] Rev[0] Detected!
[ 12.397957] fan53555-regulator 1-0042: Chip ID 0 not supported!
[ 12.398511] fan53555-regulator 1-0042: error -EINVAL: Failed to setup device!
[ 12.399372] fan53555-regulator 1-0042: probe with driver fan53555-regulator failed with error -22
so based on some online pointers, I defined a "generic" Orange Pi 5
machine (for which all the underlying RK3588S content was already
mostly there), built for that new machine, and got a successful boot.
Just means I'm not including any Pro-specific features (yet), but all
I wanted was a bootable image.
rday