From: Fabio.Estevam@freescale.com (Fabio.Estevam at freescale.com)
To: linux-arm-kernel@lists.infradead.org
Subject: i.MX25 esdhc2 incomplete cmd0 transmission
Date: Tue, 5 Aug 2014 16:09:01 +0000 [thread overview]
Message-ID: <1407254932760.78584@freescale.com> (raw)
In-Reply-To: <20140729124808.GF13842@pengutronix.de>
[Sorry for top-posting here]
Are you sure 0x00000000 are the correct values for the IOMUX?
Or do you mean 0x80000000, which would let the same IOMUX as configured by the bootloader?
Are you able to correctly access port esdhc2 from the bootloader?
________________________________________
From: Markus Pargmann <mpa@pengutronix.de>
Sent: Tuesday, July 29, 2014 9:48 AM
To: Guo Shawn-R65073
Cc: Estevam Fabio-R49496; linux-arm-kernel at lists.infradead.org; kernel at pengutronix.de
Subject: i.MX25 esdhc2 incomplete cmd0 transmission
Hi,
This mail did not reach the mailinglist, so here is the same mail
without the images attached.
On Mon, Jul 28, 2014 at 10:06:33AM +0200, Markus Pargmann wrote:
> Hi,
>
> I am currently having a Board with an i.MX25 which has an SD-Card slot
> wired to the CSI pins (ESDHC2). I can see the correct clock and the beginning of
> the cmd0 on the CMD wire (01 00000). But the arguments and CRC that
> should follow the comand are missing. The card doesn't respond to this.
> The same behavior is observable on the karo tx25 module with an
> oscilloscope on ESDHC2.
>
> The tx25 works correctly with the same software and the ESDHC1. I can
> see the complete cmd0 command even without any SD card plugged in, as
> expected. I attached some oscilloscope pictures of these two cases to
> this mail.
>
> This is the pincontrol setup I am using for esdhc2 on karo tx25:
>
> #define MX25_PAD_CSI_HSYNC__SDHC2_DAT2 0x148 0x340 0x4ec 0x02 0x001
> #define MX25_PAD_CSI_MCLK__SDHC2_DAT0 0x140 0x338 0x4e4 0x02 0x001
> #define MX25_PAD_CSI_PIXCLK__SDHC2_DAT3 0x14c 0x344 0x4f0 0x02 0x001
> #define MX25_PAD_CSI_VSYNC__SDHC2_DAT1 0x144 0x33c 0x4e8 0x02 0x001
> #define MX25_PAD_CSI_D6__SDHC2_CMD 0x130 0x328 0x4e0 0x02 0x001
> #define MX25_PAD_CSI_D7__SDHC2_DAT_CLK 0x134 0x32C 0x4dc 0x02 0x001
> esdhc {
> pinctrl_esdhc2: esdhc2 {
> fsl,pins = <
> MX25_PAD_CSI_HSYNC__SDHC2_DAT2 0x00000000
> MX25_PAD_CSI_MCLK__SDHC2_DAT0 0x00000000
> MX25_PAD_CSI_PIXCLK__SDHC2_DAT3 0x00000000
> MX25_PAD_CSI_VSYNC__SDHC2_DAT1 0x00000000
> MX25_PAD_CSI_D6__SDHC2_CMD 0x00000000
> MX25_PAD_CSI_D7__SDHC2_DAT_CLK 0x00000000
> >;
> };
> };
>
> Any ideas what may be wrong/missing?
Here are the images uploaded to a ftp server:
karo tx25 esdhc1 initial communication without SD card inserted:
ftp://ftp.pengutronix.de/pub/20140729_imx25-esdhc2-scope/karo_2.png
ftp://ftp.pengutronix.de/pub/20140729_imx25-esdhc2-scope/karo.png
and the same with karo tx25 esdhc2 and the above pincontrol setup:
ftp://ftp.pengutronix.de/pub/20140729_imx25-esdhc2-scope/karo_esdhc2.png
ftp://ftp.pengutronix.de/pub/20140729_imx25-esdhc2-scope/karo_esdhc2_2.png
Thanks,
Markus
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next parent reply other threads:[~2014-08-05 16:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140728080633.GA13842@pengutronix.de>
[not found] ` <20140729124808.GF13842@pengutronix.de>
2014-08-05 16:09 ` Fabio.Estevam at freescale.com [this message]
2014-08-06 10:41 ` i.MX25 esdhc2 incomplete cmd0 transmission Markus Pargmann
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=1407254932760.78584@freescale.com \
--to=fabio.estevam@freescale.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.