On Wed, Jun 10, 2015 at 2:03 AM, Edward Wingate wrote:
> Thanks, Nathan, for your help. It worked, with a little oddity I don't
> understand.
>
> In my uEnv.txt, I set both fdt_high and initrd_high to 0x1000 and
> fdt/initrd are now loaded to 1st 256 MB:
>Loading Kernel Image ... OK
>L
Typo in last email, I used "mem=256M", not "mem=256MB"
On Tue, Jun 9, 2015 at 9:03 AM, Edward Wingate wrote:
> Thanks, Nathan, for your help. It worked, with a little oddity I don't
> understand.
>
> In my uEnv.txt, I set both fdt_high and initrd_high to 0x1000 and
> fdt/initrd are now loaded
Thanks, Nathan, for your help. It worked, with a little oddity I don't
understand.
In my uEnv.txt, I set both fdt_high and initrd_high to 0x1000 and
fdt/initrd are now loaded to 1st 256 MB:
Loading Kernel Image ... OK
Loading Ramdisk to 0f44c000, end 02f2 ... OK
Loading Device Tre
On Tue, Jun 9, 2015 at 4:06 AM, Edward Wingate wrote:
>
> I am using Yocto with meta-xilinx layer to create a distribution for a
> custom Zynq 7000 board with 512MB RAM. In my uEnv, I'm loading the
> kernel to 0x0010_, device tree to 0x0190_ and ramdisk image to
> 0x0210_.
>
> Later in
I am using Yocto with meta-xilinx layer to create a distribution for a
custom Zynq 7000 board with 512MB RAM. In my uEnv, I'm loading the
kernel to 0x0010_, device tree to 0x0190_ and ramdisk image to
0x0210_.
Later in the boot process, I see this:
Loading Kernel Image ... OK
L
