From: Marc Reilly <marc@cpdesign.com.au>
To: barebox@lists.infradead.org
Subject: Re: command bootu to start kernel
Date: Fri, 29 Oct 2010 19:04:16 +1100 [thread overview]
Message-ID: <201010291904.16717.marc@cpdesign.com.au> (raw)
In-Reply-To: <AANLkTikBmg33g-Uh=_fEtvkN6n6GZAi71Lc5tFm51yjJ@mail.gmail.com>
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@gmail.com>
> >> 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@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2010-10-29 8:03 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
2010-10-29 6:08 ` Belisko Marek
2010-10-29 7:49 ` Belisko Marek
2010-10-29 8:04 ` Marc Reilly [this message]
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=201010291904.16717.marc@cpdesign.com.au \
--to=marc@cpdesign.com.au \
--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