From: Daniel Mack <daniel@caiaq.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-boot memory dump
Date: Sat, 25 Apr 2009 18:45:32 +0200 [thread overview]
Message-ID: <20090425164532.GA24836@buzzloop.caiaq.de> (raw)
In-Reply-To: <528f13590904250941y5f156b09ga76e36b48239b509@mail.gmail.com>
On Sat, Apr 25, 2009 at 11:41:43AM -0500, alfred steele wrote:
> I am using uboot on the MX31 PDk board. I am trying to dump the
> contents of a status register found at location 50004004. This status
> register shows the status of the SDHC( SD card host controller) like
> interrupt , card insertion, card removal etc. According to the MX31
> manual, the status register i.e the contents at the corresponding
> memory location should change on events like card insertion and
> removal. But the contents aren't changing as expected.
> I have verified this with Linux and it works.
The difference is most probably that under Linux, your IOMUX is set up
correctly. IOW, the CPU does not see any external peripherals unless
you enable the pins for the specific function you're trying to use.
Daniel
prev parent reply other threads:[~2009-04-25 16:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-25 16:41 [U-Boot] U-boot memory dump alfred steele
2009-04-25 16:45 ` Daniel Mack [this message]
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=20090425164532.GA24836@buzzloop.caiaq.de \
--to=daniel@caiaq.de \
--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