On 4 April 2017 at 17:20, Michal Simek <michal.si...@xilinx.com> wrote: > On 3.4.2017 13:38, Jean-Francois Dagenais wrote: >> >>> On Apr 3, 2017, at 02:55, Michal Simek <michal.si...@xilinx.com> wrote: >>> >>> This is not only one way how to configure system. You can use >>> psu_init*.tcl and configure chip through jtag and then you don't need >>> this .c/.h files. >>> You should be able to see warning already about it if you miss that files. >> >> Mmh. I had thought of that, but it seemed like this scenario might have been >> a >> minority issue. I guess this is a very yocto-centric problem. Warnings >> emitted >> inside builds that bitbake spawns are only visible in a log file for each >> steps >> (configure, compile, etc.) inside each recipe's work dir and so they are >> completely invisible to the operator that invokes bitbake. >> >> Perhaps I should come up with a strategy to emerge this particular warning in >> the u-boot-xlnx_%.bb recipe? >> >> Thoughts?
The meta-xilinx layer has some logic to cause an error when these files are not available (currently only for zynq, this should work fine for the zynqmp use case as well). Specifically if nothing is providing the platform init files it will cause a dependency chain error. However due to u-boot source providing the platform init for some boards there is a list of u-boot configs that don't trigger the error on purpose. This could be extended to check that the symbols (the ps*_init ones) are compiled and included in the output u-boot-spl elf as a sanity check. Which would be more complete than just validating the files are there. Regards, Nathan _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
