• TI Thinks Resolved

CDCM6208: PLL lock issue

Intellectual 850 points

Replies: 5

Views: 108

Part Number: CDCM6208

HI,

I am using CDCM6208, interfaced CDCM6208 with TM4C1294NCPDT TIVA C microcontroller, on our board there are 3 CDCM ICs, out of both 2 are working fine and one is not functional . On one IC PLL is not getting locked properly. 

I checked the power and input clocks both are fine. SPI write and read backs are happening fine . As soon as SPI writes are done PLL lock is asserted high for a small duration of time and again it goes low, what would be the possible issue?

Thanks,

Janardan 

  • Hi Janardan,

    I know that you've checked the input, but this still might be due to input matching or termination. You can compare your schematic with TI EVM schematic and start with the GUI that comes with the EVM.

    Regards,
    Hao

  • In reply to Hao Z:

    Hi Hoa,

    Thanks for the response, we have checked the input clocks and it appears clean. 

    Let me elaborate the scenario. 

    Previously we were using Stellaris LM3S2D93 controller to configure the same CDCM IC. Stellaris part  was running at 16Mhz .In this case CDCM Ic is responding as expected. PLL is getting locked.

    Presectly CDCM IC is same but we are trying to configure IC through TIVA C, TM4C1294NCPDT. Tiva is running at 25MHz. Here we are seeing the issue.

    Please guide me to narrow down the issue.

    Thanks and Regards,

    Janardan M

  • In reply to Janardan M:

    Hi Janardan,

    It seems like this might be due to SPI clock speed according to your description. Is there a way to reduce the SPI speed on your new controller? Also, with LM3S2D93 and  TM4C1294NCPDT, are you passing the same registers in the same sequence to CDCM6208?

    Regards,

    Hao

  • In reply to Hao Z:

    HI Hao,

    The sequence in which CDCM is configured remains same for both the controllers.

    As mentioned earlier 2 CDCM ICs on board are working as expected. 3rd CDCM IC I am able to write and read back the registers but PLL is not getting locked , so I am not seeing that to be SPI related issue.

    But I will further reduce clock speed and test the setup and update on observation.

    Thanks,

    Janardan 

     

  • In reply to Janardan M:

    Hi Janardan,

    When there's loss of lock while the register setting is correct, the problem is often due to failure of input detection. Meaning that it fails to detect input signal due to input distortion caused by impedance mismatch and reflection. I suggest trying different input formats and switching between PRIREF and SECREF if possible. I assume that you are not using crystal, correct?

    Regards,
    Hao