[U-Boot-Users] mtest boundaries
Hello,
how I can detect where u-boot puts itself into RAM in such a way the "mtest" command doesn't destroy it during memory tests?
In this manner it could be possible to auto-exclude u-boot code during the test...
Thanks,
Rodolfo
In message 20061107110946.GC2682@gundam.enneenne.com you wrote:
how I can detect where u-boot puts itself into RAM in such a way the "mtest" command doesn't destroy it during memory tests?
A good start is reading the README. Then you should consult the memory map you set up when porting U-Boot to your board.
It would also definitely help if you provided a *bit* more detail, like which architecture you are talking about, etc.
Best regards,
Wolfgang Denk
On Tue, Nov 07, 2006 at 06:44:42PM +0100, Wolfgang Denk wrote:
It would also definitely help if you provided a *bit* more detail, like which architecture you are talking about, etc.
I'm using MIPS/au1x00 and ARM/PXA2xx, but I think this should be a general issue since the "mtest" command is not architectural dependent.
Thanks for the suggestions,
Rodolfo
I'm not sure if this'll help you but I generally found that you couldn't get full coverage with the 'mtest' command.
To get around this I implemented some code which optionally intervenes just before U-Boot relocates it's self, to run a full memory test, taking into account the limited available resources when running in this mode.
Rodolfo Giometti giometti@linux.it 11/08/06 6:49 am >>>
On Tue, Nov 07, 2006 at 06:44:42PM +0100, Wolfgang Denk wrote:
It would also definitely help if you provided a *bit* more
detail,
like which architecture you are talking about, etc.
I'm using MIPS/au1x00 and ARM/PXA2xx, but I think this should be a general issue since the "mtest" command is not architectural dependent.
Thanks for the suggestions,
Rodolfo
--
GNU/Linux Solutions e- mail: giometti@enneenne.com Linux Device Driver giometti@gnudd.com Embedded Systems giometti@linux.it UNIX programming phone: +39 349 2432127
------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre- integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as- us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ U- Boot- Users mailing list U- Boot- Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u- boot- users
In message 45519BED.7A9D.00CE.0@alliedtelesis.co.nz you wrote:
I'm not sure if this'll help you but I generally found that you couldn't get full coverage with the 'mtest' command.
To get around this I implemented some code which optionally intervenes just before U-Boot relocates it's self, to run a full memory test, taking into account the limited available resources when running in this mode.
You probably should look into the post/memory.c code instead.
Best regards,
Wolfgang Denk
In message 20061107174935.GA28991@gundam.enneenne.com you wrote:
I'm using MIPS/au1x00 and ARM/PXA2xx, but I think this should be a general issue since the "mtest" command is not architectural dependent.
But the memory mapo is NOT independent of the architecture. For example, on PowerPC U-Boot will relocate itself always to the upper end of available RAM, auto-adjusting to different RAM sizes. For ARM or MIPS this is not the case, there it will reside at a pre- determined fixed address.
Since you are on ARM and MIPS, you just have to look up the used address ranges in your memory map.
Best regards,
Wolfgang Denk
participants (3)
-
matthew millman -
Rodolfo Giometti -
Wolfgang Denk