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

[Alan DuBoff]

On Thu, February 20, 2014 12:30 am, Nathan Rossi wrote:
> 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)

Damn, I thought this was my problem for certain, in that I just checked in the
binary and there is a string for the above, so I figured it had to be an older
bootgen from the 14.4 toolkit...I made sure I have the 2013.4 tools in, and
redid it, but now I get:

------------------------
Starting kernel ...

data abort
pc : [<0000800c>]          lr : [<1ff76b7c>]
sp : 1fb55bb8  ip : ffffffff     fp : 00000000
r10: 1ffabbcc  r9 : fff80225     r8 : 1fb55f68
r7 : 1ff76c9c  r6 : 00000000     r5 : 00008000  r4 : 1ffac148
r3 : 000016b9  r2 : 1f7c9000     r1 : b55ff723  r0 : 00000000
Flags: nzCv  IRQs off  FIQs off  Mode SVC_32
Resetting CPU ...

resetting ...
------------------------

> 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).

I have the right one and did rename it.

Hmmm...it doesn't like something...seems I am so close...but no cigar...

-- 
Cheers,
Alan