From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Robin Theunis <robint91@gmail.com>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-embedded mailing list <linux-embedded@vger.kernel.org>
Subject: Re: ARM target not boot after remap memory
Date: Mon, 13 Sep 2010 13:53:10 +0100 [thread overview]
Message-ID: <20100913125310.GI30787@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <AANLkTi=dT1uMrRctB4=Hvh35zVc-DtReWmHj-18cd9XT@mail.gmail.com>
BTW, Please do not drop CCs.
On Mon, Sep 13, 2010 at 02:48:18PM +0200, Robin Theunis wrote:
> Hi Russell,
>
> Yes I have tested it. I made a breakpoint at 0x2008000 and viewed that
> the r1 register and there in I found the correct ID.
>
> Robin
>
> 2010/9/13 Russell King - ARM Linux <linux@arm.linux.org.uk>:
> > On Mon, Sep 13, 2010 at 02:07:51PM +0200, Mike Rapoport wrote:
> >> (add LAKLM to CC)
> >
> >>> The problem is now when linux kernel is booting, nothing happens.
> >>>
> >>> ---
> >>> U-Boot> bootm
> >>> ## Booting kernel from Legacy Image at 21000000 ...
> >>> Image Name: Linux-2.6.34.1robin9200v1.0
> >>> Image Type: ARM Linux Kernel Image (uncompressed)
> >>> Data Size: 1811796 Bytes = 1.7 MiB
> >>> Load Address: 20008000
> >>> Entry Point: 20008000
> >>> Verifying Checksum ... OK
> >>> Loading Kernel Image ... OK
> >>> OK
> >>>
> >>> Starting kernel ...
> >>>
> >>> 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
> >
> > Probably __error. Either your machine isn't supported, or the kernel
> > doesn't recognise your processor.
> >
> > Is your version of uboot sufficiently recent that it passes the correct
> > machine ID in r1 ?
> >
WARNING: multiple messages have this Message-ID (diff)
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM target not boot after remap memory
Date: Mon, 13 Sep 2010 13:53:10 +0100 [thread overview]
Message-ID: <20100913125310.GI30787@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <AANLkTi=dT1uMrRctB4=Hvh35zVc-DtReWmHj-18cd9XT@mail.gmail.com>
BTW, Please do not drop CCs.
On Mon, Sep 13, 2010 at 02:48:18PM +0200, Robin Theunis wrote:
> Hi Russell,
>
> Yes I have tested it. I made a breakpoint at 0x2008000 and viewed that
> the r1 register and there in I found the correct ID.
>
> Robin
>
> 2010/9/13 Russell King - ARM Linux <linux@arm.linux.org.uk>:
> > On Mon, Sep 13, 2010 at 02:07:51PM +0200, Mike Rapoport wrote:
> >> (add LAKLM to CC)
> >
> >>> The problem is now when linux kernel is booting, nothing happens.
> >>>
> >>> ---
> >>> U-Boot> bootm
> >>> ## Booting kernel from Legacy Image at 21000000 ...
> >>> ? ?Image Name: ? Linux-2.6.34.1robin9200v1.0
> >>> ? ?Image Type: ? ARM Linux Kernel Image (uncompressed)
> >>> ? ?Data Size: ? ?1811796 Bytes = 1.7 MiB
> >>> ? ?Load Address: 20008000
> >>> ? ?Entry Point: ?20008000
> >>> ? ?Verifying Checksum ... OK
> >>> ? ?Loading Kernel Image ... OK
> >>> OK
> >>>
> >>> Starting kernel ...
> >>>
> >>> 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
> >
> > Probably __error. ?Either your machine isn't supported, or the kernel
> > doesn't recognise your processor.
> >
> > Is your version of uboot sufficiently recent that it passes the correct
> > machine ID in r1 ?
> >
next prev parent reply other threads:[~2010-09-13 12:53 UTC|newest]
Thread overview: 17+ 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:07 ` Mike Rapoport
2010-09-13 12:40 ` Russell King - ARM Linux
2010-09-13 12:40 ` Russell King - ARM Linux
2010-09-13 12:48 ` Robin Theunis
2010-09-13 12:51 ` Russell King - ARM Linux
2010-09-13 13:11 ` Robin Theunis
2010-09-13 12:53 ` Russell King - ARM Linux [this message]
2010-09-13 12:53 ` Russell King - ARM Linux
2010-09-13 12:12 ` Johannes Stezenbach
[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=20100913125310.GI30787@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--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 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.