From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from exprod7og109.obsmtp.com ([64.18.2.171]) by canuck.infradead.org with smtp (Exim 4.72 #1 (Red Hat Linux)) id 1QBA75-0008Fq-Av for barebox@lists.infradead.org; Sat, 16 Apr 2011 18:20:56 +0000 From: Greg Topmiller Date: Sat, 16 Apr 2011 11:14:13 -0700 Message-ID: Content-Language: en-US MIME-Version: 1.0 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0667830116==" Sender: barebox-bounces@lists.infradead.org Errors-To: barebox-bounces+u.kleine-koenig=pengutronix.de@lists.infradead.org Subject: Imx51 processor hangs when we do an md 0xf0000000 (memory display) in u-boot To: "barebox@lists.infradead.org" --===============0667830116== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_F384D1288827C547A75DEBA2647D64BA172BA39F6BMILEXCH1dsjds_" --_000_F384D1288827C547A75DEBA2647D64BA172BA39F6BMILEXCH1dsjds_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable We're are using the Freescale release L2.6.31_MX51_SDK_0912_Image and it wi= ll do this on a Freescale Babbage board and our design. It also does the s= ame 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 3Stac= k board we get an illegal address error in Redboot, but it will hang in u-b= oot. 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 b= e some sort of MMU initialization difference between Redboot and u-boot? Thanks in advance. Greg --_000_F384D1288827C547A75DEBA2647D64BA172BA39F6BMILEXCH1dsjds_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

We're are using the Freescale releas= e L2.6.31_MX51_SDK_0912_Image and it will do this on a Freescale Babbage boar= d 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 real= ize this is a reserved physical address but would hope that an error of some ki= nd would occur rather than locking up the CPU.  Could it be some sort of = MMU initialization difference between Redboot and u-boot?

 

Thanks in advance.

 

Greg

 

--_000_F384D1288827C547A75DEBA2647D64BA172BA39F6BMILEXCH1dsjds_-- --===============0667830116== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox --===============0667830116==--