Hi, I have no experience with the mini2440, but: On Friday, October 29, 2010 06:49:52 pm Belisko Marek wrote: > On Fri, Oct 29, 2010 at 8:08 AM, Belisko Marek <marek.belisko@xxxxxxxxx> > >> me@host$ file arch/arm/boot/uImage > >> arch/arm/boot/uImage: u-boot legacy uImage, > >> Linux-2.6.31-00770-g54c3fe6-dir, Linux/ARM, OS Kernel Image (Not > >> compressed), 2350016 bytes, Mon Oct 25 16:58:30 2010, Load Address: > >> 0x40008000, Entry Point: 0x40008000, Header CRC: 0x17A7330B, Data CRC: > >> 0x888DAA63 > >> > >> Anything wrong with the uImage (built with "make uImage") or the > >> command 'bootm'? The load and entry point are 0x400... here > > > > Instead bootm for my uImage works: > > bootm uImage > > Verifying Checksum ... OK > > Image Name: Linux-2.6.32-rc8 > > Created: 2010-09-27 8:36:01 UTC > > Image Type: ARM Linux Kernel Image (uncompressed) > > Data Size: 2058404 Bytes = 2 MB > > Load Address: 30008000 > > Entry Point: 30008000 > > OK and 0x300.. here I've no idea how your RAM is mapped, but verify that it is being loaded to the correct address. (also check that it's not overlapping your barebox, malloc or stack) > > commandline: console=ttySAC0,115200 > > arch_number: 1999 > > > > Starting kernel ... > > Despite of loading kernel is working kernel isn't started for > mini2440(from u-boot works fine). It hang at: > Uncompressing > Linux..................................................................... > ............................................................. done, booting > the kernel. Also enable low level debugging and the earlyprintk in your kernel - maybe the kernel is running but crashes before it gets ti initializing the console. Cheers Marc _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
