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.

Problem of TSW30SH84EVM Lock status

Other Parts Discussed in Thread: LMK04808, DAC34SH84, DAC34H84

   x00	x329C
   x01	x050E
   x02	x7052
   x03	xA001
   x04	xC076
   x05	x3F68
   x06	x2F00
   x07	xFFFF
   x08	x0000
   x09	xE000
   x0A	x0000
   x0B	x0000
   x0C	x05A6
   x0D	x05A6
   x0E	x05A6
   x0F	x05A6
   x10	x0000
   x11	x0000
   x12	x0000
   x13	x0000
   x14	x6666
   x15	x0A66
   x16	x0000
   x17	x1800
   x18	x246B
   x19	x0404
   x1A	x2400
   x1B	x0800
   x1C	x0000
   x1D	x0000
   x1E	x1111
   x1F	x8886
   x20	x1401
   x22	x1B1B
   x23	x07FF
   x24	x0000
   x25	x7A78
   x26	xB6B6
   x27	xEAEA
   x28	x4545
   x29	x1A1A
   x2A	x1616
   x2B	xAAAA
   x2C	xC6C6
   x2D	x0004
   x2E	x0000
   x2F	x0000
   x30	x0000
   x7F	x0000
LMK REGISTERS
   x00	x4000000
   x01	x400A040
   x02	x0000014
   x03	x0000014
   x04	x0000014
   x05	x4000000
   x06	x2800000
   x07	x042A800
   x08	x0288800
   x0A	x48A0210
   x0B	x1BF8880
   x0C	x098600D
   x0D	x1D81033
   x0E	x0900000
   x0F	x4000400
   x10	x00AA820
   x18	x0000006
   x19	x0080800
   x1A	x47D00C8
   x1B	x08000C1
   x1C	x0008180
   x1D	x0000064
   x1E	x0180064
ATTENUATOR AB
0.00
ATTENUATOR CD
0.00

Dear Sir or Madam:

I made a configuration for TSW30SH84EVM. The LMK04808 works as PLL2 internal VCO frequency at 3000Mhz, outputs 150Mhz to DAC34SH84 and FPGA by divider of 20. I measured the clock to FPGA was 150MHz. The INPUT page of TSW30SH84EVM page shows the PLL locked, however it is showing PLL UNLOCKED on page of Advanced. I checked the spectrum was also not good.

What the is reason for this? I think the PLL is not locked. Could you please help to check the configuration file uploaded? Is there anything wrong with configuration file?

DAC34SH84 works as PLL mode, interpolation by 4, input rate 150MSPS, output 600MSPS.

Thank you.

Regards,

Cheng

  • Hi Cheng,

    Under the PLL setting of the DAC34SH84 > freq. tune, you have set it to be 9. Most likely the VCO of the on-chip PLL is out of range. You will need to set this to about 32 to center the VCO frequency to be about 3GHz.

    The PLL Lock alarm in the advanced page (CONFIG5) will need to be cleared before it updates again for the current status. These alarms will not self-clear upon error recovery because it need to retain the error in between alarm polling intervals. You can check the "clear status" check box to clear alarm and check to see if the PLL LOCK status is cleared.

    The PLL lock status in CONFIG5 have a known issue in this silicon that may not accurately detect the PLL lock status properly under certain conditions (documents in the datasheet). The best way is to read back the PLL LF voltage in config0x18 for optimal VCO voltage. Adjust the freq. tune until the PLL LF voltage reads back 3, 4, or 5.

    By the way, a nice reference to LMK04808 configuration can be found on page 86 of the LMK datasheet. The condition is very similar to your case.

    -KH

  • Hi Kang:

    Thanks for your reply and valuable information.

    I tried to set the fine tune as 9 and still no lock at Advanced page. Also I manually cleared and updated alarm status and the result is the same.  The strange thing is that everything looks good if do not enable the DAC PLL and set the CLK4 as 600MHz (DACCLK). If set the DACCLK as 150MHz and enabled the DACPLL, the DACPLL can not really lock as Input page shows lock but the Advanced page does not. And at PLL mode the spectrum is also not good.

    Looks like PLL is locked when I played as 80Mhz mode using your configuration file. Could you please modify the configuration file I uploaded to make sure the DACPLL lock?  And then I will test it accordingly here.

    Thank you.

    Regards,

    Cheng

  • Dear Sir or Madam:

    Is there anyone can help out?

    Thanks,

    Cheng

  • Hello Cheng,

    Could you set the freq. tune (coarse) to be 32 like I mentioned before? By setting the freq. tune to be 32, you center the VCO tuning range to about 3GHz. I was able to get PLL lock on my TSW30SH84 setup.

    See attached. Let me know if it works.

    -KH

  • Hi Kang:

    Thanks for your information. I tried it, and when I set fine tune as 32, there is no lock. When I set fine tune as 9, the DAC side shows lock, but the Advanced page shows no lock. And looks like the PLL did not really lock. I did uncheck and check the status from Advanced page, it always shows unlock.  I pretty sure the hardware is good, as everything is ok if set the evaluation board as 2.88G

    Anything else I could try?

    Regards,

    Cheng

  • Hi Cheng,

    could you tell me the package label of U1 on your TSW30SH84EVM? Is it DAC34H84 or DAC34SH84?

    -KH

  • Hi Kang:

    It is DAC34SH84.


    Cheng


  • Hi Cheng,

    I have tested two TSW30SH84EVMs and both of them showed the on-chip PLL locked after loading my register settings. Also, all of the DAC34SH84 devices are tested for PLL lock range during manufacturing. Therefore, I do not think this is a device issue or register setting problem.

    On one of the EVMs I do see the on-chip PLL staying locked intermittently after I performed a "read all" event. I suspect the LMK register value might be lost after you perform a SPI register read back. This may be the reason that the DAC34SH84 on-chip PLL not staying locked because the reference clock keeps changing.

    Do you have a USB Blaster or Byte Blaster to program the on-board CPLD? If so, you can update the on-board CPLD with the newer firmware. Afterwards, you should be able to see the on-chip PLL staying locked at 600MHz. Instructions and the CPLD firmware are attached.

    If not, please private message me and we can discuss about replacement EVM.

    -KH

    CPLD Programming Procedure.zip
  • Kang,

    I think this response you generated may have been for someone else.

    FYI

    Pete Harbour

    ORB Analytics

  • The PLL issue should be resolved with the new CPLD firmware update. The old firmware did not have proper LMK04800 read back. This caused the LMK setting to be disturbed in read back mode.

    -KH