From: Juergen Beisert <jbe@pengutronix.de>
To: barebox@lists.infradead.org
Subject: Re: command bootu to start kernel
Date: Wed, 27 Oct 2010 16:38:42 +0200 [thread overview]
Message-ID: <201010271638.42404.jbe@pengutronix.de> (raw)
In-Reply-To: <20101027135438.GL6017@pengutronix.de>
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@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2010-10-27 14:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-27 12:42 Belisko Marek
2010-10-27 13:33 ` Juergen Beisert
2010-10-27 13:54 ` Sascha Hauer
2010-10-27 14:03 ` Belisko Marek
2010-10-27 14:38 ` Juergen Beisert [this message]
2010-10-29 6:08 ` Belisko Marek
2010-10-29 7:49 ` Belisko Marek
2010-10-29 8:04 ` Marc Reilly
2010-10-29 8:20 ` Belisko Marek
2010-10-29 8:34 ` Baruch Siach
2010-10-29 8:45 ` Belisko Marek
2010-10-29 8:50 ` Marc Kleine-Budde
2010-10-29 9:04 ` Belisko Marek
2010-10-29 9:12 ` Marc Kleine-Budde
2010-10-29 9:21 ` Belisko Marek
2010-10-29 9:26 ` Marc Kleine-Budde
2010-10-29 9:30 ` Uwe Kleine-König
2010-10-29 9:31 ` Belisko Marek
2010-10-29 12:36 ` Juergen Beisert
2010-11-02 13:53 ` Belisko Marek
2010-10-27 13:46 ` Sascha Hauer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201010271638.42404.jbe@pengutronix.de \
--to=jbe@pengutronix.de \
--cc=barebox@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox