This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TSW54J60 - JESD204B clocking and LMK04828 problem

Other Parts Discussed in Thread: ADS54J60, LMK04828

Hi,

We are currently testing the TSW54J60 EVB (paired with TSW14J56) and have a couple of questions.

First, I have a lack of knowledge in the JESD204B protocol. In HSDC Pro, if you enter a sampling frequency of 500 MHz for the ADC you will need a JESD core clock of 125 MHz. This comes from the 2 lanes we use per ADC (LMFS4211 configuration) and we have to divide the JESD data rate /40 (5Gsps becomes 125Msps). Now there is an hard coded trick in the ADC configuration that makes it so when you go under 3.125Gsps data rate (78.125MHz core clock), the software will instead ask for the same core clock as the sampling clock (300 MHz sampling = 300 MHz core clock). 

The exact line that does this in the ADC firmware config file must be the following (in ADS54J60_LMF4211.ini) :

MIF Config= 0.611G to 0.7G:RX:RX_PMA_x5,0.7G to 3.125G:RX:RX_PMA_x10,3.125G to 10.25G:RX:RX_PMA_x40

My understanding is this is a way to bypass the minimum FPGA transceiver frequency (which may be around 80 MHz). If this is true, then how come is the behaviour of having a 320 MHz data rate be the same as having a 80 MHz data rate in JESD204B?


My second question is about the setup of the LMK04828 which generates the clocks required on the EVB.

Using an R divider for OSCin of 1024 and an N divider for feedback of 12288 should do the same as using an R of 2048 and N of 24576. (same ratio)

For some reason, the PLL locks correctly with an R of 1024 but will not lock at 2048 nor 4096. I thought there could be a minimum phase detector frequency, but there is only a max of 155 MHz.

We'd like to use a large oscillator divider ratio to get more resolution in changing frequencies.

Any thoughts on this ?

Thank you,

Philippe

  • Philippe,

    This line in the ini determines the MIF file that needs to be streamed based on the lane rate calculated from ADC Output Data Rate.

    Format :

    [Lower Range] to [Higher Range]:RX:[MIF File Name]

    Regards,

    Jim

  • Hi Jim,

    Thank you for the precision, although my question was more about why the lane rate would be different from 0.7G to 3.125G (x10) than from 3.125G to 10.25G (x40).

    Philippe
  • Philippe,

    The lane rate is based on the ADC output sample rate, number of octets per lane and the decimation/interpolation factor if used.

    •Serial Line Rate = Fs * 10 * F   [bits/lane] (Note: # lanes influences F parameter, no inter/dec)            

    Regards,

    Jim

  • Jim, 

    The rate is indeed always Fs*10*F in the software.  In our case, F=1 in LMFS4211 so its always Fs*10

    I am talking about the clock you send to the FPGA. This clock is the Serial Line Rate / 40 (in 40x mode which uses 2 lanes instead of 4), so 250MHz with a lane rate of 10G (Fs = 1G). This clock is asked by HSDC Pro when you enter a sampling rate and you have to set the clock generator to send this frequency to the FPGA

    This clock, under 3.125G lane rate, becomes Serial Line Rate / 10.

    Why so?

    Philippe