isn't U-boot's address given by the relocadrr variable? If it is so, it is already at the end of ram and I'm giving a smaller end address to the ram - I'm getting relocaddr 0x07fcd000 and using this minus 0x01000 as ending position...
Érico V. Porto
On Sat, Jan 21, 2012 at 2:21 PM, amruth vamadev amruth.vamadev@gmail.comwrote:
Hi Erico Possibly you are overwriting your u-boot code hence causing the hang.You need to move your uboot code to end of DDR and you should be able to test your RAM.You need to change the entry point and reset vector and you can read using readelf using u-boot. Thanks Amruth p.v
On Sat, Jan 21, 2012 at 2:01 AM, Érico Porto ericoporto2008@gmail.com wrote:
I've partially solved the ctrl+c situatin inserting more check for it
into
the code. But this isn't really what I was hoping...
Any known alternatives? Thanks.
Érico V. Porto
On Fri, Jan 20, 2012 at 4:22 PM, Érico Porto <ericoporto2008@gmail.com wrote:
Okay, got 2011.12 working here.
Same problem, my system stalls when I try using mtest on low position of the memory, but now I have the relocaddr var to tell me what is the superior memory limit.
( I can't paste any output here because the list gives me a BASE
ENCODE64
not allowed error... )
And if the system freezes during mtest, I can't ctrl+c out of it.
Is there any know workaround?
My system is much a like MPC8323ERDB. Other than that, seems I can run linux fine on it after bootload, I just can't use mtest...
Érico V. Porto
On Fri, Jan 20, 2012 at 8:56 AM, Érico Porto <ericoporto2008@gmail.com
wrote:
Now I understood, LTIB is giving me an older u-boot version - 1.1.6 and not 2011.12. Will try to update it...
Érico V. Porto
On Fri, Jan 20, 2012 at 8:38 AM, Anatolij Gustschin <agust@denx.de
wrote:
Hi,
On Fri, 20 Jan 2012 08:07:41 -0200 Érico Porto ericoporto2008@gmail.com wrote:
Hello,
I want to stop autoboot and use mtest to check if my ram is alright,
but
0x07FD2C00 forward freezes, and 0x00000902 also freezes, mtest, when
using
it. My ramsize is 0x08000000.
Does u-boot uses any parts of ram by itself, I mean, is there any
known
spots where I can't test because it would crash my system?
U-Boot relocates itself into RAM. You can check the address using 'bdinfo' command (look at 'relocaddr' in the output). There are also some data structures in RAM (global data, board info, stack, malloc area) and also exception vectors. Where it is located in RAM depends on your architecture and board configuration options. You can try to define DEBUG in the arch board.c file to get more info. Board config file should define CONFIG_SYS_MEMTEST_START and CONFIG_SYS_MEMTEST_END to prevent crashing when mtest is invoked.
HTH, Anatolij
U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot