From: Jerry Van Baren <gerald.vanbaren@ge.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] booting the kernel
Date: Tue, 21 Oct 2008 13:47:51 -0400 [thread overview]
Message-ID: <48FE15C7.608@ge.com> (raw)
In-Reply-To: <c5ee099c0810211035x7c430968sb30d59dbcbce6600@mail.gmail.com>
Mathieu Dube wrote:
> Hi,
> Im trying to boot the linux kernel with uboot and it just hangs so I
> tried the instructions in the Linux PostMortem FAQ entry.
>
> I'd like to know if I could be doing something obviously wrong here:
>
> the kernel I use is for freescale imx31_litekit. I've booted it using the
> logicpd loader so I know it works.
>
> I use the arch/arm/boot/Image with mkimage like this:
>
> mkimage -A arm -O linux -T kernel -C none -a 86000000 -e 86000000 -d Image
> image.bin
>
> are the load address and entry point ok? if not how can I determine which
> value they should have?
Sorry, I don't know.
> Starting kernel ...
>
> and hangs there, if I use my jtag I can see that the core is running ie: it
> doesnt crash. Btw I've also tried with the jtag attached so thats not the
> problem.
Do you have a console configured and enabled?
> __log_buf in my System.map is at c035c168
> and CONFIG_KERNEL_START is c0000000
>
> so am I right to do
>
> md 8635c168 ?
>
> there doesnt seem to be anything interesting around this address...
Try 0035c168 - I'm not a arm-man, but the linux kernel traditionally
relocates itself at location 00000000 and remaps itself to the virtual
address c0000000. When you are looking with the debugger, you need to
drop the "c" to get the physical address.
> what else could I try to figure out why the kernel isnt booting?
>
> thanks a lot.
> -M
HTH,
gvb
next prev parent reply other threads:[~2008-10-21 17:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-21 17:35 [U-Boot] booting the kernel Mathieu Dube
2008-10-21 17:47 ` Jerry Van Baren [this message]
2008-10-22 1:10 ` Roman Mashak
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=48FE15C7.608@ge.com \
--to=gerald.vanbaren@ge.com \
--cc=u-boot@lists.denx.de \
/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