mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: michael.graichen@hotmail.com,
	"barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: arasan-sdhci eMMC Problem 'command timeout'
Date: Thu, 6 Oct 2022 15:13:23 +0200	[thread overview]
Message-ID: <5ab7d76d-2d89-4aa5-3f9b-1eeffefd9437@pengutronix.de> (raw)
In-Reply-To: <AM9P192MB08709ED9E86625C99913EA2FAB5C9@AM9P192MB0870.EURP192.PROD.OUTLOOK.COM>

Hello,

On 06.10.22 15:03, michael.graichen@hotmail.com wrote:
> Hey, 
> 
> I have connected an eMMC to sdhci0 and a uSD Card to sdhci1 of a Zynq. 
> while the uSD Card seams to work fine i'm getting the error
> 
> arasan-sdhci e0100000.mmc@e0100000.of: registered as mmc0
> arasan-sdhci e0100000.mmc@e0100000.of: SDHCI_INT_ERROR: 0x00000001
> arasan-sdhci e0100000.mmc@e0100000.of: error while transfering data for command 8
> arasan-sdhci e0100000.mmc@e0100000.of: state = 0x01ff0001 , interrupt = 0x00018000
> arasan-sdhci e0100000.mmc@e0100000.of: SDHCI_INT_ERROR: 0x00000001
> arasan-sdhci e0100000.mmc@e0100000.of: error while transfering data for command 55
> arasan-sdhci e0100000.mmc@e0100000.of: state = 0x01ff0001 , interrupt = 0x00018000
> 
> from the eMMC. 

Please try adding no-sd to your eMMC device tree node and try again.
I don't know why it's necessary, because falling back to MMC after
SD fails is normal operation on all other hosts. I don't have the
hardware, but I've seen that the recently added device trees that
use the arasan, set this in barebox for the eMMC node.

> 
> arasan-sdhci e0101000.mmc@e0101000.of: registered as mmc1
> mmc1: detected SD card version 2.0
> mmc1: registered mmc1
> 
> both eMMC and SDCard work fine in Linux. So I think the Problem is some confuguration difference between Linux and barebox. 
> The MMC is from type MTFC8G but Linux detects it as  
> 
> [    2.012122] mmc0: new high speed MMC card at address 0001
> [    2.021129] mmcblk0: mmc0:0001 Q2J55L 7.09 GiB 
> [    2.026355] Btrfs loaded, crc32c=crc32c-generic, zoned=no, fsverity=no
> [    2.027458] mmcblk0boot0: mmc0:0001 Q2J55L 16.0 MiB 
> [    2.031509] mmcblk0boot1: mmc0:0001 Q2J55L 16.0 MiB 
> [    2.039829] mmcblk0rpmb: mmc0:0001 Q2J55L 4.00 MiB, chardev (245:0)
> 
> Unfortunattly I'm not very familliar with SDHCI, so I would apreciate any help.

If it's indeed resolved by no-sd, this sound like a good occasion to dig
deeper into the SDHCI. ;)

Let me know if that works for you.

Cheers,
Ahmad

 
> 
> Best Regards 
> Michael
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 


-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |



  reply	other threads:[~2022-10-06 13:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-06 13:03 michael.graichen
2022-10-06 13:13 ` Ahmad Fatoum [this message]
2022-10-07 14:13   ` AW: " michael.graichen
2022-10-07 14:21     ` Ahmad Fatoum
2022-10-06 13:28 ` Yann Sionneau
2023-01-03 22:06   ` Ahmad Fatoum
2023-01-04  9:27     ` Yann Sionneau

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=5ab7d76d-2d89-4aa5-3f9b-1eeffefd9437@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=michael.graichen@hotmail.com \
    /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