* sdhci_data_transfer: Trasnfer data timeout @ 2021-05-24 14:43 ` aregaard 2021-05-25 1:16 ` Jaehoon Chung 0 siblings, 1 reply; 2+ messages in thread From: aregaard @ 2021-05-24 14:43 UTC (permalink / raw) To: u-boot Hi, I have made a custom board based on ARM A53. I use a NOR-flash, eMMC and DDR3. I can start the Uboot from NOR and communicate with the eMMC. But for some reason it is timing out the first time I connect to the eMMC. *(CLK =25MHz)* => run mmc_format eMMC: INT_STATUS = 00018000 eMMC: INT_STATUS = 00018001 sdhci_transfer_data: Transfer data timeout sdhci_transfer_data: Transfer data timeout After this part it can communicate: *(CLK = 50MHz)* success! Writing GPT: success! Saving Environment to SPI Flash... SF: Detected n25q128a13 with page size 256 Bytes, erase size 4 KiB, total 16 MiB Erasing SPI flash...Writing to SPI flash...done Valid environment: 1 OK This Timeout might cause problems with the DDR3 (I am having problems with the Kernel not booting corretly). I think there is an issue with the communication with the eMMC and DDR, due to the timeout. What can generate the timing-out-issue? To make it clear; I can communicate with the eMMC. The first time it is really slow and is timing out with 25 MHz FLASH-clk. The second time it goes directly into sync: => run mmc_format success! Writing GPT: success! Saving Environment to SPI Flash... Erasing SPI flash...Writing to SPI flash...done Valid environment: 2 OK I sounds like a HW-issue, but what can cause this in the code? If I reset the system it is timing out again the first time. Kind Regards -- Sent from: http://u-boot.10912.n7.nabble.com/ ^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: sdhci_data_transfer: Trasnfer data timeout 2021-05-24 14:43 ` sdhci_data_transfer: Trasnfer data timeout aregaard @ 2021-05-25 1:16 ` Jaehoon Chung 0 siblings, 0 replies; 2+ messages in thread From: Jaehoon Chung @ 2021-05-25 1:16 UTC (permalink / raw) To: aregaard, u-boot Hi On 5/24/21 11:43 PM, aregaard wrote: > Hi, > I have made a custom board based on ARM A53. > I use a NOR-flash, eMMC and DDR3. > > I can start the Uboot from NOR and communicate with the eMMC. > But for some reason it is timing out the first time I connect to the eMMC. > You can enable MMC_TRACE, then you can see more information. Best Regards, Jaehoon Chung > > *(CLK =25MHz)* > => run mmc_format > eMMC: INT_STATUS = 00018000 > eMMC: INT_STATUS = 00018001 > sdhci_transfer_data: Transfer data timeout > sdhci_transfer_data: Transfer data timeout > > After this part it can communicate: > > *(CLK = 50MHz)* > success! > Writing GPT: success! > Saving Environment to SPI Flash... SF: Detected n25q128a13 with page size > 256 Bytes, erase size 4 KiB, total 16 MiB > Erasing SPI flash...Writing to SPI flash...done > Valid environment: 1 > OK > > This Timeout might cause problems with the DDR3 (I am having problems with > the Kernel not booting corretly). I think there is an issue with the > communication with the eMMC and DDR, due to the timeout. > > What can generate the timing-out-issue? > > To make it clear; I can communicate with the eMMC. The first time it is > really slow and is timing out with 25 MHz FLASH-clk. The second time it goes > directly into sync: > > => run mmc_format > success! > Writing GPT: success! > Saving Environment to SPI Flash... Erasing SPI flash...Writing to SPI > flash...done > Valid environment: 2 > OK > > I sounds like a HW-issue, but what can cause this in the code? > > If I reset the system it is timing out again the first time. > > Kind Regards > > > > -- > Sent from: http://u-boot.10912.n7.nabble.com/ > ^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2021-05-25 1:16 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <CGME20210524195119epcas1p253a93f9697a34f072a7c449f04bea5c3@epcas1p2.samsung.com>
2021-05-24 14:43 ` sdhci_data_transfer: Trasnfer data timeout aregaard
2021-05-25 1:16 ` Jaehoon Chung
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox