From: "Michał Kruszewski" <mkru@protonmail.com>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>,
Alexander Shiyan <eagle.alexander923@gmail.com>
Subject: Re: Compiling barebox without PBL and using dts from Linux dts upstream for Zynq SoC
Date: Thu, 26 Mar 2026 09:06:11 +0000 [thread overview]
Message-ID: <mTw4y_xR5aiHEkjdE2rA6eEGvVkxqees8prnFukfaV5DSv4qcIUBmdtZJ--nwcZQjjf_84O-TDQ8cBHlZubeOfUZeInYOK76kyxGVFxrbvc=@protonmail.com> (raw)
In-Reply-To: <be11f271-1d48-4db4-b06e-f3862264105f@pengutronix.de>
> Do you use upstream or a fork? There seems to be no Z-turn board support upstream.
Upstream, release 2026.03.1.
> barebox can generate multiple images in a build, which image did you use?
I think I don't understand the question.
> Every barebox image on ARM has a prebootloader prepended that:
>
> - decompresses barebox proper
> - loads it and configures the MMU
> - executes it while passing a device tree
How Does PBL pass a device tree to the barebox?
> I am looking at start_avnet_zedboard() and at the start of
> avnet_zedboard_ps7_init(), it skips the low level init if started
> second stage, which is what you seem to be after?
This is true.
However, I don't use the avnet zedboard board.
I don't want any code realted to some other board to be executed.
What is the point of this?
The FSBL has already configured everything at this stage.
If PBL is required, I just want minimal PBL that only does whatever is required to start barebox.
Is it possible to configure PBL in such a way?
> For quick testing, you can replace in arch/arm/dts/zynq-zed.dts
>
> #include <arm/xilinx/zynq-zed.dts>
>
> with your own board. Check that the stdout-path is correct.
If I do so, the dtb compilation fails with:
FATAL ERROR: Couldn't open "zynq-zturn-common.dtsi": No such file or directory
'zynq-zturn-common.dtsi' is included in 'dts/src/arm/xilinx/zynq-zturn-v5.dts'.
Is is placed in the same directory as 'zynq-zturn-v5.dts' ('dts/src/arm/xilinx/').
If I replace
/include/ "zynq-zturn-common.dtsi"
with
/include/ "arm/xilinx/zynq-zturn-common.dtsi"
the dtc still can't find the file:
FATAL ERROR: Couldn't open "arm/xilinx/zynq-zturn-common.dtsi": No such file or directory
> dts/ are just the device trees as they are in Linux. You can only build
> device tree in arch/${ARCH/dts/.
>
> You can read more about barebox device tree handling at:
>
> https://www.barebox.org/doc/latest/devicetree/index.html
So the help message of the Makefile in the dts directory is misleading.
Is is simply copied from the Linux?
Regards,
Michał Kruszewski
next prev parent reply other threads:[~2026-03-26 9:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-26 7:29 Michał Kruszewski
2026-03-26 8:19 ` Ahmad Fatoum
2026-03-26 9:06 ` Michał Kruszewski [this message]
2026-03-26 9:28 ` Ahmad Fatoum
2026-03-26 10:35 ` Michał Kruszewski
2026-03-26 14:07 ` Ahmad Fatoum
2026-03-27 10:37 ` Michał Kruszewski
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='mTw4y_xR5aiHEkjdE2rA6eEGvVkxqees8prnFukfaV5DSv4qcIUBmdtZJ--nwcZQjjf_84O-TDQ8cBHlZubeOfUZeInYOK76kyxGVFxrbvc=@protonmail.com' \
--to=mkru@protonmail.com \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=eagle.alexander923@gmail.com \
/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