ZCU111 getting stuck - mmc0: Timeout waiting for hardware cmd interrupt

Hi,

I complied ZCU111 Pynq image on Ubuntu16.04.3
Using latest master branch of PYNQ and ZCU111-PYNQ
Using Vivado 2019.1 and Petalinux 2019.1

Image building was successful. Used PREBUILT and PYNQ_SDIST to enhance speed of build

make PREBUILT=~/PynqRootFs/bionic.aarch64.2.5.img BOARDDIR=~/ZCU111-PYNQ PYNQ_SDIST=~/Pynq_Dist/pynq-2.5.4.tar.gz

Image booted successfully.
But following error came within few seconds of successful bootup

It got stuck and I can’t enter another command


xilinx@pynq:~$ [ 244.959856] mmc0: Timeout waiting for hardware cmd interrupt.
[ 244.965595] mmc0: sdhci: ============ SDHCI REGISTER DUMP ===========
[ 244.972026] mmc0: sdhci: Sys addr: 0x00000008 | Version: 0x00001002
[ 244.978448] mmc0: sdhci: Blk size: 0x00007200 | Blk cnt: 0x00000000
[ 244.984872] mmc0: sdhci: Argument: 0xaaaa0000 | Trn mode: 0x00000023
[ 244.991295] mmc0: sdhci: Present: 0x01f70000 | Host ctl: 0x0000001f
[ 244.997718] mmc0: sdhci: Power: 0x0000000f | Blk gap: 0x00000080
[ 245.004141] mmc0: sdhci: Wake-up: 0x00000000 | Clock: 0x00000207
[ 245.010564] mmc0: sdhci: Timeout: 0x00000009 | Int stat: 0x00000001
[ 245.016988] mmc0: sdhci: Int enab: 0x02ff008b | Sig enab: 0x02ff008b
[ 245.023411] mmc0: sdhci: AC12 err: 0x00000000 | Slot int: 0x00000001
[ 245.029834] mmc0: sdhci: Caps: 0x35ecc881 | Caps_1: 0x00002007
[ 245.036257] mmc0: sdhci: Cmd: 0x00000d1a | Max curr: 0x00000000
[ 245.042680] mmc0: sdhci: Resp[0]: 0x00000900 | Resp[1]: 0x003b377f
[ 245.049104] mmc0: sdhci: Resp[2]: 0x325b5900 | Resp[3]: 0x00000900
[ 245.055527] mmc0: sdhci: Host ctl2: 0x00000000
[ 245.059954] mmc0: sdhci: ADMA Err: 0x00000000 | ADMA Ptr: 0x0000000077c9820c
[ 245.067071] mmc0: sdhci: ============================================
[ 255.268889] mmc0: Timeout waiting for hardware cmd interrupt.
[ 255.274630] mmc0: sdhci: ============ SDHCI REGISTER DUMP ===========
[ 255.281061] mmc0: sdhci: Sys addr: 0x00000008 | Version: 0x00001002
[ 255.287483] mmc0: sdhci: Blk size: 0x00007200 | Blk cnt: 0x00000000
[ 255.293907] mmc0: sdhci: Argument: 0xaaaa0000 | Trn mode: 0x00000023
[ 255.300330] mmc0: sdhci: Present: 0x01f70000 | Host ctl: 0x0000001f
[ 255.306753] mmc0: sdhci: Power: 0x0000000f | Blk gap: 0x00000080
[ 255.313177] mmc0: sdhci: Wake-up: 0x00000000 | Clock: 0x00000207
[ 255.319600] mmc0: sdhci: Timeout: 0x00000009 | Int stat: 0x00000001
[ 255.326023] mmc0: sdhci: Int enab: 0x02ff008b | Sig enab: 0x02ff008b
[ 255.332446] mmc0: sdhci: AC12 err: 0x00000000 | Slot int: 0x00000001
[ 255.338870] mmc0: sdhci: Caps: 0x35ecc881 | Caps_1: 0x00002007
[ 255.345293] mmc0: sdhci: Cmd: 0x00000d1a | Max curr: 0x00000000
[ 255.351716] mmc0: sdhci: Resp[0]: 0x00000900 | Resp[1]: 0x003b377f
[ 255.358139] mmc0: sdhci: Resp[2]: 0x325b5900 | Resp[3]: 0x00000900
[ 255.364562] mmc0: sdhci: Host ctl2: 0x00000000
[ 255.368990] mmc0: sdhci: ADMA Err: 0x00000000 | ADMA Ptr: 0x0000000077c9820c
[ 255.376107] mmc0: sdhci: ============================================

Are you using JTAG by any chance? We’ve seen this issue arise when using the ILA or SDK debuggers. You can fix it by changing the kernel boot arguments as discussed in this thread.

Thanks,
I complied whole image again using:
Ubunutu16 and Pynq Branch v2.5.1
and Vivado/PetaLinux 2019.1

With Branch 2.5.1, I can’t see this error anymore.
Problem seem like starting after 2.5.1