public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Wadim Egorov <w.egorov@phytec.de>
To: jh80.chung@samsung.com
Cc: linux-mmc@vger.kernel.org, ulf.hansson@linaro.org
Subject: Initialising eMMC: Card stuck in programming state! __mmc_switch
Date: Wed, 31 Aug 2016 11:56:40 +0200	[thread overview]
Message-ID: <57C6A9D8.6020705@phytec.de> (raw)

Hello,

I have a RK3288 based board with a Micron eMMC chip (MTFC16GAKAECN-4M
IT). This eMMC is EDEC/MMC standard version 5.0-compliant.

While doing eMMC boot tests with a 4.4.16 and 4.8.0-rc4 kernel I run
into the following problem after more than 100 cold resets:

[    3.535448] dwmmc_rockchip ff0c0000.dwmmc: 1 slots initialized
[    3.543823] dwmmc_rockchip ff0f0000.dwmmc: IDMAC supports 32-bit address mode.
[    3.551276] dwmmc_rockchip ff0f0000.dwmmc: Using internal DMA controller.
[    3.558206] dwmmc_rockchip ff0f0000.dwmmc: Version ID is 270a
[    3.564275] dwmmc_rockchip ff0f0000.dwmmc: DW MMC controller at irq 31,32 bit host data width,256 deep fifo
[    3.604426] mmc_host mmc0: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0)
[    3.634510] dwmmc_rockchip ff0f0000.dwmmc: 1 slots initialized
[    3.645305] leds-pca953x 4-0062: setting platform data
[    3.656675] ledtrig-cpu: registered to indicate activity on CPUs
[    3.663200] usbcore: registered new interface driver usbhid
[    3.668783] usbhid: USB HID core driver
[    3.672674] usbcore: registered new interface driver r8188eu
[    3.678393] usbcore: registered new interface driver rtl8723au
[    3.699210] mmc_host mmc0: Bus speed (slot 0) = 50000000Hz (slot req 52000000Hz, actual 50000000HZ div = 0)
[    3.900398] random: crng init done
[    3.954089] NET: Registered protocol family 10
[    3.974107] mmc0: Card stuck in programming state! __mmc_switch
[    3.980027] mmc0: error -110 whilst initialising MMC card


The bootloader I am using has no problems with the eMMC as you can see
below:

barebox@phycore-rk3288:/ devinfo mshc0
Host information:
  current clock: 52000000
  current buswidth: 8
  capabilities: 4bit 8bit sd-hs mmc-hs mmc-52MHz
Card information:
  Attached is a MMC card
  Version: 4.0
  Capacity: 14080 MiB
  High capacity card
   CID: 13014E52-314A3536-4C11616D-559BA2BD
   CSD: D04F0132-0F5913FF-FFFFFFEF-8A4000BF
  Max. transfer speed: 52000000 Hz
  capabilities: 4bit mmc-hs mmc-52MHz
  Manufacturer ID: 13
  OEM/Application ID: 014E
  Product name: 'R1J56'
  Product revision: 4.12
  Serial no: 1634555291
  Manufacturing date: 10.1999
Parameters:
  boot: disabled ("disabled", "boot0", "boot1", "user")
  nt_signature: 8a35eb82
  probe: 0

Any hints on what the problem could be?

Regards,
Wadim


             reply	other threads:[~2016-08-31  9:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20160831095654epcas1p46eff3c8b36117c8baef87050aee315a9@epcas1p4.samsung.com>
2016-08-31  9:56 ` Wadim Egorov [this message]
2016-08-31 10:29   ` Initialising eMMC: Card stuck in programming state! __mmc_switch Jaehoon Chung
2016-08-31 14:25     ` Wadim Egorov
2016-09-01  1:34   ` Shawn Lin

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=57C6A9D8.6020705@phytec.de \
    --to=w.egorov@phytec.de \
    --cc=jh80.chung@samsung.com \
    --cc=linux-mmc@vger.kernel.org \
    --cc=ulf.hansson@linaro.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