From: Lorenz Kolb <lorenz@missinglinkelectronics.com>
To: Peter Korsgaard <jacmet@sunsite.dk>
Cc: joachim@missinglinkelectronics.com,
dbrownell@users.sourceforge.net, Joachim Foerster <JOFT@gmx.de>,
lorenz@missinglinkelectronics.com, linuxppc-dev@ozlabs.org,
john.linn@xilinx.com
Subject: Re: SD card over (xilinx_)SPI, timeout error while CID
Date: Mon, 08 Jun 2009 17:14:45 +0200 [thread overview]
Message-ID: <4A2D2AE5.2040509@missinglinkelectronics.com> (raw)
In-Reply-To: <87bpp1xulr.fsf@macbook.be.48ers.dk>
Peter Korsgaard wrote:
>>>>>> "Joachim" == Joachim Foerster <JOFT@gmx.de> writes:
>>>>>>
>
> Hi,
>
> Joachim> Any hints? Does anybody use SD card support with
> Joachim> mmc_spi+xilinx_spi ?
>
> I don't, but have you compared the spi signals on a scope in the 2
> setups? Is timing significantly different?
>
>
Hi,
we just tried to find differences for the timing with the oszi:
Here are to screenshots taken from the initial first few data bytes that are
communicated. At least at that time there does not seem to be any timing
issue.
2.6.26 using arch ppc and virtex-devices:
http://img145.imageshack.us/img145/9662/2626virtexdevices.jpg
2.6.29.4 using arch powerpc:
http://img145.imageshack.us/img145/9847/2629devtree.jpg
For explanation:
yellow = chan 1 = MOSI = trigger
green = chan 2 = chipselect not
blue = chan 3 = clock
red = chan 4 = MOSI
Looks like we're gonna have to switch to a logic analyzer
(with spi-mode sdcard analyzing support) as we cannot see any differences
in the short timeframe our oszi does measure, though checking the timing
does not look too promising.
We even configured the Xilinx-SPI core to go down to ~780 kHz just to be
safe,
did not help either.
Regards,
Lorenz
next prev parent reply other threads:[~2009-06-08 15:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-05 15:34 SD card over (xilinx_)SPI, timeout error while CID Joachim Foerster
2009-06-05 21:15 ` John Linn
2009-06-06 15:14 ` Peter Korsgaard
2009-06-08 15:14 ` Lorenz Kolb [this message]
2009-06-09 17:26 ` Joachim Foerster
2009-06-11 19:15 ` Ricardo Ribalda Delgado
[not found] ` <aa76a2be0906111215j15933053rf128f1985a982ca0__26561.0047536486$1244748319$gmane$org@mail.gmail.com>
2009-06-11 20:05 ` Lorenz Kolb
2009-06-11 20:49 ` Ricardo Ribalda Delgado
2009-06-11 21:07 ` Wolfgang Denk
2009-06-11 21:16 ` Ricardo Ribalda Delgado
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=4A2D2AE5.2040509@missinglinkelectronics.com \
--to=lorenz@missinglinkelectronics.com \
--cc=JOFT@gmx.de \
--cc=dbrownell@users.sourceforge.net \
--cc=jacmet@sunsite.dk \
--cc=joachim@missinglinkelectronics.com \
--cc=john.linn@xilinx.com \
--cc=linuxppc-dev@ozlabs.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.