Post Go back to editing

How to set sample rate in AD9081 via pyadi-iio

Category: Software
Product Number: AD9081-FMCA-EBZ


With pyadi-iio I am able to configure my MxFE AD9081 board connected to Xilinx ZCU102.

However I am not able to change the sample rate on either ADCs or DACs.  On the ZCU102 Linux system, using the paths found here:

I get for example:

root@analog:~# cat /sys/bus/iio/devices/iio:device2/out_voltage_sampling_frequency

Can I use the python bindings to set the part up to use a higher sampling rate?  Or does it require some change in the device tree?  I understand this may require some change to the JESD204 settings to support the higher rate.

Any example on using the AD9081 at or least nearer to the max sample rates (12 GSPS for DAC, 4 GSPS for ADC) would be much appreciated.

Best regards,


  • I found this discussion which answers a lot of my question: 

    In  's response, where I'm not clear now is how to build the device tree for my particular board set (zcu102 and AD9081-FMCA-EBZ) - none of the options on the linked page match this configuration.



  • Changing the sample rate is not a simple operation with JESD-based devices. As it requires changing the clocking configuration between the converter, clock chip, and FPGA. It can even require re-synthesizing the FPGA design.

    If you can stick to the current JESD mode, basically ignore the HDL aspect for now, you will need to do two things.

    1. Validate a know good configuration for the clock chip, converter, and FPGA clocks. There is a tool that can help called pyadi-jif which does this validation. Example: Doc: .  pyadi-jif proves out the clocks for the different components and will solve for good configurations.

    2. Once you know the config will work for that rate you will need to translate it to devicetree. Here is documentation on configuring devicetree for AD9081: 

    For advanced users and likely contains bugs: There is some early beta work that will generate the devicetree fragment for you from the pyadi-jif generated structs which is part of the devicetree manager we maintain with pyadi-dt. Example:  Doc:

    To use this you would create a config structure from pyadi-jif then feed that to pyadi-dt to generate the dts fragment. Then compile that with the kernel.


  • Hi Travis,

    Thanks for this detailed response.  Sorry for the late reply, I must have missed the notification email!  I'm back looking at this again after some time away from it, and these links are very helpful.

    I think I'm getting close to getting a working setup, but I'm still unclear about a couple things.

    1)   For the AD9081 ADC side, there is a JESD quick configuration mode referred to like:
    adi,link-mode = <10>;            /* JESD Quick Configuration Mode */

    However, my JESD quick configurations for ADC side are in the form "X.Y", for instance "10.1".  How do I translate this into a uint32 value expected by the adi,link-mode ?

    2) What JESD changes will require an HDL change?  I see that the HDL project is set up for 8 Lane width in the parameters, so I would think I can do up to 8 lanes.  I don't see other JESD parameters in the HDL so I'm assuming they can be programmed, but maybe I'm missing something.

    Thanks again!

  • 1. This is just the JTX_MODE from the table

    2. The HDL should be built based on the JESD params of the desired mode. These are set by command line arguments to make or by modifying the top level system_project.tcl file.


  • I think I found the table you are referring to in the adijif/converters/resources folder.  If I'm reading this correctly, bits [7:6] are for the ".Y" and bits [5:0] are for the "X". 
    So to do 10.1 I'd need to write binary 01 001010, or 0x4A:

    adi,link-mode = <0x4A>;

    Is that correct?

    On the HDL question, thanks, I see all the parameters now.  It seems like I will need to rebuild the project with these parameters changed for this to work.

  • JTX_MODE I was referring to was from the UG but the one in pyadi-jif are the same.


  • Hi Travis,
    Following up on the HDL changes for JESD lane rate changes:

    I ran the ad9081_fmca_ebz/zcu102 make, passing in the parameters like this

    Build completed successfully.  I was scanning the log after the build, and I noticed the following warnings:
    WARNING: [Synth 8-3301] Unused top level parameter/generic RX_LANE_RATE
    WARNING: [Synth 8-3301] Unused top level parameter/generic TX_LANE_RATE
    WARNING: [Synth 8-3301] Unused top level parameter/generic RX_JESD_M
    WARNING: [Synth 8-3301] Unused top level parameter/generic RX_JESD_S
    WARNING: [Synth 8-3301] Unused top level parameter/generic RX_JESD_NP
    WARNING: [Synth 8-3301] Unused top level parameter/generic RX_TPL_WIDTH
    WARNING: [Synth 8-3301] Unused top level parameter/generic TX_JESD_M
    WARNING: [Synth 8-3301] Unused top level parameter/generic TX_JESD_S
    WARNING: [Synth 8-3301] Unused top level parameter/generic TX_JESD_NP
    WARNING: [Synth 8-3301] Unused top level parameter/generic TX_TPL_WIDTH
    WARNING: [Synth 8-3301] Unused top level parameter/generic TDD_SUPPORT

    It looks as if most of the parameters are not actually being used in the RTL.

    Is this expected?

    Thank you!