Am 30.09.24 um 13:52 schrieb Peter Robinson via arm:
Hello Peter,

sorry for the delay. Here's my enviroment:
Rock5b with
- Radxa Wireless Module A8
- Radxa PowerPower PD 30W
- 1 TB NVME, no EMMC-Card
- your bootloader u-boot-rockchip-spi.bin flashed to SPI
- Fedora 41 Beta on NVME

I've tested 
Armbian_24.8.1_Rock-5b_jammy_current_6.10.6_kde-neon-kisak_desktop.img.xz and 
and other *img.xz Image to boot on this system: no success. It only boots 
installed Fedora 41 Beta system.
I don't care about Armbian, I have no idea what they put on their
images, Armbian is off topic for this list.

Only images which comes as iso image are bootable. Output via serial console. I 
have to search for a bootable image with support for /dev/mtdblock0
What Fedora images did you test? What do you mean by "bootable image
with support for mtdblock0"? You should be able to reflash from the
U-Boot shell.

You're right with reflash from U-Boot shell, but I couldn't manage it.

How do I get u-boot-rockchip-spi.bin or another SPI Image to the mmc card and load it ?

From the U-Boot menu I choose Exit but

=> ls mmc 1:1

0 file(s), 0 dir(s)

=>

Could I get a little bit of help to go further ?

Andreas

Question: is there any timeline for support of HDMI output?
You'd have to ask upstream, it didn't make 6.12-rc1 so the next window
is the 6.13 merge window which will be in about 2 months so maybe
early next year? How long is a piece of string.... the patchset that
is currently posted is the just the basic driver, no DT etc. Once
something looks sane I may add it to my a64 kernel I build in copr to
make it easier to consume but even there isn't soon.
-- 
_______________________________________________
arm mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to