[Buildroot] Zynqmp ZCU-102 Xilinx
Adrian martinez munera
adrianmartinezmunera at gmail.com
Tue Dec 3 08:44:51 UTC 2019
thanks for your answer!
How I said to Thomas, I'm trying to compile a Linux image to my ZCU-102
with EPICS (https://epics.anl.gov). But, as first step, I'd want build a
simple Linux image, all of this using Buildroot.
Using yours steps, I've created a pmufw.bin with your builder and the
'pm_cfg_obj.c', created by the Vivado project (xilpm library enabled).
Now I've a new two errors at the boot:
1. boot console [cdns0] disabled
2. The root file system is empty
*defconfig* file that I'm using:
# BR2_TARGET_ROOTFS_TAR is not set
El mar., 26 nov. 2019 a las 17:49, Luca Ceresoli (<luca at lucaceresoli.net>)
> Hi Adrian,
> On 20/11/19 09:21, Adrian martinez munera wrote:
> > Hi,
> > I'm not sure if I have to write you by this mail.
> > I'm using buildroot to create a Linux image to my ZCU-102, adding EPICS.
> > My first attempt are been build a simple Linux image, without EPICS,
> > but it doesn't work.
> > ¿Could you help me? ¿Could you give me all of necessary files to build
> > the image?
> Thomas already replied with some objections, and I agree you should
> explain better your problem.
> However, as setting up booting is more complex on ZynqMP platforms than
> in other ones, here are a few notes to address booting. They could be
> useful for other people as well.
> Buildroot has a defconfig for the ZCU106 board, you can take that as a
> starting point. However some things have changed since that was added,
> so I recommend a better approach now.
> I assume you already have a Vivado project implementing your FPGA
> design. Even a project with a completely empty FPGA is OK, what matters
> is that you configure the "ZynqMP block" appropriately for the board
> (the Vivado wizard helps you in starting from a default configuration
> with proper DDR timings, among others).
> With the Vivado project you can start the Xilinx XSDK to produce a bsp
> (don't forget to enable the xilpm library in the wizard). The xilpm
> library in the generated bsp has a file called pm_cfg_obj.c. It's the
> "configuration object" that tells the PMU FW how to configure peripherals.
> Now you could go for the "old" approach, the one used for the zcu106
> defconfig currently in Buildroot: using zynqmp-pmufw-builder  you can
> generate a pmufw.bin that contains your configuration object hard-coded.
> This is how the pmufw binaries in zynqmp-pmufw-binaries , and used in
> Buildroot for ZCU106, have been generated.
> But I rather suggest to use the "new" approach. U-Boot SPL since
> v2019.10 can load the PMUFW configuration object at runtime (just like
> Xilinx FSBL does). In this case you can avoid hard-coding the config
> object into the pmufw binary, and use a "standard" PMUFW that works for
> any ZynqMP board. The v2018.3 PMUFW in  has been built in this way.
> For additional explanations on the "new" approach see . I wrote some
> suggestions on how to implement such a workflow for yocto on the
> meta-xilinx mailing list , the underlying idea should apply to
> Buildroot as well.
> I hope this is useful for you. As pointed out by Thomas, your question
> is not very precise, so please add more details on exactly what you want
> to achieve, what you tried and how it failed. Somebody will probably be
> able to help you better.
>  https://github.com/lucaceresoli/zynqmp-pmufw-builder
>  https://github.com/lucaceresoli/zynqmp-pmufw-binaries
>  https://lucaceresoli.net/zynqmp-uboot-spl-pmufw-cfg-load/
>  https://lists.yoctoproject.org/g/meta-xilinx/message/4570
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the buildroot