All of lore.kernel.org
 help / color / mirror / Atom feed
From: aregaard <aregaard@protonmail.com>
To: u-boot@lists.denx.de
Subject: sdhci_data_transfer: Trasnfer data timeout
Date: Mon, 24 May 2021 07:43:45 -0700 (MST)	[thread overview]
Message-ID: <1621867425096-0.post@n7.nabble.com> (raw)

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/

             reply	other threads:[~2021-05-24 19:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20210524195119epcas1p253a93f9697a34f072a7c449f04bea5c3@epcas1p2.samsung.com>
2021-05-24 14:43 ` aregaard [this message]
2021-05-25  1:16   ` sdhci_data_transfer: Trasnfer data timeout Jaehoon Chung

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=1621867425096-0.post@n7.nabble.com \
    --to=aregaard@protonmail.com \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.