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.

LMK03318: unstable clock generation issue_continued ticket

Part Number: LMK03318

Hi Adam Siismets

Previous ticket has been locked and I am not able to udpate status. So I open new ticket with the same question.

At Previous ticket, You gave some idea as below.

========================================================================

Can you confirm that you waited for the device to stabilize in the error state before pulling PDN low for 2ms? Again, it would be helpful to see a plot of VDD and PDN vs time to make sure the ramp is monotonic and that PDN doesn't ramp up too quickly.


As for the N divider problem, could you route PLL RDIV/2 and PLL NDIV/2 to the Status0 and Status1 pins and send plots for the N divider at 64 and 66? This will help verify that the PLL is working properly. I will do the same measurements so that we can compare.

=========================================================================

Regarding PDN and VDD, I checked the plot of both VDD and PDN. PDN was plot in yellow. Now customer check VDD Plot in order to make Supply rail ramped in monotonic manner.

However, We'd like you to cofirm if VDD ramp can cause reported problem.

When issue was reproduced

 1) R50 (Input select): 0x53

     select PRI (PRI/Sec : differential input mode)

 2) R29 (control over input):0x0f

 3) R13(INT Status): 0x00

   ->  there was no  interrupt for loss of lock, loss of input 

 4) status pin

   -. status pin #1: 1

   -. status pin#2: : 0

  • Hi again,

    I will continue to look into your problem. Thank you for providing me with that information.

    Have you made any modifications to the TICSpro configuration since the original post? If so, could you please export an up to date version of the configuration? (inside TICSPro, File > Save)

    Adam

  • Hello,

    All options provided by the wizard should work, and theoretically setting N divider to 64 or 66 shouldn't matter. I assume that you are using EEPROM and sometimes there's a problem powering up from EEPROM, correct? When problem occurs, can you (1) read back all registers, check if PLL is locked (LOL), if reference is valid (LOS), if the outputs are muted and if SYNCN_SW is 1. (2) write all registers (with N div = 64, there's nothing wrong with N = 64) then write a 1 to "RESETN_SW"?

    It's helpful to first figure out if it's a EEPROM problem or configuration problem.

    Regards,
    Hao