Sascha Hauer wrote: > On Wed, Oct 27, 2010 at 03:33:15PM +0200, Juergen Beisert wrote: > > Belisko Marek wrote: > > > I have mini2440 board with barebox running from RAM. > > > I try to start uImage kernel for that platform but I'm little bit > > > confused how to do it. > > > > > > I do tftp uImage and the bootu uImage but it always hangs : > > > > > > commandline: console=ttySAC0,115200 > > > arch_number: 1999 > > > > > > I track down that theKernel pointer point to 0xffffffff (memmap return > > > (void*)-1) which is obviously wrong. > > > If I understand correctly bootu function take first parameter and try > > > to open a file and memmap. If file isn't opened successfully then > > > convert string address which is then taken for > > > theKernel pointer. > > > > > > Is this correct procedure or do I something wrong? > > > > Try to start a zImage with "bootz". On my system 'bootm' and 'bootu' do > > not work. > > bootz is for starting zImages. At least this command has a convenient > name :) > bootz should work on your system aswell. If not, please complain loudly. bootz works here. bootm always complains with the scripts from the generic environment: booting kernel of type uimage from /dev/ram0.kernel Bad Magic Number But: 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'? jbe -- Pengutronix e.K. | Juergen Beisert | Linux Solutions for Science and Industry | Phone: +49-8766-939 228 | Vertretung Sued/Muenchen, Germany | Fax: +49-5121-206917-5555 | Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de/ | _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
