Hi Belisko, On Tue, May 6, 2014 at 12:34 PM, Belisko Marek <marek.beli...@gmail.com> wrote: > Hi Abdullah, > > On Tue, May 6, 2014 at 10:55 AM, Abdullah YILDIZ > <abdullah.ma...@gmail.com> wrote: >> I'm trying to understand how u-boot loads zImage into RAM. >> >> mkimage is called as >> >> mkimage -A arm -O linux -T kernel -C none -a 0x80008000 -e 0x80008040 >> -d arch/arm/boot/zImage /bootImage/uImage >> Why is entry point different from load address of uImage? >> Here, 'a' stands for load address and 'e' stands for entry point (64 >> bytes are used for wrapping?). However, when loading uImage from >> u-boot, boot operation starts at address 0x80100000. Furthermore, >> u-boot recognizes the load address and entry point as 0x80008000. > Kernel uImage is loaded from NAND to ram at address which $loadaddr > points to (check print $loadaddr) > or env command which loading kerenl image from NAND. > Then by bootm command is copied to address which is specified in > mkimage (e.g. 0x80008000). Hope this helps.
Kind regards. abdullah _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
