On Fri, 24 Jun 2016, Wolfgang Denk wrote: > Dear Vinoth, > > In message > <CAJst-kFZjA_Nq7K25CEPri9Aq7r=-mmtgyenywwg-p2crn4...@mail.gmail.com> you > wrote: > > > > I am using the following command to create uImage. Here in the architecture > > argument I am not seeing any option corresponding to the Intel-x86_64. So I > > had used x86, which I am not sure is valid or not. The kernel is 64 bit. > > > > mkimage -A x86 -O linux -T kernel -C none -a 0x100000 -e 0x00000 -n Linux > > -d vmlinux-4.4.6-ina uImage > > Image Name: Linux > > Created: Fri Jun 24 10:35:40 2016 > > Image Type: Intel x86 Linux Kernel Image (uncompressed) > > Data Size: 21966248 Bytes = 21451.41 kB = 20.95 MB > > Load Address: 00100000 > > Entry Point: 00000000 > > This makes no sense to me. When the kernel image is loaded to RAM > starting at address 0x00100000, then ther eis no valid code at address > 0x00000000. So 0x00000000 cannot be a valid entry oint address. The > entry point address must be somewhare in the range between "load > address" and "load address + size of uncompressed kernel image". > > > Error: Invalid Boot Flag (found 0x0000, expected 0xaa55) > > Setup at 0x000000 > > Magic signature not found > > > > Is is I need to load setup.bin also?
i'm sure i'm not adding much to this discussion, but 0xaa55 is the last two bytes of an MBR that identifies that 512-byte block as a legitimate master boot record, so *something* is looking for an MBR and not finding it. rday -- ======================================================================== Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ======================================================================== _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot