Data abort while mtest
Hello ,
We have successfuuly configured U-boot for our custom board based on PXA255.
The Board is having 32 MB ram. I am able to sucessfully run the coimmands, md, mw etc..
But if I give mtest( CFG_ALT_MEMTEST is defined) I am getting dataabort as below..
$ mtest 0xa1000000 0xa1ffffff 1 Testing a1000000 ... a1ffffff: data abort 1 pc : [<a07e52ac>] lr : [<a07f00f8>] sp : a07bddb4 ip : a07bdc48 fp : a07bddf8 r10: a1ffffff r9 : 00000000 r8 : a07bdfdc r7 : 00000000 r6 : a1000000 r5 : fffffffe r4 : 00000001 r3 : a07f2d1c r2 : a07f2d63 r1 : a07bdc7c r0 : 0000000d Flags: nzCv IRQs off FIQs off Mode <NULL>
What could be wrong ?
Also if I undefine CFG_ALT_MEMTEST, & do mtest I am not getting any exception & am able to test..
Why is that I am not able to test if CFG_ALT_MEMTEST is enabled..? TIA
Regards
Praveen
praveen at spacomp.com schreibt:
Quoted 5 lines
We have successfuuly configured U-boot for our custom board based on PXA255.
The Board is having 32 MB ram. I am able to sucessfully run the coimmands, md, mw etc..
But if I givemtest( CFG_ALT_MEMTEST is defined)I am getting dataabort
Hi,
on ARM (including PXA), you MUST set CFG_MEMTEST_SCRATCH to a valid RAM address (outside the area to be tested, e.g. the last 32-bit word of your RAM), otherwise the memtest will try to write to address 0 (which is flash).
To quote the README:
"- CFG_MEMTEST_SCRATCH:
Scratch address used by the alternate memory test You only need to set this if address zero isn't writeable"
Cheers
Anders
Quoted 2 lines · In message <000601c4e352$34a2bb80$0400a8c0@praveenvs> you wrote:
The Board is having 32 MB ram. I am able to sucessfully run the
...
Quoted 1 line
$ mtest 0xa1000000 0xa1ffffff 1
...
Quoted 1 line
What could be wrong ?
Maybe it would be a god idea to exclude from the memroy test the RAM areas used by U-Boot itself...
Best regards,
Wolfgang Denk
Signature · 4 lines
Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de When in doubt, mumble; when in trouble, delegate; when in charge, ponder. -- James H. Boren
Thanks for your suggestions,
We tried with the CFG_MEMTEST_SCRATCH giving it A1FFFFFC. But again the same problem..., Data Abort....
My Ram is 32 MB...& so the RAM is from A0000000 to A2000000 Is there anything wrong in the RAM Configuration.?. But I am able to properly write to different location using mw & display it by using md
My U-boot is from A07E0000 -> A07F59D8..
What might be the problem ?
Regards
Praveen
-----Original Message-----
From: [email protected] [mailto:u-boot-users-admin at lists.sourceforge.net] On Behalf Of Anders Larsen
Sent: Thursday, December 16, 2004 3:21 PM
To: praveen at spacomp.com
Cc: u-boot-users at lists.sourceforge.net
Subject: Re: [U-Boot-Users] Data abort while mtest
praveen at spacomp.com schreibt:
Quoted 4 lines
We have successfuuly configured U-boot for our custom board based on PXA255. The Board is having 32 MB ram. I am able to sucessfully run the coimmands, md, mw etc..
But if I givemtest( CFG_ALT_MEMTEST is defined)I am getting dataabort
Hi,
on ARM (including PXA), you MUST set CFG_MEMTEST_SCRATCH to a valid RAM address (outside the area to be tested, e.g. the last 32-bit word of your RAM), otherwise the memtest will try to write to address 0 (which is flash).
To quote the README:
"- CFG_MEMTEST_SCRATCH:
Scratch address used by the alternate memory test You only need to set this if address zero isn't writeable"
Cheers
Anders
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
U-Boot-Users mailing list
U-Boot-Users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/u-boot-users
Quoted 8 lines · In message <001301c4e35f$f7a48890$0400a8c0@praveenvs> you wrote:
My Ram is 32 MB...& so the RAM is from A0000000 to A2000000 Is there anything wrong in the RAM Configuration.?. But I am able to properly write to different location using mw & display it by using md
My U-boot is from A07E0000 -> A07F59D8..What might be the problem ?
Isn't this obvious? You are overwriting the U-Boot code when you run a memory test that includes this area.
Best regards,
Wolfgang Denk
Signature · 4 lines
Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de An age is called Dark not because the light fails to shine, but because people refuse to see it. -- James Michener, "Space"
But I am not testing to the U-boot area at all(A07E0000 -> A07F59D8) . I am testing the default which is from 0xa0004000 to 0xa0008000 ..Which is giving data abort...
I gave like this...
$ mtest 0xa0004000 0xa0008000 1
TIA
Regards
Praveen
-----Original Message-----
From: [email protected] [mailto:wd at denx.de]
Sent: Thursday, December 16, 2004 7:34 PM
To: praveen at spacomp.com
Cc: u-boot-users at lists.sourceforge.net
Subject: Re: [U-Boot-Users] Data abort while mtest
Quoted 8 lines · In message <001301c4e35f$f7a48890$0400a8c0@praveenvs> you wrote:
My Ram is 32 MB...& so the RAM is from A0000000 to A2000000 Is there anything wrong in the RAM Configuration.?. But I am able to properly write to different location using mw & display it by using md
My U-boot is from A07E0000 -> A07F59D8..What might be the problem ?
Isn't this obvious? You are overwriting the U-Boot code when you run a memory test that includes this area.
Best regards,
Wolfgang Denk
Signature · 4 lines
Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de An age is called Dark not because the light fails to shine, but because people refuse to see it. -- James Michener, "Space"