AnsweredAssumed Answered

ZedBoard and AD-FMCOMMS1-EBZ problem

Question asked by oleg.latin on Oct 4, 2013
Latest reply on Oct 6, 2013 by oleg.latin



I have ZedBoard Rev C. and AD-FMCOMMS1-EBZ Rev B.

I obtained reference design from here: and followed this tutorial: I took an existing SDK export (system.xml, system.bit, etc) and make FSBL, u-boot and uImage myself (as in tutorial).


But seems to linux kernel cannot probe drivers for xcomm board (see attached boot.log file). I debugged it a bit and seems what xiic driver (linux/drivers/i2c/busses/i2c-xiic.c) makes iowrite32 to wrong addresses (i2c@0xe0860000 and i2c@0xe0880000, but in devicetree zynq-zed-adv7511-xcomm.dts i2c@4160000 and i2c@4162000) and reporting error -110 (ETIMEDOUT).


Also device tree have kernel boot command "console=ttyPS0,115200 root=/dev/mmcblk0p2 rw earlyprintk rootfstype=ext4 rootwait devtmpfs.mount=0", but kernel wants ramdisk image and don't mount second partition from sdcard.


Any ideas how to make it work? Precompiled image ( works fine.