From: Daniel Smith <dpsmith@praxiseng.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Kernel boot problems
Date: Thu, 28 Jul 2011 11:47:28 -0400 [thread overview]
Message-ID: <j0s0bb$brf$1@dough.gmane.org> (raw)
In-Reply-To: <F7C0AA5DD1508F4789E10B6CC9BB75DB04B7A25E@nzc-ap-xch-02.ap.trimblecorp.net>
On 7/27/2011 10:20 PM, Bernard Mentink wrote:
> 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
For (A), I ran into a similar issue cns3xxx which has a similar core as
your imx31. You can see the thread here (http://goo.gl/HEOVK). Basically
go look in the Makefile.boot for your sub-arch and see what is set for
the zreladdr. If it is different than 0x20008000, then in your kernel
recipe you need to set the UBOOT_ENTRYPOINT and UBOOT_LOADADDRESS to
your zreladdr.
Hope that helps!
V/r,
Daniel P. Smith
prev parent reply other threads:[~2011-07-28 15:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-28 2:20 Kernel boot problems Bernard Mentink
2011-07-28 11:22 ` 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 [this message]
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='j0s0bb$brf$1@dough.gmane.org' \
--to=dpsmith@praxiseng.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox