cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
sfun
Visitor
Visitor
737 Views
Registered: ‎07-29-2019

Zynq Ultrascale+ U-Boot not detecting eMMC

Hi there.

We are using a Zynq UltraScale+ MPSoC ZCU102 and would like to access data during the boot process from U-Boot. This data is located on the eMMC (not SD-Card). However, U-Boot does not seem to detect the eMMC, only the SD-Card. Following is the output of running mmc list:

$> mmc list
mmc@ff170000: 0 (SD)

Interestingly, after booting, we can access the SD-Card as well as eMMC.

Our device tree looks as follows:

mmc@ff160000 {
			u-boot,dm-pre-reloc;
			compatible = "xlnx,zynqmp-8.9a\0arasan,sdhci-8.9a";
			status = "okay";
			interrupt-parent = < 0x04 >;
			interrupts = < 0x00 0x30 0x04 >;
			reg = < 0x00 0xff160000 0x00 0x1000 >;
			clock-names = "clk_xin\0clk_ahb";
			xlnx,device_id = < 0x00 >;
			#stream-id-cells = < 0x01 >;
			iommus = < 0x0e 0x870 >;
			power-domains = < 0x0c 0x27 >;
			nvmem-cells = < 0x16 >;
			nvmem-cell-names = "soc_revision";
			clocks = < 0x03 0x36 0x03 0x1f >;
			clock-frequency = < 0x662decc >;
			xlnx,mio_bank = < 0x00 >;
			non-removable;
			no-1-8-v;
			disable-wp;
			bus-width = < 0x08 >;
		};

mmc@ff170000 {
			u-boot,dm-pre-reloc;
			compatible = "xlnx,zynqmp-8.9a\0arasan,sdhci-8.9a";
			status = "okay";
			interrupt-parent = < 0x04 >;
			interrupts = < 0x00 0x31 0x04 >;
			reg = < 0x00 0xff170000 0x00 0x1000 >;
			clock-names = "clk_xin\0clk_ahb";
			xlnx,device_id = < 0x01 >;
			#stream-id-cells = < 0x01 >;
			iommus = < 0x0e 0x871 >;
			power-domains = < 0x0c 0x28 >;
			nvmem-cells = < 0x16 >;
			nvmem-cell-names = "soc_revision";
			clocks = < 0x03 0x37 0x03 0x1f >;
			clock-frequency = < 0xb2d05e0 >;
			xlnx,mio_bank = < 0x01 >;
			pinctrl-names = "default";
			pinctrl-0 = < 0x18 >;
			no-1-8-v;
			disable-wp;
		};

And our configs for u-boot:

CONFIG_IDENT_STRING=" Avantgarde ZynqMP Main Control Board"
CONFIG_ARM=y
CONFIG_ARCH_ZYNQMP=y
CONFIG_SYS_TEXT_BASE=0x8000000
CONFIG_SYS_MALLOC_F_LEN=0x8000
CONFIG_SPL=y
CONFIG_DEBUG_UART_BASE=0xff000000
CONFIG_DEBUG_UART_CLOCK=100000000
CONFIG_ZYNQMP_USB=y
CONFIG_DEBUG_UART=y
CONFIG_AHCI=y
CONFIG_DISTRO_DEFAULTS=y
CONFIG_FIT=y
CONFIG_FIT_VERBOSE=y
CONFIG_SPL_LOAD_FIT=y
# CONFIG_DISPLAY_CPUINFO is not set
CONFIG_SPL_OS_BOOT=y
CONFIG_SPL_RAM_SUPPORT=y
CONFIG_SPL_RAM_DEVICE=y
CONFIG_SPL_ATF=y
CONFIG_SYS_PROMPT="Avantgarde MCB> "
CONFIG_CMD_MEMTEST=y
CONFIG_CMD_CLK=y
CONFIG_CMD_DFU=y
# CONFIG_CMD_FLASH is not set
CONFIG_CMD_FPGA_LOADBP=y
CONFIG_CMD_FPGA_LOADP=y
CONFIG_CMD_FPGA_LOAD_SECURE=y
CONFIG_CMD_GPIO=y
CONFIG_CMD_GPT=y
CONFIG_CMD_I2C=y
CONFIG_CMD_MMC=y
CONFIG_CMD_SF=y
CONFIG_CMD_USB=y
CONFIG_CMD_TFTPPUT=y
CONFIG_CMD_TIME=y
CONFIG_CMD_TIMER=y
CONFIG_CMD_EXT4_WRITE=y
CONFIG_SPL_OF_CONTROL=y
CONFIG_DEFAULT_DEVICE_TREE="zynqmp-zcu104-revC"
CONFIG_ENV_IS_IN_FAT=y
CONFIG_NET_RANDOM_ETHADDR=y
CONFIG_SPL_DM=y
CONFIG_SPL_DM_SEQ_ALIAS=y
CONFIG_SCSI_AHCI=y
CONFIG_SATA_CEVA=y
CONFIG_CLK_ZYNQMP=y
CONFIG_DFU_RAM=y
CONFIG_FPGA_XILINX=y
CONFIG_FPGA_ZYNQMPPL=y
CONFIG_DM_GPIO=y
CONFIG_DM_I2C=y
CONFIG_SYS_I2C_CADENCE=y
CONFIG_I2C_MUX=y
CONFIG_I2C_MUX_PCA954x=y
CONFIG_MISC=y
CONFIG_I2C_EEPROM=y
CONFIG_ZYNQ_GEM_I2C_MAC_OFFSET=0x20
CONFIG_SYS_I2C_EEPROM_ADDR=0x0
CONFIG_SYS_I2C_EEPROM_ADDR_OVERFLOW=0x0
CONFIG_MMC_SDHCI=y
CONFIG_MMC_SDHCI_ZYNQ=y
CONFIG_SPI_FLASH=y
CONFIG_SPI_FLASH_BAR=y
CONFIG_SF_DUAL_FLASH=y
CONFIG_SPI_GENERIC=y
CONFIG_SPI_FLASH_ISSI=y
CONFIG_SPI_FLASH_MACRONIX=y
CONFIG_SPI_FLASH_SPANSION=y
CONFIG_SPI_FLASH_STMICRO=y
CONFIG_SPI_FLASH_WINBOND=y
# CONFIG_SPI_FLASH_USE_4K_SECTORS is not set
CONFIG_SYS_CONFIG_NAME="avg_zynqmp_mcb"
CONFIG_PHY_MARVELL=y
CONFIG_PHY_NATSEMI=y
CONFIG_PHY_REALTEK=y
CONFIG_PHY_TI=y
CONFIG_PHY_VITESSE=y
CONFIG_PHY_FIXED=y
CONFIG_PHY_GIGE=y
CONFIG_MII=y
CONFIG_ZYNQ_GEM=y
CONFIG_SCSI=y
CONFIG_DM_SCSI=y
CONFIG_DEBUG_UART_ZYNQ=y
CONFIG_DEBUG_UART_ANNOUNCE=y
CONFIG_ZYNQ_SERIAL=y
CONFIG_SPI=y
CONFIG_ZYNQMP_GQSPI=y
CONFIG_USB=y
CONFIG_USB_XHCI_HCD=y
CONFIG_USB_XHCI_DWC3=y
CONFIG_USB_XHCI_ZYNQMP=y
CONFIG_USB_DWC3=y
CONFIG_USB_DWC3_GADGET=y
CONFIG_USB_DWC3_GENERIC=y
CONFIG_USB_ULPI_VIEWPORT=y
CONFIG_USB_ULPI=y
CONFIG_USB_GADGET=y
CONFIG_USB_GADGET_DOWNLOAD=y
CONFIG_EFI_LOADER_BOUNCE_BUFFER=y
CONFIG_SIMPLE_BUS=y
CONFIG_SYS_EXTRA_OPTIONS="EMMC_BOOT"
CONFIG_DM_MMC=y

As we can perfectly use the eMMC after booting, I suspect that there is some error in the config of u-boot.

Does anybody have any hints or tips?

Thanks, kind regards

Tags (2)
0 Kudos
1 Reply
xylon_toni
Visitor
Visitor
625 Views
Registered: ‎05-22-2018

Hello,

we have exactly the same problem: u-boot not detecting eMMC.

However, after booting linux over ethernet we can detect and access the eMMC.

We suspect it has something to do with non-existence of the Card Detect pin (normally existing in SD device).

Have you been able to solve the problem?

Thanks.

Best regards

 

0 Kudos