• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 21 subscribers
  • Views 426 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

LMK03328: In case of PRIREF=no input, SECREF=50MHz

Hirotaka Matsumoto
Guru 27525 points
Part Number: LMK03328

Hi all

Would you mind if we ask LMK03328?
Could you refer to the attachment file "20200213_LMK03328EVM.pdf"?
20200213_LMK03328EVM.pdf

The following is the TCS file which is relation to our questions.
20200213_LMK03328_A.tcs

Kind regards,

Hirotaka Matsumoto

  • 0
    TI__Mastermind 18070 points

    Hi Hirotaka-san,

    PRIREF doesn't need to be present. SECREF alone is sufficient.

    I have very limited lab access right now so let me first explain the basic debugging procedures:

    1. Check PLL lock status and if SECREF is valid. To do so, go to status page, configure the two status pins and observe the status LEDs on the board. For example, SECREF LOS means loss of SECREF, when it's active, it means that SECREF is lost; PLL2 LOL means PLL2 loss of lock.

    2. If reference is valid but PLL is not locked, load default configuration first for sanity check (in the tool bar, go to "default configuration" -> "EVM default")

    3. If reference is valid and PLL is locked but there's no output, check and make sure that the SYNCN pin is high and the output is not disabled or powered down. Also make sure that the SYNCN bit is high.

    In general, please start from EVM default and use the wizard page to configure the device. If the problem persists, then I'll let my coworker help check it in the lab.

    Regards,

    Hao

  • 0 in reply to Hao Z
    Guru 27525 points

    Hao san

    Thank you for your reply.

    1. Check PLL lock status and if SECREF is valid. To do so, go to status page, configure the two status pins and observe the status LEDs on the board. For example, SECREF LOS means loss of SECREF, when it's active, it means that SECREF is lost; PLL2 LOL means PLL2 loss of lock.
    ->Please refer to the page4 and page 5 on the attachment file.
       In case of PLL = lock status, the STAT1 LED turns on with our TICSPRO's setting.
       Therefore, it seems to keep Lock condition.  
    20200214_LMK03328EVM.pdf

    2. If reference is valid but PLL is not locked, load default configuration first for sanity check (in the tool bar, go to "default configuration" -> "EVM default")
    ->EVM doesn't have any damege. EVM operates in any case which includes default setting. 

    3. If reference is valid and PLL is locked but there's no output, check and make sure that the SYNCN pin is high and the output is not disabled or powered down. Also make sure that the SYNCN bit is high.
    ->Could you refer to .tcs file which we attached yesterday?
       We confirmed as follows;
       -SYNCN pin is high
       -Outputs are enable
       -Outputs are not powered down.

    If the problem persists, then I'll let my coworker help check it in the lab.
    ->Yes, could you check our phenomenon using LMK03328EVM?


    Kind regards,

    Hirotaka Matsumoto

  • 0 in reply to Hirotaka Matsumoto
    TI__Intellectual 950 points

    Hello Hirotaka-san,

    I was able to successfully reproduce this problem on our LMK03328EVM board and have determined an explanation / solution. 

    In your configuration, the SYNC_AUTO and SYNC_MUTE fields are enabled. This means that upon startup of the device, a synchronization event begins and all of the outputs are muted. Because PRIREF is not connected, there is no output on OUT4 so all of the outputs cannot be properly synchronized which results in the outputs staying muted. 

     

    If you disable the SYNC_AUTO field, this behavior should not occur. A synchronization event can be manually issued later after PRIREF has been turned on. Alternatively, you can choose to bypass the mute function for each output by changing the CHX_MUTE_LVL field to "Mute Bypass"

    Hopefully this resolves your issue.

    Regards,

    Adam

  • 0 in reply to Adam Siismets
    Guru 27525 points

    Adam san

    Thank you so much for your cooperation!
    We could confirm that this resolved our issue using our LMK03328EVM!

    Kind regards,

    Hirotaka Matsumoto