ADI Reference Design for ZC702, AD9467_FMC and AD9739a

Hallo,

I have the same Boards (ZC702, AD9467 FMC and AD9739a) like in this Thread (AD9739A-FMC-EBZ / AD9467-FMC). Based on Istvan advice to include the no-OS Software, I am trying to built the HDL File, first. Afterward I want to export it to sdk and use the no-OS Software, too.

For this purpose I have to built my own HDL File because neither the AD9467 FMC nor the AD9739a supports the carrier for the ZC702. My Idea is to built a HDL file with the ADI Reference Designs for one of the supported Carriers (like ZED) and do some changes to get them running on the ZC702. Is this possible?

Building the libraries worked fine, I also inserted the two missing library cores. But when I tried to build the project for the ZED, I stuck with these Errors, which can be find in attachment.


Can someone help me, please? And is there a better way to get the Board running?

Thanks,

Tudo

loglife.txt.zip
Parents
  • Hallo,

    for my situation I need a custom devicetree because the zc702 is using ad9467 via fmc1 and ad9739a via fmc2. Or what did you mean with download dts?

    So I will summerize what's done by now with the basis zynq-zc702-adv7511 devicetree:

    1) Imported lines for ad9467 from zynq-zed-adv7511-ad9467-fmc-250ebz

    2) Imported lines for ad9739a from zynq-zc706-adv7511-ad9739a-fmc

    3) Changed clashed phandle clock and spibus-connected for adf4350 and ad9739a to unused values: 0x25,0x2f,0x2e (highlighted)

    Until this step just the ad9739a works fine, so with the help of 'dmesg' there was a double definition for spi@e0006000, so:


    4) Changed ad9467@2 {reg=<0x2>} and ad9517@3 {reg=<0x3>}

    Issue with spi double definition was solved. But there is no reaction on ad9467. Dmesg: 'Driver ad9467 requests probe deferral' 'ad9517: Unrecognized CHIP_ID 0x0'

    5) Switched ad9467@0 {reg=<0x0>} and ad9517@1 {reg=<0x1>}

      and ad9739a@2{reg=<0x2>} and ad4350@3 {reg=<0x4>}

    Now ad9467 works fine but ad9739a no longer. Dmesg: 'Driver cf_axi_dds requests probe deferral' 'ad9739a: Unrecognized CHIP_ID 0x0'

    For CHIP_ID 0x0 i can't see any possibility to change this value. Can you explain what is necessary to fix that and can you please take a look on the appendix.

    Thanks!

    attachments.zip
Reply
  • Hallo,

    for my situation I need a custom devicetree because the zc702 is using ad9467 via fmc1 and ad9739a via fmc2. Or what did you mean with download dts?

    So I will summerize what's done by now with the basis zynq-zc702-adv7511 devicetree:

    1) Imported lines for ad9467 from zynq-zed-adv7511-ad9467-fmc-250ebz

    2) Imported lines for ad9739a from zynq-zc706-adv7511-ad9739a-fmc

    3) Changed clashed phandle clock and spibus-connected for adf4350 and ad9739a to unused values: 0x25,0x2f,0x2e (highlighted)

    Until this step just the ad9739a works fine, so with the help of 'dmesg' there was a double definition for spi@e0006000, so:


    4) Changed ad9467@2 {reg=<0x2>} and ad9517@3 {reg=<0x3>}

    Issue with spi double definition was solved. But there is no reaction on ad9467. Dmesg: 'Driver ad9467 requests probe deferral' 'ad9517: Unrecognized CHIP_ID 0x0'

    5) Switched ad9467@0 {reg=<0x0>} and ad9517@1 {reg=<0x1>}

      and ad9739a@2{reg=<0x2>} and ad4350@3 {reg=<0x4>}

    Now ad9467 works fine but ad9739a no longer. Dmesg: 'Driver cf_axi_dds requests probe deferral' 'ad9739a: Unrecognized CHIP_ID 0x0'

    For CHIP_ID 0x0 i can't see any possibility to change this value. Can you explain what is necessary to fix that and can you please take a look on the appendix.

    Thanks!

    attachments.zip
Children
No Data