mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Greg Topmiller <Greg.Topmiller@jdsu.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: RE: Imx51 processor hangs when we do an md 0xf0000000 (memory display) in u-boot
Date: Mon, 18 Apr 2011 02:44:16 -0700	[thread overview]
Message-ID: <F384D1288827C547A75DEBA2647D64BA172AE7EABC@MILEXCH1.ds.jdsu.net> (raw)
In-Reply-To: <20110418072941.GH14770@pengutronix.de>

Thank you for your response.

Is there any way we can put code in u-boot to handle the abort?

Thanks,

Greg

________________________________________
From: Sascha Hauer [s.hauer@pengutronix.de]
Sent: Monday, April 18, 2011 3:29 AM
To: Greg Topmiller
Cc: barebox@lists.infradead.org
Subject: Re: Imx51 processor hangs when we do an md 0xf0000000 (memory display) in u-boot

On Sat, Apr 16, 2011 at 11:14:13AM -0700, Greg Topmiller wrote:
> We're are using the Freescale release L2.6.31_MX51_SDK_0912_Image and
> it will do this on a Freescale Babbage board and our design.  It also
> does the same thing in Linux when we mmap the address 0xf0000000 and
> try to read from it.  It does not hang on the Redboot.bin image
> supplied with the Freescale SDK.  The Redboot dump command displays
> some data.  On the Freescale 3Stack board we get an illegal address
> error in Redboot, but it will hang in u-boot.  We realize this is a
> reserved physical address but would hope that an error of some kind
> would occur rather than locking up the CPU.  Could it be some sort of
> MMU initialization difference between Redboot and u-boot?

I have no idea how redboot maps the memory in the mmu, but barebox and
u-boot use a 1:1 mapping which results in the behaviour you see.
Accessing reserved memory can result in a abort.

Sascha

--
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2011-04-18  9:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-16 18:14 Greg Topmiller
2011-04-18  7:29 ` Sascha Hauer
2011-04-18  9:44   ` Greg Topmiller [this message]
2011-04-18 13:15     ` on enviromen Omar Pighi
2011-04-18 15:03   ` again on enviroment and partition problems Omar Pighi
2011-04-18 17:48     ` Sascha Hauer
2011-04-19  9:17       ` Omar Pighi

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=F384D1288827C547A75DEBA2647D64BA172AE7EABC@MILEXCH1.ds.jdsu.net \
    --to=greg.topmiller@jdsu.com \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.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