From: Alessandro Rubini <rubini-list@gnudd.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Uboot mtest hang on mx31
Date: Mon, 27 Apr 2009 09:12:27 +0200 [thread overview]
Message-ID: <20090427071227.GA7755@mail.gnudd.com> (raw)
In-Reply-To: <528f13590904262155t1bc8c19aqad202172eb8c8bdc@mail.gmail.com>
> When i do a memtest without any args, it crashes after printing the
> first line.
> => mtest
> Pattern 00000000 Writing...
> After reboot, when i do and md for the base address 0x0, i get the
> following, which proabbly is the uboot image itself in RAM.
Not exactly. At address 0 you have the internal boot ROM. That code
is not u-boot, as you can see from comparing with the u-boot.bin
you compiled.
Actually, your ram start at 2GB physical (CSD0_BASE, 0x80000000)
but the MX31 config file in current git says:
#define CONFIG_SYS_MEMTEST_START 0 /* memtest works on */
#define CONFIG_SYS_MEMTEST_END 0x10000
So, most likely memtest without arguments has never been used on the
board.
[disclaimer: I have mx21 but not mx31, I just assume it's similar]
/alessandro
next prev parent reply other threads:[~2009-04-27 7:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-27 4:55 [U-Boot] Uboot mtest hang on mx31 alfred steele
2009-04-27 7:12 ` Alessandro Rubini [this message]
2009-04-27 15:21 ` alfred steele
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090427071227.GA7755@mail.gnudd.com \
--to=rubini-list@gnudd.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox