From: Kilian Zinnecker via buildroot <buildroot@buildroot.org>
To: buildroot@buildroot.org, Drew Fustini <dfustini@tenstorrent.com>
Cc: Giulio Benetti <giulio.benetti@benettiengineering.com>,
Revy <rabenda.cn@gmail.com>,
robertcnelson@beagleboard.org, jkridner@beagleboard.org,
Drew Fustini <drew@beagleboard.org>
Subject: Re: [Buildroot] [PATCH v5 0/2] Add board support for the BeagleV-Ahead
Date: Wed, 01 Jan 2025 21:00:54 +0100 [thread overview]
Message-ID: <2292259.iZASKD2KPV@kilian-laptop> (raw)
In-Reply-To: <Z3WcIOKr8jnCUVCY@x1>
Hello Drew,
[--SNIP--]
> > I think that u-boot is the ideal solution since that is the direction
> > that T-Head decided to go. I asked Revy on Telegram [1] and they showed
> > me where in thead-u-boot [2] that reset_sample() is called.
> >
> > Revy pointed me to a build of u-boot-with-spl-beagle.bin [3] that I've
> > just flashed to my Ahead [4]. Unfortunately, there is an issue that
> > results in the board not booting [5]. Revy is going to look into the
> > issue and get back to me.
[--SNIP--]
>
> Revy just replied that I should be trying mainline OpenSBI. I have to go
> offline for awhile but I will try that later today.
I actually didn't wait and acutally already tried the revyos uboot and it
seems to work with kernel 6.12.7 and OpenSBI 1.6. I now get:
[ 0.113565] smp: Bringing up secondary CPUs ...
[ 0.121700] smp: Brought up 1 node, 4 CPUs
[--SNIP--]
[ 0.216965] cpuidle: using governor menu
[ 0.251283] cpu3: Ratio of byte access time to unaligned word access is
6.14, unaligned accesses are fast
[ 0.251283] cpu2: Ratio of byte access time to unaligned word access is
6.14, unaligned accesses are fast
[ 0.251284] cpu1: Ratio of byte access time to unaligned word access is
6.14, unaligned accesses are fast
[ 0.303594] cpu0: Ratio of byte access time to unaligned word access is
6.14, unaligned accesses are fast
So I think all cores are up and running now! :D Thanks for all the help so
far! I still have some questions though and there are still some things to do.
However, I will send a v6 of the patches, although they are still not ready to
get accepted.
Regarding the revyos boot, I have two questions:
1) Are the xuantie binary blobs still needed? The light_aon_fpga.bin and the
light_c906_audio.bin?
2) The revyos uboot seems to also need the reset-sampe device tree node. I
therefore added it via a custom device tree. However I still get the error
message "## fdt has no reset_sample". Any idea, what could be wrong here?
https://github.com/revyos/thead-u-boot/blob/th1520/arch/riscv/lib/bootm.c#L115
Thanks and best regards,
Kilian
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-01-01 20:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-30 22:46 [Buildroot] [PATCH v5 0/2] Add board support for the BeagleV-Ahead kilian.zinnecker--- via buildroot
2024-12-30 22:46 ` [Buildroot] [PATCH v5 1/2] package/xuantie-bins: new package kilian.zinnecker--- via buildroot
2024-12-30 22:46 ` [Buildroot] [PATCH v5 2/2] configs/beaglev_ahead: new defconfig kilian.zinnecker--- via buildroot
2024-12-30 22:53 ` [Buildroot] [PATCH v5 0/2] Add board support for the BeagleV-Ahead Kilian Zinnecker via buildroot
2024-12-31 23:01 ` Drew Fustini
2025-01-01 17:13 ` Kilian Zinnecker via buildroot
2025-01-01 19:46 ` Drew Fustini
2025-01-01 19:48 ` Drew Fustini
2025-01-01 20:00 ` Kilian Zinnecker via buildroot [this message]
[not found] ` <CAAT7Ki9Js9C47anbGWMZ--gu88w=k1yVSbU_HJ=T2N7+7n_DUg@mail.gmail.com>
2025-01-01 20:59 ` Kilian Zinnecker via buildroot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2292259.iZASKD2KPV@kilian-laptop \
--to=buildroot@buildroot.org \
--cc=dfustini@tenstorrent.com \
--cc=drew@beagleboard.org \
--cc=giulio.benetti@benettiengineering.com \
--cc=jkridner@beagleboard.org \
--cc=kilian.zinnecker@mail.de \
--cc=rabenda.cn@gmail.com \
--cc=robertcnelson@beagleboard.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox