All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robin Theunis <robint91@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-embedded@vger.kernel.org
Subject: ARM target not boot after remap memory
Date: Mon, 13 Sep 2010 13:25:26 +0200	[thread overview]
Message-ID: <AANLkTi=tWwaFHB0DY=j0UaqbYdYJpGJpmWdGC4aMufSw@mail.gmail.com> (raw)

Dear (Embedded)-Kernel-Devs,

I'm trying to build linux 2.6.34.1 for a AT91RM9200 target. The whole
build process is successful because I get correct kernel images and
also a uImage for U-boot.
The U-boot version is 2010.08. I have build the whole system on a
64bit ubuntu machine. I use the latest buildroot to make the toolchain
and etc. At this moment I have a
openocd jtag dongle connected to my target for debug sessions.
I have check that the machine id/type are correct. I have gotten those
error messages of a unsupported target. I have resolved those errors.
The target is self is a AT91RM9200 with 64MiB ram and 16MiB cfi flash.
The boot args of u-boot are "console=ttyS0,115200n8
root=/dev/mtdblock0 rootfstype=jffs2 mem=64M".

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
---

This just loops at that address. Why does it that?
You see that the mmu is enabled and the cpu has remapped the memory.
Does someone have a clue what goes wrong?

Here is the .config and board file.
http://www.on8rth.be/wp-content/uploads/2010/09/dotconfig.txt
http://www.on8rth.be/wp-content/uploads/2010/09/board-robin9200.c

Thank you

Robin Theunis
ON8RTH

             reply	other threads:[~2010-09-13 11:25 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-13 11:25 Robin Theunis [this message]
2010-09-13 12:07 ` ARM target not boot after remap memory 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
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='AANLkTi=tWwaFHB0DY=j0UaqbYdYJpGJpmWdGC4aMufSw@mail.gmail.com' \
    --to=robint91@gmail.com \
    --cc=linux-embedded@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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.