For Zynq, you need to adjust your system dependencies.

Same thing, same arguments. Se your dependencies to nothing and provide a dummy .elf/.bin if necessary.

Otherwise you need to disable the dependency path for FSBL.

The FSBL is required by bootbin/bootgen. The configuration of this is documented in the meta-xilinx-core/recipes-bsp/bootbin/* files. I don't know of the SPL flow uses bootgen, if it does you need to configure it for SPL.

If you are not using bootgen, then you need to change the system dependencies.

Your IMAGE_BOOT_FILES has a dependency on 'boot.bin', which triggers a dependency on xilinx-bootin as the provider. Remove/change this value.

Where this is defined is:

https://github.com/Xilinx/meta-xilinx/blob/6cbae9509694a2ed65435f391c5a900e4c1d3908/meta-xilinx-core/conf/machine/include/machine-xilinx-default.inc#L40

Instead of 'xilinx-bootbin' it probably should be pointing to 'virtual/boot-bin' as well, but the key is IMAGE_BOOT_FILES is used as a key for the WKS_FILE_DEPENEDS, which is used for a wic image to build the components necessary to construct the image. This is likely what you are hitting.

--Mark

On 2/15/23 9:43 AM, Martin Siegumfeldt wrote:
    SPL flow has nothing to do with proprietary tools or not. You still need the
    firmware component(s) to boot and use the SoC's components. What it changes
    is what loads parts of the configuration. The SPL flow itself is not
    currently being tested by us. If you get it working, please post
    instructions on what you did. Lots of people claim to be using it, but
    everyone I've talked to has custom hacks and nothing that I've been able to
    replicate in a way to make this generally useful to everyone.

We are building just for Zynq 7000 family, hence no need for firmware. Init code exported from Vivado is simply used by u-boot for building the SPL, this appears to be working for other (u-boot) in-tree Zynq 7000 based boards and works flawless for us as well.

What I expect to be a bug (correct me if I am wrong) is the fsbl-firmware recipe append introduced in the BSP layer (through https://github.com/Xilinx/meta-xilinx/commit/3182c3c10ffba0d92563bf83d9c583a30be3fabc <https://github.com/Xilinx/meta-xilinx/commit/3182c3c10ffba0d92563bf83d9c583a30be3fabc>) appending to the recipe residing in the standalone layer. However the layer.conf of the BSP layer do not describe this layer-dependency. I would thus expect that either layer.conf should describe this dependency or potentially somewhow make the dependency dynamic for these users actually utilizing the FSBL.

Thanks,
Martin




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5157): 
https://lists.yoctoproject.org/g/meta-xilinx/message/5157
Mute This Topic: https://lists.yoctoproject.org/mt/96982329/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/meta-xilinx/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to