From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Gwenhael Goavec-Merou <gwenj@trabucayre.com>,
barebox@lists.infradead.org
Cc: johannes@gnu-linux.rocks
Subject: Re: MMC prepare for zynq
Date: Fri, 4 Jul 2025 16:56:01 +0200 [thread overview]
Message-ID: <c4307832-408c-4508-aa7a-46a448dbfe5b@pengutronix.de> (raw)
In-Reply-To: <db21b526-ba6f-4714-8dca-3ed57d7bf028@trabucayre.com>
Hi Gwenhael,
On 7/3/25 09:18, Gwenhael Goavec-Merou wrote:
> Dear all,
>
> I'm trying to uses my zedboard with barebox but can't be able to boot this.
>
> According to mails found in this mailing list I have done this sequence:
>
> export ARCH=arm
> export CROSS_COMPILE=$SOMEWHERE/arm-buildroot-linux-gnueabihf-
>
> make zynq_defconfig
> make -j$(nproc)
That looks correct IMO.
> And copied in the first SDCard FAT partition:
> - images/barebox-avnet-zedboard.img as BOOT.bin
> - barebox.bin
Which binary is barebox.bin?
> But I have nothing displayed through serial port.
Two things come to mind:
- The Image is 184K. Does the Zynq enforce a maximum limit on the BOOT.BIN?
- Does DEBUG_LL produce any output? For details on how to configure
DEBUG_LL, see the troubleshooting guide I just Cc'd you on.
> Are there somewhere details on how to prepare SD Card for a zynq board?
I haven't done work with the Zynq 7000 so far, but Lucas and Johannes
did. I Cc'd them as they may be able to give some tips for troubleshooting.
Cheers,
Ahmad
>
> Thanks
>
> Gwenhael
>
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2025-07-04 15:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-03 7:18 Gwenhael Goavec-Merou
2025-07-04 14:56 ` Ahmad Fatoum [this message]
2025-07-04 17:38 ` Johannes Roith
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=c4307832-408c-4508-aa7a-46a448dbfe5b@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=gwenj@trabucayre.com \
--cc=johannes@gnu-linux.rocks \
/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