[meta-xilinx] SPL Method on ZCU102 - Missing files?
nathan at nathanrossi.com
Tue Mar 7 07:04:12 PST 2017
On 7 March 2017 at 15:40, Giordon Stark <kratsg at gmail.com> wrote:
> I re-ran on the latest distro (I was on kogoroth and switched to morty).
> Here's what I see in the list of files:
> On Mon, Mar 6, 2017 at 6:14 PM Oleg K Dzhimiev <oleg at elphel.com> wrote:
>>> I have a few questions based on this:
>>> - where is boot.bin?
>>> - where is u-boot.img / u-boot-dtb.img?
>> Check with the poky/meta/recipes-bsp/u-boot/u-boot.inc look for "deploy"
>> Also, boot.bin should be the smallest in size.
> I see the deploy function:
> but this looks really confusing and hard to read. Comparing to what I see
> it looks like "SPL_BINARY" is not set and would need to be set to get this
> working. I don't know where to set this. It also looks like, similarly,
> UBOOT_ENV is not set as well. So uEnv.txt does not get made.
Currently ZCU102 does not have boot.bin generated by default, for
1. No one has sent patches for it, and I don't have hardware so I
haven't tested or been able to look at getting it working
2. u-boot-xlnx has a few different 'zcu102' configs/psu_init setups
To get it working, SPL_BINARY = "spl/boot.bin" should be enough (you
can set this in conf/local.conf or in the machine.conf) as the
boot.bin should be being built regardless. But you will need to use
u-boot-xlnx, and you will likely need to select a psu_init* that works
for your board (https://github.com/Xilinx/u-boot-xlnx/tree/master/board/xilinx/zynqmp
there is a few for zcu102).
Additionally for custom psu_init files, the platform-init recipe
provider setup is not there just yet. There are some patches on my
(https://github.com/nathanrossi/meta-xilinx/tree/nrossi/wip) for it if
>>> - where is the root filesystem (eg: to populate the second partition)? I
>>> only see a ramdisk which goes in the first partition (*cpio.gz)
>> a. convert cpio.gz to tar.gz
>> b. in the rootfs recipe (zynq-base.bb?) specify:
>>> IMAGE_FSTYPES = "tar.gz"
> Looks like this is getting made. I'm not sure why it wasn't before!
>> Then don't forget about bootargs.
> Don't forget about it? Right now, I manually create the uEnv.txt file and
> fill it in myself (including the bootargs and uenvcmd myself manually). Is
> there a more automated way to set this?
You can set bootargs in the chosen node of the device tree if you
want. But u-boot will overwrite that anyway if you set bootargs within
the u-boot environment.
>>> - where is uImage? is it just "Image"?
>> Most likely.
> How can I confirm?
Image is the kernel, should be in your machine's deploy/images directory.
The kernel does not make uImage for arm64, 'Image' is a special type
that is new for arm64 that is a binary image packed with a info
header. U-Boot can read them with the booti command.
More information about the meta-xilinx