pmos/u-boot-radxa-cm5 #1126

Open
opened 2025-05-20 03:19:59 +00:00 by forge · 10 comments
Owner

Getting a truncate error similar to https://github.com/SecKatie/u-boot-rockchip/issues/1

Getting a truncate error similar to https://github.com/SecKatie/u-boot-rockchip/issues/1
Author
Owner

Notwithstanding that truncate error, if I am to follow with how alpine does it, I should try to use the upstream u-boot if possible, and build arm-trusted-firmware for rk3588, following rk3399.

According to https://gitlab.collabora.com/hardware-enablement/rockchip-3588/notes-for-rockchip-3588/-/blob/main/upstream_uboot.md, rk3588 support is upstreamed, so it'll probablt a question of patching in the defconfig.

That said, I should try to get the rockchip version built first so I have a control.

Notwithstanding that truncate error, if I am to follow with how alpine does it, I should try to use the upstream u-boot if possible, and build arm-trusted-firmware for rk3588, following rk3399. According to https://gitlab.collabora.com/hardware-enablement/rockchip-3588/notes-for-rockchip-3588/-/blob/main/upstream_uboot.md, rk3588 support is upstreamed, so it'll probablt a question of patching in the defconfig. That said, I should try to get the rockchip version built first so I have a control.
Author
Owner
rk3588 is indeed supported by arm-trusted-firmware: https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/21840 (https://www.collabora.com/news-and-blog/blog/2024/02/21/almost-a-fully-open-source-boot-chain-for-rockchips-rk3588/)
Author
Owner

Once I want to bring up mainline, I can base the package on https://gitlab.collabora.com/hardware-enablement/rockchip-3588/debian-image-recipes

Once I want to bring up mainline, I can base the package on https://gitlab.collabora.com/hardware-enablement/rockchip-3588/debian-image-recipes
Author
Owner

Got arm-trusted-firmware updated: https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/84545

Also looks like I'm getting u-boot-radxa-cm5 to a good place. This ressource was really helpful, as I couldn't figure out how to build the itb and itbloader file: https://opensource.rock-chips.com/wiki_Boot_option

Got arm-trusted-firmware updated: https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/84545 Also looks like I'm getting u-boot-radxa-cm5 to a good place. This ressource was really helpful, as I couldn't figure out how to build the itb and itbloader file: https://opensource.rock-chips.com/wiki_Boot_option
Author
Owner

Okay, getting somewhere. The boot process is stuck but at least a first step works!

(stuck with one line in serial: U-Boot TPL 2017.09...)

Okay, getting somewhere. The boot process is stuck but at least a first step works! (stuck with one line in serial: U-Boot TPL 2017.09...)
Author
Owner

Got u-boot to a place where it goes through 3.1. Issue is with booting the kernel now:

No misc partition
"Synchronous Abort" handler, esr 0x96000010

* Reason:        Exception from a Data abort, from current exception level
....

This fails whether we use the debian kernel or alpine kernel.

Got u-boot to a place where it goes through 3.1. Issue is with booting the kernel now: ``` No misc partition "Synchronous Abort" handler, esr 0x96000010 * Reason: Exception from a Data abort, from current exception level .... ``` This fails whether we use the debian kernel or alpine kernel.
Author
Owner

It might be the case that u-boot is just to damn old. It might be a good idea to reflash the debian image, and upgrade u-boot to a newer version, and see if it works. An up-to-date branch: https://gitlab.collabora.com/hardware-enablement/rockchip-3588/u-boot

It might be the case that u-boot is just to damn old. It might be a good idea to reflash the debian image, and upgrade u-boot to a newer version, and see if it works. An up-to-date branch: https://gitlab.collabora.com/hardware-enablement/rockchip-3588/u-boot
Author
Owner

The error was caused by not setting the fdt

The error was caused by not setting the fdt
Author
Owner

Okay, I now have a shell now that the serial port is set as ttyFIQ0 and added in inittab. fdt is all but working, but at least this works.

Okay, I now have a shell now that the serial port is set as ttyFIQ0 and added in inittab. fdt is all but working, but at least this works.
Author
Owner

Okay, so turns out the kernel didn't actually build the required modules. WIth that done, we now have an (empty) screen.

Okay, so turns out the kernel didn't actually build the required modules. WIth that done, we now have an (empty) screen.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
forge/ayaports#1126
No description provided.