[meta-xilinx] Address location for binaries...

[Alan DuBoff]

On Tue, February 18, 2014 10:29 pm, Mike Looijmans wrote:
> Don't use a gzipped kernel. Just create a "uImage", that will have that header
> that u-boot understands and uncompress itself. So you don't even need gzip
> support in uboot (and you can use lzo to compress the kernel which is much
> faster).

Ok, that was my fault for using a wiki page for the MicroBlaze, I
think...there was a -C gzip in the command...I didn't realize that...duh...

> If you have a gzipped kernel, you cannot load it at (or even near) its boot
> address, because u-boot has to unzip the blob into its final destination at
> 0x8000. I don't recommend it anyway, because u-boot runs less efficiently than
> the kernel (e.g. with data cache disabled).

I can't believe this one is so difficult, stuff like the beaglebone,
raspberrypi, even OMAP and Tegra didn't give me as much problems.

I just want to get to have a booting image so I can start adding packages.

These are the files I am using, from a core-image-basic, and u-boot-xlnx.

the_ROM_image:
{
        [bootloader]zynq_fsbl.elf
        u-boot.elf
        system_wrapper.bit
        [load=0x2a0000]devicetree.dtb
        [load=0x200000]uramdisk.image.gz
        [load=0x8000]uImage.bin
}

Currently I have a mix of stuff, as I wasn't sure how to build a couple yet.

fsbl, bitstream, devicetree.dtb come from the Zedboard demo.

I use their ramdisk to make the uramdisk.image.gz.

mkimage -A arm -O linux -C gzip -n ramdisk -d ramdisk.image.gz uramdisk.image.gz

1) Do I need that compression for the uramdisk.image.gz to be different?
Should I set the address of 0x200000 also ? Does that matter ?

My bootgen line for the above image, is:

bootgen -image bootimage.bif -o i BOOT/BOOT.BIN

I think I need BOOT.BIN, devicetree.dtb uImage and the uramdisk on my BOOT
partition.

uImage command is:

mkimage -A arm -O linux -T kernel -C none -d uImage.bin uImage

2) somehow these files have not been able to boot...I don't completely
understand. I used a Mars Starter from Enclustra in Switzerland, it had a zynq
7020 on it and I booted from the SPI and mounted the rootfs.

With the zedboard, the image names are not so straight forward and/or I don't
seem to have the ramdisk.

Could you explain these files for my dumb brain:

3) This looks like the device tree for the sd card, do I need this ?

uImage--3.8-xilinx+gitf4ff79d44a966ebea6229213816d17eb472b303e-r1-zedboard-zynq7-mmcblk0p2-20140216095642.dtb

4) this looks like the device tree for the ramdisk. But where is my ramdisk? I
think it is the rootfs.cpio but not certain about that.

uImage--3.8-xilinx+gitf4ff79d44a966ebea6229213816d17eb472b303e-r1-zedboard-zynq7-ram-20140216095642.dtb

-- 
Cheers,
Alan