On 07.10.22 16:13, michael.graichen@xxxxxxxxxxx wrote: > > Hey, > > thanks for your advices. Adding "no-sd" really solved it. Good to know. Keep in mind that's just a work-around though. I highly encourage you to debug it... :D Cheers, Ahmad > > Best Regards > Michael > > > ________________________________________ > Von: Ahmad Fatoum <a.fatoum@xxxxxxxxxxxxxx> > Gesendet: Donnerstag, 6. Oktober 2022 15:13 > An: michael.graichen@xxxxxxxxxxx; barebox@xxxxxxxxxxxxxxxxxxx > Betreff: Re: arasan-sdhci eMMC Problem 'command timeout' > > Hello, > > On 06.10.22 15:03, michael.graichen@xxxxxxxxxxx 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@xxxxxxxxxxx: registered as mmc0 >> arasan-sdhci e0100000.mmc@xxxxxxxxxxx: SDHCI_INT_ERROR: 0x00000001 >> arasan-sdhci e0100000.mmc@xxxxxxxxxxx: error while transfering data for command 8 >> arasan-sdhci e0100000.mmc@xxxxxxxxxxx: state = 0x01ff0001 , interrupt = 0x00018000 >> arasan-sdhci e0100000.mmc@xxxxxxxxxxx: SDHCI_INT_ERROR: 0x00000001 >> arasan-sdhci e0100000.mmc@xxxxxxxxxxx: error while transfering data for command 55 >> arasan-sdhci e0100000.mmc@xxxxxxxxxxx: 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@xxxxxxxxxxx: 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 | > > -- 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 |
