AnsweredAssumed Answered

adv7511 HDL reference design missing eth0 and DMA interrupts

Question asked by mikelee188 on Jun 4, 2017
Latest reply on Jun 9, 2017 by larsc

Hi ADI,

 

zedboard, vivado 2015.4, petalinux 2015.4, adv7511 HDL reference design, AXI-DMA loopback, ethernet, interrupt

 

I added an extra AXI-DMA loopback on top of adv7511 HDL reference design in Vivado 2015.4, then exported  bitstream hardware to SDK, and finally constructed the petalinux project to generate " BOOT.BIN and Image.ub " files.

 

There are 6 designed interrupts, while 88 / 89 belong to AXI-DMA loopback MM2S and S2MM.

      86  gpio
      87  41620000.i2c
      90  41600000.i2c
      91  xilinx-vdma-controller

      88  xilinx-dma-controller
      89  xilinx-dma-controller

 

Petalinux scripts looks like below,

 

      petalinux-create --type project --name MYPROJECT --template zynq

      petalinux-config --get-hw-description=<sdk directory>

      petalinux-config -c kernel --defconfig zynq_xcomm_adv7511_defconfig

      petalinux-build

      petalinux-package --boot --fsbl zynq_fsbl.elf --fpga system_top.bit --u-boot --force

 

However, two problems appear of this petalinux build,

1. " ifconfig " only shows lo portion, and misses eth0

2. " cat /proc/interrupts " misses AXI-DMA loopback MM2S and S2MM.

 

For comparison, I built another project with xilinx_zynq_defconfig on the same vivado/sdk HDF outputs, with exact same device-tree files located inside  /MYPROJECT/subsystems/linux/configs/device-tree/ . Notice some portion of files had already been modified to accommodate zynq-zed-adv7511.dtsi . Both zynq_xcomm_adv7511_defconfig and xilinx_zynq_defconfig are from GitHub - analogdevicesinc/linux at xcomm_zynq_4_0

 

      petalinux-create --type project --name MYPROJECT2 --template zynq

      petalinux-config --get-hw-description=<sdk directory>

      petalinux-config -c kernel --defconfig xilinx_zynq_defconfig

      petalinux-build

      petalinux-package --boot --fsbl zynq_fsbl.elf --fpga system_top.bit --u-boot --force

 

This build shows both lo and eth0, also it shows 88 / 89 AXI-DMA interrupts, while it misses 87 / 90 41620000.i2c interrupts as expected, since xilinx_zynq_defconfig may not recognize ADI's i2c.

 

The boot-up sequences of both builds are in the attachment,

 

find one similar reported on 2014 AD-FMCOMMS3-EBZ and ZC702 ethernet problems , though it does not solve my problem.

 

Please advise, thanks in advance

 

Mike

Outcomes