[meta-xilinx] Options for automatically generating BOOT.BIN file for ZC702 using Yocto

[Mike Looijmans]

On 04/05/2014 08:30 PM, Elvis Dowson wrote:
> Hi Mike,
>
> On Apr 5, 2014, at 22:21, Mike Looijmans <mike.looijmans at topic.nl> wrote:
>
>> Basically, the same method as the other boards. You can use the u-boot-zynq-spl.bb recipe from meta-topic as an example, it builds the reference design using XPS, exports the SDK files which the u-boot recipe picks up to build the bootloader. I'm working on a better method to get the ps7_init.[ch], but as it is now, it doesn't need any manual actions, and no external tools like bootgen (well, you need XPS or Vivado to build the logic) to create a complete image from scratch. It also doesn't need an FSBL.
>>
>> Best would be to have only the MIO and DDR configuration in the bootloader, and leave the rest for the kernel to configure. There is no pinmux support yet, but since everything you need is publicly available, anyone with some kernel hacking skill should be able to cook something up. By far the simplest starting point would be "if a device is initialized by the kernel, but not configured, assume it should be connected to the EMIO”.
>
> Suppose I want to use the traditional method (for the moment), and want to get at the u-boot.elf file using Yocto, how would I got about exporting it to the deploy/images folder (e.g. command/script fragment) ?
>
> Is there any examples of any layers using a pre-built zynq_fsbl.elf, u-boot.elf and system_top.bit files to create a BOOT.BIN file using Yocto?

The other u-boot script in the same layer has been doing that:

https://github.com/topic-embedded-products/meta-topic/blob/master/recipes-bsp/u-boot/u-boot-zynq_git.bb

It picks a prebuilt fsbl and combines it with u-boot.bin for deployment.


-- 
Mike Looijmans