[meta-xilinx] Bitstream/Boot.bin/etc - Providers/Virtual targets

[Nathan Rossi]

> -----Original Message-----
> From: meta-xilinx-bounces at yoctoproject.org [mailto:meta-xilinx-
> bounces at yoctoproject.org] On Behalf Of Alan DuBoff
> Sent: Thursday, February 20, 2014 5:47 PM
> To: Mike Looijmans
> Cc: meta-xilinx Mailing List
> Subject: Re: [meta-xilinx] Bitstream/Boot.bin/etc - Providers/Virtual
> targets
> 
> On Wed, February 19, 2014 10:32 pm, Mike Looijmans wrote:
> > Don't expect anything spectacular here - even building completely on a
> RAM
> disk (RAM was cheap too) did not make any difference at all.
> 
> Mike,
> 
> Actually, now that I think about it for a few seconds, that does make
> sense.
> When compiles were hurting for disk access was mainly because our machines
> didn't have enough memory in relation to storage in it's day.
> 
> I guess now that we have so much memory, most of the time is actually
> spend in
> memory anyway, at least for the actual number crunching...as I mentioned I
> don't see a cramp on memory with 8 gigs in most environments, and like to
> have
> at least this much for Android...Android build will make one appreciate
> Yocto!
> ;-)
> 
> Not to digress, I think you have my answer for me, I am so frickin' close.
> 
> I believe I'm down to the devicetree.dtb
> 
> This is what I get upon boot. Loads everything ok, and says:
> 
> -----------------------
> Starting kernel ...
> 
> Error: unrecognized/unsupported device tree compatible list:
> [ 'xlnx,zynq-zed' ]
> 
> Available machine support:
> 
> ID (hex)        NAME
> ffffffff        ARM-Versatile Express
> 000008e0        ARM-Versatile Express
> 00000d32        Xilinx Zynq Platform
> 
> Please check your kernel config and/or bootloader.

Make sure the device tree compatible value matches a supported one, xlnx,zynq-zed was deprecated some time ago. You should use:
compatible = "xlnx,zynq-7000";

Also I believe the kernel will move the dtb after boot so that is can layout the memory better. Which is why the kernel will save the dtb is at a different address to where you loaded it.
(Which is in answer to your other email)

> 
> -----------------------
> 
> This is my bootimage.bif
> 
> {
>         [bootloader]zynq_fsbl.elf
>         u-boot.elf
>         system_wrapper.bit
>         [load=0x2a0000]devicetree.dtb
>         [load=0x200000]uramdisk.image.gz

0x20_0000 - 0x2a_0000 is only 640KB. I assume you have a very small pivot ramdisk?

>         [load=0x8000]uImage.bin
> }
> 
> $64k question, do I need this as my devicetree.dtb, from my deploy/images
> directory ???
> 
> uImage--3.8-xilinx+gitf4ff79d44a966ebea6229213816d17eb472b303e-r1-
> zedboard-zynq7-mmcblk0p2-20140216095642.dtb

There are two dtb's, "zedbard-zynq7-ram*.dtb" and "zedbard-zynq7-mmcblk0p2*.dtb". Use the "zedbard-zynq7-ram*.dtb" if your initial root device is a ramdisk (given you are using loading a ramdisk above this is the one you will want).

You will need to rename it, because the ".bif"/bootgen can't handle characters like "+".

Regards,
Nathan

> 
> Fingers crossed...
> 
> --
> Cheers,
> Alan
> 
> 
> 
> 
> _______________________________________________
> meta-xilinx mailing list
> meta-xilinx at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-xilinx