public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Jaehoon Chung <jh80.chung@samsung.com>
To: amit mahadik <amitmaddy@gmail.com>, linux-mmc@vger.kernel.org
Subject: Re: How to print CMD18 read data
Date: Wed, 01 Feb 2017 17:08:37 +0900	[thread overview]
Message-ID: <e0fcedc7-58f4-7ee3-e182-db684c8748d6@samsung.com> (raw)
In-Reply-To: <CAMGZvfKXGwmrOSD-z_4F5aM5S7TPENmPkLKQ3ArQxJ+rEruhtg@mail.gmail.com>

Hi,

On 02/01/2017 04:23 PM, amit mahadik wrote:
> Hello,
>          I want to interface MMC card via SPI bus. However, I am
> getting CRC errors for CMD18. I tried reading partition table using
> CMD17 but still get errors.
> The same SDMMC card gets detected using SD interface. I want to
> compare the data of CMD18/CMD17 of SD and SPI modes. Please let me
> know how can I print the read data of the said commands in the block
> layer?

In my experience, CRC error was timing issue..(clock, driver-strength, etc..)
You can check those things.

Best Regards,
Jaehoon Chung

> 
> I tried using the following code but it didn't help
> 
> sg_copy_to_buffer(brq->data.sg, brq->data.sg_len, buf, 4096); and printed buf.
> 
> Regards,
> Amit.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> 


  reply	other threads:[~2017-02-01  8:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20170201072351epcas2p4b40fc91e204153ce57d510622ab021cc@epcas2p4.samsung.com>
2017-02-01  7:23 ` How to print CMD18 read data amit mahadik
2017-02-01  8:08   ` Jaehoon Chung [this message]
2017-02-01  8:48     ` amit mahadik
2017-02-01 11:43       ` Jaehoon Chung
2017-02-01 12:16         ` amit mahadik
2017-02-01 18:00           ` David Haworth

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=e0fcedc7-58f4-7ee3-e182-db684c8748d6@samsung.com \
    --to=jh80.chung@samsung.com \
    --cc=amitmaddy@gmail.com \
    --cc=linux-mmc@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox