AnsweredAssumed Answered

U-boot show errors when accessing the SD card!

Question asked by FivePandaH on Jan 21, 2018
Latest reply on Jan 24, 2018 by larsc

Hi,

I'm debuging a new z7045 board, I generated a minimum system with just an uart1 and SD card enabled in vivado ,

then after the bitstream file generated , copied the ZC706 boot image's fsbl.elf, uImage and u-boot.elf to generate a 

new BOOTBIN, and plug into the SD card, the boot information is strange:


U-Boot 2016.07-11381-g45e5971-dirty (Nov 21 2017 - 09:01:16 +0800)

Model: Zynq ZC706 Development Board
Board: Xilinx Zynq
I2C: ready
DRAM: ECC disabled 1 GiB
MMC: sdhci@e0100000: 0
Invalid bus 0 (err=-1)
*** Warning - spi_flash_probe() failed, using default environment

In: serial@e0001000
Out: serial@e0001000
Err: serial@e0001000
Model: Zynq ZC706 Development Board
Board: Xilinx Zynq
Net: ZYNQ GEM: e000b000, phyaddr 7, interface rgmii-id
mdio_wait: Timeout
mdio_wait: Timeout
mdio_wait: Timeout
mdio_wait: Timeout
mdio_wait: Timeout
mdio_wait: Timeout
mdio_wait: Timeout
mdio_wait: Timeout
mdio_wait: Timeout
mdio_wait: Timeout
mdio_wait: Timeout
mdio_wait: Timeout
mdio_wait: Timeout
mdio_wait: Timeout
mdio_wait: Timeout
mdio_wait: Timeout
mdio_wait: Timeout
mdio_wait: Timeout
mdio_wait: Timeout
mdio_wait: Timeout
mdio_wait: Timeout
mdio_wait: Timeout
mdio_wait: Timeout
mdio_wait: Timeout
mdio_wait: Timeout
mdio_wait: Timeout
mdio_wait: Timeout
mdio_wait: Timeout
mdio_wait: Timeout
mdio_wait: Timeout
mdio_wait: Timeout
mdio_wait: Timeout
mdio_wait: Timeout
PHY is not detected
GEM PHY init failed
No ethernet found.
reading uEnv.txt
380 bytes read in 56 ms (5.9 KiB/s)
Importing environment from SD ...
Hit any key to stop autoboot: 0
Zynq> MC: sdhci@e0100000: 0
Unknown command 'MC:' - try 'help'
Zynq>
Unknown command 'MC:' - try 'help'
Zynq> Invalid bus 0 (err=-1)
Unknown command 'Invalid' - try 'help'
Zynq>
Unknown command 'Invalid' - try 'help'
Zynq> *** Warning - q> MC: sdhci@e0100000:qq> Invalid bus 0 (err=-qq> *** Warning - q> MC: sdhci@e0100000:qq> Invalid bus 0 (err=-qq> *** Warning - q> MC: sdhci@e0100000:qq> Invalid bus 0 (err=-qq> *** Warning - q> MC: sdhci@e0100000:qq> Invalid bus 0 (err=-qq> *** Warning - q> MC: sdhci@e0100000:qq> Invalid bus 0 (err=-qq> *** Warning - q> MC: sdhci@e0100000:qq> Invalid bus 0 (err=-qq> *** Warning - q> MC: sdhci@e0100000:qq> Invalid bus 0 (err=-qq> *** Warning - q> MC: sdhci@e0100000:qq> Invalid bus 0 (err=-qq> *** Warning - q> MC: sdhci@e0100000:qq> Invalid bus 0 (err=-qq> *** Warning - q> MC: sdhci@e0100000:qq> Invalid bus 0 (err=-qq> *** Warning - q> MC: sdhci@e0100000:qq> Invalid bus 0 (err=-qq> *** Warning - q> MC: sdhci@e0100000:qq> Invalid bus 0 (err=-qq> *** Warning - q> MC: sdhci@e0100000:qq> Invalid bus 0 (err=-qq> *** Warning - q> MC: sdhci@e0100000:qq> Invalid bus 0 (err=-qq> *** Warning - q> MC: sdhci@e0100000:qq> Invalid bus 0 (err=-qq> *** Warning - q> MC: sdhci@e0100000:qq> Invalid bus 0 (err=-qq> *** Warning - q> MC: sdhci@e0100000:qq> Invalid bus 0 (err=-qq> *** Warning - q> MC: sdhci@e0100000:qq> Invalid bus 0 (err=-qq> *** Warning - q> MC: sdhci@e0100000:qq> Invalid bus 0 (err=-qq> *** Warning - q> MC: sdhci@e0100000:qq> Invalid bus 0 (err=-qq> *** Warning - q> MC: sdhci@e0100000:qq> Invalid bus 0 (err=-qq> *** Warning - q> MC: sdhci@e0100000:qq> Invalid bus 0 (err=-qq> *** Warning - q> MC: sdhci@e0100000:qq> Invalid bus 0 (err=-qq> *** Warning - q> MC: sdhci@e0100000:qq> Invalid bus 0 (err=-qq> *** Warning - q> MC: sdhci@e0100000:qq> Invalid bus 0 (err=-qq> *** Warning - q> MC: sdhci@e0100000:qq> Invalid bus 0 (err=-qq> *** Warning - q> MC: sdhci@e0100000:qq> Invalid bus 0 (err=-qq> *** Warning - q> MC: sdhci@e0100000:qq> Invalid bus 0 (err=-qq> *** Warning - q> MC: sdhci@e0100000:qq> Invalid bus 0 (err=-qq> *** Warning - q> MC: sdhci@e0100000:qq> Invalid bus 0 (err=-qq> *** Warning - q> MC: sdhci@e0100000

 

Does it mean the SD card is damaged? I googled and find nothing helpful.

Outcomes