From: Johannes Stezenbach <js@sig21.net>
To: Robin Theunis <robint91@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-embedded@vger.kernel.org
Subject: Re: ARM target not boot after remap memory
Date: Mon, 13 Sep 2010 14:12:47 +0200 [thread overview]
Message-ID: <20100913121247.GA4003@sig21.net> (raw)
In-Reply-To: <AANLkTi=tWwaFHB0DY=j0UaqbYdYJpGJpmWdGC4aMufSw@mail.gmail.com>
On Mon, Sep 13, 2010 at 01:25:26PM +0200, Robin Theunis wrote:
>
> Uncompressing Linux... done, booting the kernel.
> ---
>
> Here is stalls. With my jtag probe I can locate the problem.
>
> ---
> > halt
> target state: halted
> target halted in ARM state due to debug-request, current mode: Supervisor
> cpsr: 0x600000d3 pc: 0xc000af3c
> MMU: enabled, D-Cache: enabled, I-Cache: enabled
> > arm disassemble 0xc000af3c
> 0xc000af3c 0xeafffffe B 0xc000af3c
> ---
>
> This just loops at that address. Why does it that?
Maybe it panicked but you can't see the message since
you have not enabled EARLY_PRINTK.
Since you have JTAG, you could also dump the printk
buffer __log_buf to see the message.
HTH
Johannes
next prev parent reply other threads:[~2010-09-13 12:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-13 11:25 ARM target not boot after remap memory Robin Theunis
2010-09-13 12:07 ` Mike Rapoport
2010-09-13 12:40 ` Russell King - ARM Linux
[not found] ` <AANLkTi=dT1uMrRctB4=Hvh35zVc-DtReWmHj-18cd9XT@mail.gmail.com>
2010-09-13 12:53 ` Russell King - ARM Linux
[not found] ` <20100913125140.GH30787@n2100.arm.linux.org.uk>
2010-09-13 13:11 ` Robin Theunis
2010-09-13 12:12 ` Johannes Stezenbach [this message]
[not found] ` <AANLkTiksacwuOwqJGZ0F3M1jhZ6Srr88wbfBQodOGOAt@mail.gmail.com>
2010-09-13 14:31 ` Fwd: " Robin Theunis
2010-09-13 17:26 ` Johannes Stezenbach
2010-09-13 18:28 ` Robin Theunis
2010-09-13 19:12 ` Robin Theunis
2010-09-13 21:41 ` Wolfgang Denk
2010-09-14 5:32 ` Robin Theunis
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=20100913121247.GA4003@sig21.net \
--to=js@sig21.net \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robint91@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).