On Tue, Jul 24, 2012 at 05:43:28PM +0200, Markus Hubig wrote: > I looked at every single byte on the internet an I found some information > that in order to get this bad-ass relocation to work, one needs to adapt > at91bootstrap to work with u-boot. Could this be my problem? At the moment > I'm using the original at91bootstrap from taskit. > > Here is what I think the problem could, maybe, be: > > 1. Board gets powered on. > 2. at91bootstrap magically starts. > 3. It reads IMG_SIZE from IMG_ADDRESS and writes it to JUMP_ADDR in RAM. > - IMG_ADDRESS is where I write u-boot to inside NAND? > - IMG_SIZE should be the size of u-boot.bin? (exactly or is a bigger > size OK?) > - JUMP_ADDR is where u-boot is relocated to in RAM. Should be > CONFIG_SYS_TEXT_BASE? > 4. at91bootstrap sets the PC to JUMP_ADDR and starts u-boot. > > Since IMG_SIZE in at91bootstrap is not the size of my new u-boot.bin it > crashes after relocation!
Year! This was exactly my problem! Building a new at91bootstrap with a bigger IMG_SIZE solved it. Now U-Boot starts up! Im getting closer to a patch! ;-) Cheers, Markus _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
