The panda board has 0x80000000 + 0x40000000 available memory in u-boot. I always make the kernel uImage 0x82000000, the uInitrd 0x87000000, and the FDT 0x86000000. Of course the mkimage cmd has to match whatever loadaddr's you choose for the kernel uImage, and all zeros for initrd If you have problems at "starting kernel ..." you might see if adding "earlyprintk" to BOOTARGS helps. You might try not booting with the initrd parameter, something like this: bootm 0x82000000 - 0x86000000 Good luck, -Jon Disnard On Mon, Sep 9, 2013 at 1:31 PM, Nigel Sollars <nsollars@xxxxxxxxx> wrote: > Hi, > > Sorry for the super late response, > > I think perhaps I need information with regards to the required > LOADADDR=0xfoo and basically the boot.scr. > > For the LOADADDR ( on make uImage ) i use 0x80008000 and the same for > fatload and bootm. > > If I use anything else ( as suggested ) the panda stops at starting kernel > and both leds are on solid. > > Nige > > > On Mon, Sep 2, 2013 at 5:55 PM, Peter Robinson <pbrobinson@xxxxxxxxx> wrote: >> >> On Mon, Sep 2, 2013 at 3:51 AM, Nigel Sollars <nsollars@xxxxxxxxx> wrote: >>> >>> Hi all, >>> >>> I was wondering if anyone has solved the uboot LOADADDR issue with >>> Pandaboard ( ES ) .. Ive been toying with newer kernels but keep getting hit >>> with the data abort after the kernel is loaded ( 0x80008000 ) for Omap, Omap >>> 4 in my case. >>> >> >> What LOADADDR issue? what addresses are you using for the kernel/initrd? >> >> Peter >> > > > > -- > “Science is a differential equation. Religion is a boundary condition.” > > Alan Turing > > _______________________________________________ > arm mailing list > arm@xxxxxxxxxxxxxxxxxxxxxxx > https://admin.fedoraproject.org/mailman/listinfo/arm -- -Jon _______________________________________________ arm mailing list arm@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/arm
