From: johannes@gnu-linux.rocks
To: barebox@lists.infradead.org
Subject: Porting Cora Z7 Board to barebox
Date: Mon, 28 Apr 2025 19:20:01 +0200 [thread overview]
Message-ID: <20250428172001.6708-1-johannes@gnu-linux.rocks> (raw)
I have a Cora Z7 board which I want to port to barebox. The Cora Z7 embeds an
Zynq 7000 SoC with a single core Cortex-A9 and 512 MB DDR3 memory. Barebox
already supports the Zynq 7000 and the Avnet Zedboard.
I have some questions and maybe you can point me in the right direction:
When I am compiling barebox with the zynq_defconfig, as an output I get the file
barebox-avnet-zedboard.img. This file contains the PBL, barebox proper and the
device tree, right?
The Cora Z7 uses a different memory configuration compared to the Zedboard. My
first idea was to use Xilinx FSBL and let the FSBL start barebox. The FSBL can
start an ELF file. But if I use just the compiled barebox file, the device tree
is missing, right? Is there a way to hard code the UART to use for the barebox
console for barebox proper?
The Zynq on the Cora Z7 only embeds a single core Cortex A9 while the SoC on the
Zedboard embeds a dual core Cortex A9. Does this affect the cores initialization
in arch/arm/mach_zynq?
I am looking forward to your replies.
Thank you and best regards,
Johannes Roith
next reply other threads:[~2025-04-28 17:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-28 17:20 johannes [this message]
2025-04-29 8:34 ` Porting Cora Z7 Board to barebox Sascha Hauer
2025-04-29 9:49 ` Ahmad Fatoum
2025-05-01 12:16 ` Johannes Roith
2025-05-01 13:56 ` Johannes Roith
2025-05-05 7:39 ` Sascha Hauer
2025-05-06 17:04 ` Johannes Roith
2025-05-16 19:45 ` Ahmad Fatoum
2025-05-19 8:32 ` AW: " Michael Graichen
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=20250428172001.6708-1-johannes@gnu-linux.rocks \
--to=johannes@gnu-linux.rocks \
--cc=barebox@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.