When booting a Versal ACAP target in QSPI bootmode, an SD timeout issue similar to the following is observed after issuing a subsytem restart:
Hit any key to stop autoboot: 5 4 3 2 1 0
sdhci_send_command: MMC: 0 busy timeout increasing to: 200 ms.
sdhci_send_command: MMC: 0 busy timeout increasing to: 400 ms.
sdhci_send_command: MMC: 0 busy timeout increasing to: 800 ms.
sdhci_send_command: MMC: 0 busy timeout increasing to: 1600 ms.
sdhci_send_command: MMC: 0 busy timeout increasing to: 3200 ms.
sdhci_send_command: MMC: 0 busy timeout.
sdhci_send_command: MMC: 0 busy timeout.
JTAG: Trying to boot script at 0x20000000
1. Executing script at 20000000
boot target is mmc0
Wrong Image Format for bootm command
ERROR: can't get kernel image!
JTAG: SCRIPT FAILED: continuing...
sdhci_set_clock: Timeout to wait cmd & data inhibit
sdhci_set_clock: Timeout to wait cmd & data inhibit
sdhci_set_clock: Timeout to wait cmd & data inhibit
sdhci_send_command: MMC: 0 busy timeout.
MMC Device 1 not found
no mmc device at slot 1
This is a known issues article for Versal ACAP devices.
No solution currently exists for this issue.
This issue is planned to be fixed in the 2021.1 release.
| AR# 75892 | |
|---|---|
| 日期 | 12/14/2020 |
| 状态 | Active |
| Type | 已知问题 |
| 器件 | |
| Tools | |
| Boards & Kits | |