public inbox for ecos-bugs@sourceware.org help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org To: ecos-bugs@ecos.sourceware.org Subject: [Bug 1001764] Enhancement of MMC/SD over SPI driver Date: Sun, 30 Jun 2013 13:59:00 -0000 [thread overview] Message-ID: <bug-1001764-13-1ItGlb30Tr@http.bugs.ecos.sourceware.org/> (raw) In-Reply-To: <bug-1001764-13@http.bugs.ecos.sourceware.org/> Please do not reply to this email, use the link below. http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001764 --- Comment #22 from Mike Jones <mjones@linear.com> --- I have had more bench time on the MMC, so I have more information about its operation under heavy use. First, my setup is atypical. I have a cable on J5 of the Kinetis tower board that connects to another board 30cm away. This board has its own power supply off line. Therefore, because there is a ground connection in J5, there is a ground loop. Furthermore, I am using the I2C lines in the J5 connector. I have seen four problems: 1) Can't mount Samsung microSD 2) Can't mount any microSD 3) IO failure after three hours of intense operation (logging MB to card) 4) Can't get DMA to work reliably I have some new information. I was debugging the TWR-DACADC-LTC and noticed problem 2. When I removed the ground clips from my scope, problem 2 went away. This leads me to the conclusion that problems 2 and 3 are related to grounding problems. I can't prove grounding is causing 3 until I have a single board version of my solution. Problems 1 and 4 still seem to be problems that only affect me. I work around them by not using DMA and not using the Samsung card. I am certain that problem 1 is not related to grounding. I have tested for that. I am reasonable certain problem 4 is not related to grounding, I am pretty sure I have seen the problem with my cable removed. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2013-06-30 13:59 UTC|newest] Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-02-18 20:24 [Bug 1001764] New: " bugzilla-daemon 2013-03-14 14:24 ` [Bug 1001764] " bugzilla-daemon 2013-03-15 0:47 ` bugzilla-daemon 2013-03-15 7:52 ` bugzilla-daemon 2013-03-15 14:04 ` bugzilla-daemon 2013-03-18 9:52 ` bugzilla-daemon 2013-03-19 13:36 ` bugzilla-daemon 2013-03-20 7:29 ` bugzilla-daemon 2013-03-23 16:00 ` bugzilla-daemon 2013-04-15 22:41 ` bugzilla-daemon 2013-04-16 14:41 ` bugzilla-daemon 2013-04-18 17:33 ` bugzilla-daemon 2013-04-18 18:35 ` bugzilla-daemon 2013-04-18 19:10 ` bugzilla-daemon 2013-04-18 21:16 ` bugzilla-daemon 2013-04-19 16:17 ` bugzilla-daemon 2013-04-22 15:03 ` bugzilla-daemon 2013-05-01 15:10 ` bugzilla-daemon 2013-05-05 16:09 ` bugzilla-daemon 2013-06-19 11:04 ` bugzilla-daemon 2013-06-30 13:59 ` bugzilla-daemon [this message] 2013-07-01 17:36 ` bugzilla-daemon 2013-07-01 20:27 ` bugzilla-daemon 2013-07-02 16:28 ` bugzilla-daemon 2013-02-18 20:24 [Bug 1001764] New: " bugzilla-daemon 2013-03-14 14:25 ` [Bug 1001764] " bugzilla-daemon 2013-03-15 0:47 ` bugzilla-daemon 2013-03-15 7:52 ` bugzilla-daemon 2013-03-15 14:04 ` bugzilla-daemon 2013-03-18 9:52 ` bugzilla-daemon 2013-03-19 13:36 ` bugzilla-daemon 2013-03-20 7:29 ` bugzilla-daemon 2013-03-23 16:00 ` bugzilla-daemon 2013-04-15 22:41 ` bugzilla-daemon 2013-04-16 14:41 ` bugzilla-daemon 2013-04-18 18:35 ` bugzilla-daemon 2013-04-18 19:10 ` bugzilla-daemon 2013-04-22 15:03 ` bugzilla-daemon 2013-05-01 15:10 ` bugzilla-daemon 2013-05-05 16:09 ` bugzilla-daemon 2013-06-19 11:04 ` bugzilla-daemon 2013-06-30 13:59 ` bugzilla-daemon 2013-07-01 17:36 ` bugzilla-daemon 2013-07-01 20:27 ` bugzilla-daemon 2013-07-02 16:28 ` bugzilla-daemon
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=bug-1001764-13-1ItGlb30Tr@http.bugs.ecos.sourceware.org/ \ --to=bugzilla-daemon@bugs.ecos.sourceware.org \ --cc=ecos-bugs@ecos.sourceware.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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).