On 13.04.2012 17:56, Fabio Estevam wrote:
On Wed, Apr 11, 2012 at 6:36 PM, Wolfgang Denkwd@denx.de wrote:
Does testing just the first 64 KiB of RAM make any sense? Not to me.
Ok, I will expand the mtest range.
BTW: where are the exception vectors located?
I don't know actually, but would like to learn about it. Looked at the generated u-boot.map and could not find it out.
Stefano,
Can you please help me to find a safer DDR location for performing mtest on mx6? I think we probably have the same issues on other i.MX processors as well. Do you know how can I locate the address range that the exception vectors occupy?
Regarding the exception vectors:
I would think that the code of the U-Boot exception vectors are located at
#define CONFIG_SYS_TEXT_BASE 0x17800000
and
#define CONFIG_LOADADDR 0x10800000
after relocation using
http://git.denx.de/cgi-bin/gitweb.cgi?p=u-boot.git;a=blob;f=arch/arm/cpu/arm...
and
http://git.denx.de/cgi-bin/gitweb.cgi?p=u-boot.git;a=blob;f=arch/arm/cpu/u-b...
So as long as we don't have the MMU enabled, these vectors aren't used at all. I would expect that the BootRom exception vectors at address 0x00000000 are used, instead.
I might be wrong, so people please correct me ;)
Best regards
Dirk