That is great news!
> On Jun 3, 2019, at 14:07, Manjukumar Harthikote Matha <manju...@xilinx.com>
> wrote:
>
> Hi All,
>
> We plan to release warrior by end of month.
> We also want to see if we can backport patches of u-boot from Luca to enable
> cleaner SPL flow for PMU config objects.
> If we cannot do it by 6/30, we want to make sure we can add it after the
> release branch is cut.
> Please see:
> https://lucaceresoli.net/zynqmp-uboot-spl-pmufw-cfg-load/
> or
> https://www.linkedin.com/pulse/booting-u-boot-spl-zynqmp-step-forward-luca-ceresoli/
Thanks again Luca. Hey, here's my question from the post comment, and a bonus
one:
* Does this mean we should switch to mainline u-boot or does xilinx/u-boot
closely tracks that mainline? What are the big pieces from xilinx/u-boot not
yet upstreamed?
* What do you guys do to get the pm_cfg_obj.c generated? Manually? I have my
own provider recipe for virtual/hdf which tracks internal releases made by our
Vivado people. So far, I have exploited the hdf opaquely through
meta-xilinx-tools. I was hoping to keep on generating pm_cfg_obj.c completely
automatically.
Switching to SPL boot flow compromises this part. So I am currently thinking of
still generating it with the fsbl_git.bb recipe from meta-xilinx-tools. I have
"sabotaged" the fsbl recipe through a bbappend which does this:
# replace fsbl's do_deploy:
do_deploy() {
install -Dm 0644
${B}/${XSCTH_PROJ}/zynqmp_fsbl_bsp/psu_cortexa53_0/libsrc/xilpm_v*/src/pm_cfg_obj.c
${DEPLOYDIR}/
}
# don't waste time compiling and installing:
do_compile[noexec] = "1"
do_install[noexec] = "1"
This way, only the do_configure is important and I exploit the deploy to
transport the pm_cfg_obj.c from fsbl to standalone:pmu-firmware where I can
pull on this and use it:
my pmu-firmware_2019.1.bbappend:
SRC_URI += "\
file://0001-Load-XPm_ConfigObject-at-boot.patch \
"
do_configure[mcdepends] = "multiconfig:pmu:dublin:fsbl:do_deploy"
# Inspired by Luca's zynqmp-pmufw-builder
do_configure_append () {
sed 's!"pm_defs.h"!"${S}/lib/sw_services/xilpm/src/common/pm_defs.h"!' \
${DEPLOY_DIR_IMAGE}/pm_cfg_obj.c > ${B}/pmu-firmware/pm_cfg_obj.c
}
I have a feeling this is way overkill... but I don't want to loose out on
auto-generated freebies when we upgrade Vivado and meta-xilinx-tools. These
freebies are still a bit opaque to me at this point, might not be worth all the
fuss? Anyone has any ideas on this?
Thanks for your help guys!
/jfd
--
_______________________________________________
meta-xilinx mailing list
meta-xilinx@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-xilinx
