[meta-xilinx] Custom ps7_init_gpl in Yocto Project

[Jean-Francois Dagenais]

Hi Jek, Xilinx people,

> On Jul 7, 2019, at 12:51, Jek F. <jek.fessia at gmail.com> wrote:
> 
> i'm a newbie and i'm tring to build an image for microzed with a custom ps7_init_gpl created in Vivado. I tried to create a custom layer (meta-mylayer/recipes-bsp/platform-init/platform-init.bbappend) to append ps7_init_gpl files but this didn't work. Which is the right way to Insert ps7_init_gpl files in Yocto Project?
> 

I also had trouble with this. I worked around it by changing xilinx-init-platform.bbclass:

-PLATFORM_INIT_DIR ?= "/usr/src/xilinx-platform-init"
+PLATFORM_INIT_DIR ?= "/usr/lib/xilinx-platform-init"

I was not using platform-init per se but our own recipe which declares it is providing "virtual/xilinx-platform-init". So my u-boot recipe was indeed pulling on my platform-init files. And my custom platform-init recipe was indeed providing the psu_init_gpl.[ch] files in the default package. But somehow do_prepare_recipe_sysroot did not put the psu_init_gpl files under tmp/work/mymachine/u-boot/*/recipe_sysroot/usr/src ?

I don't know exactly why it didn't work with /usr/src because I had to move on. Perhaps there is a special case in populate_recipe_sysroot for /usr/src? I know normally, the /usr/src contents are collected by the "${PN}-dbg" packaging, not the default "${PN}" packaging.

It may be a regression caused by an update to the poky layer. The original code in xilinx-init-platform.bbclass from Nathan is dated 2017-01-14 which would be 2-3 Yocto releases back.

Hope this helps!