From: "Bernard Mentink" <Bernard_Mentink@trimble.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Kernel boot problems
Date: Thu, 28 Jul 2011 14:20:04 +1200 [thread overview]
Message-ID: <F7C0AA5DD1508F4789E10B6CC9BB75DB04B7A25E@nzc-ap-xch-02.ap.trimblecorp.net> (raw)
Hi Guys,
I have got a bit further with my efforts to boot linux on an imx31 based
platform using u-boot.
My console output is now:
----------------------------------------------------------------
uboot> bootm 80100000
## Booting kernel from Legacy Image at 80100000 ...
Image Name: Angstrom/2.6.36/mx31ads
Created: 2011-07-28 2:03:27 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1586172 Bytes = 1.5 MiB
Load Address: 8f000000
Entry Point: 8f000000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
-------------------------------------------------------------------
So it seems to be getting to the 1st part of the kernel boot process,
then hangs (I presume the last line comes from kernel code.)
I don't know if the kernel is hanging, or if I don't have any more
serial out ....
I am passing "console=ttymxc0,115200" to the kernel ..
Can someone confirm:
A) If I have the correct Entry point, or does this need to be offset
into the kernel? ..
B) Is the serial console parameters correct?
C) What is the correct way to set up the memory map? (my ram starts at
0x80000000, ends at 0x8fffffff)
D) Is there a way to debug initial kernel stuff with serial output?
In the above, I have decompressed the kernel to the top of the 256M ram,
but have only advertised 120M via the bootloader ... for now, not
knowing what is correct and not wanting the kernel
to stomp all over itself running in ram.
Many Thanks,
Bernie
next reply other threads:[~2011-07-28 2:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-28 2:20 Bernard Mentink [this message]
2011-07-28 11:22 ` Kernel boot problems Gary Thomas
2011-07-28 12:51 ` Andrea Adami
2011-07-28 20:51 ` Bernard Mentink
2011-07-28 21:39 ` Gary Thomas
2011-07-28 22:10 ` Bernard Mentink
2011-07-28 22:41 ` Gary Thomas
2011-07-28 23:03 ` Bernard Mentink
2011-07-29 1:18 ` Bernard Mentink
2011-07-29 1:41 ` Bernard Mentink
2011-07-29 4:07 ` Charles Manning
2011-07-31 20:57 ` Bernard Mentink
2011-07-28 15:47 ` Daniel Smith
-- strict thread matches above, loose matches on Subject: below --
2001-01-28 0:14 kernel " Derek Benson
2001-01-28 0:49 ` Andre Hedrick
2001-01-27 20:58 Ryan Hairyes
2001-01-27 21:46 ` Joe deBlaquiere
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=F7C0AA5DD1508F4789E10B6CC9BB75DB04B7A25E@nzc-ap-xch-02.ap.trimblecorp.net \
--to=bernard_mentink@trimble.com \
--cc=openembedded-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.