Post Go back to editing

How to edit the talise_config.c file so it matches the output files from the Profile configuration wizard

The platform I use is the ADRV9009 and the ZCU102.

How to edit the talise_config.c file so it matches the output files from the Profile configuration wizard?

I can't figure out how the entries of Tx and lpbk has to be translated. They are separate in the profile configuration wizard and combined in the talise_config.c file.

The profile configuration wizards has a FIR array for Tx and lpbk. But the talise_config.c has only one.

  • Talise_config.c
  • From the Profile configuration wizard. How shall I convert the following 3 array items?
    <lpbk>
         ...
         <filter FIR gain_dB=-6 num=48>
         ...
         <lpbkAdcProfile num=42>
         ...
     </lpbk>
    <tx...
         <filter FIR gain_dB=0 numFirCoefs=20>
          ...
     </tx>


The platform I use is the ADRV9009 and the ZCU102
[edited by: JV-IE at 11:29 AM (GMT 0) on 16 Apr 2019]
  • I have fond what the error means:

    • SYSREF phase error, a new SYSREF had different timing than the first that set the LMFC timing.

    Can you also point me what the rules are for SYSREF?

    • I already checked the timing tH and tS on a oscillocope. SYSREF and REF_CLK are aligned how it should be aligned. (Valid sampling window)
    • Do I have to recalculate the sysrefDivide as well (setting AD9528)? I changed my REF_CLK from 122,88MSPS to 120 MSPS? At this moment it is set to 512.
  • Different SYSREF divide factor value doesn't change the result...

    2 questions:

    1. The K divide factor is now set to 512. This will change my SYSREF clock frequency from 240KHz (122,88MHz VCO) to 234,375KHz(120MHz VCO). Could the extra decimal digits be a problem for the Talise package? Is this the reason why there is chosen for a 122,88 MHz crystal instead of an number like 120 MHz.
    2. Is there an example talise_config.c file available with a deviceClock which is not from the list below? (if I divide those by 512, I always end up with less extra decimal digits compared to the 234,375KHz)
  • Hi ,

    I see the original question was answered, you were able to generate talise_config.c using ADRV9009 Transceiver Evaluation Software by inputting into it the profile generated with the Talise Profile Configuration Wizard.

    The discussion then switched topic to actually getting a working profile and then dried out, sorry for that. Being an old thread, is the 2nd discussion still valid ? If yes, I will split this conversation into a new thread.

    Regards

  • I use the outputs from teh evaluation software to update : https://github.com/analogdevicesinc/linux/blob/master/arch/arm64/boot/dts/xilinx/adi-adrv9009.dtsi

    I will not dynamically update profiles. I will use one fix profile.