• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 1 answer
  • Subscribers 20 subscribers
  • Views 492 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.

LMK04610: TICS PRO Write registers that are not in the datasheet

Nicolas Papadopoulos
Prodigy 50 points
Part Number: LMK04610
Other Parts Discussed in Thread: LMK04616

I am using the LMK04610 evaluation board with TICS PRO software.

I noticed that TICS PRO write some registers that are not described in the datasheet register map.

For example, If I set the PLL2 ref clock combo box to divider, the register 0x6D is written, what is normal; But also the register 0xAF is written.

I do not found this 0xAF register in the datasheet and it seems that this register is necessary.

I tried to write my own configuration sequence without this 0xAF register and my configuration doesn't start well.

Can you help me to understand this ?

In addition, I notice that if i click on the "read all registers" button, TICS PRO read all register and write the following registers: 0x20 0x56 0x57 0x21 0x22 0x61 0x62 0x1F.

BR.

  • 0
    TI__Mastermind 28960 points

    Hi BR,

    Bit 0 in 0xAF is PLL2_RDIV_CLKEN, which enables the clock to the R divider mux. I'm unsure why this isn't disclosed, as it is required for using the R divider. Likewise, bit 0 in 0xB0 is PLL2_NDIV_CLKEN, which enables the clock to the N divider mux. Again, I'm unsure why this isn't disclosed, as it is required for using the N divider. In any case, the remaining bits in both 0xAF and 0xB0 are reserved and should always be written to 0. Refer to the LMK04616 datasheet for additional information on 0xAF and 0xB0, as the LMK04616 uses the same die and does disclose these fields. Meanwhile, I'll put this on our list of corrections for the next datasheet update.

    TICS Pro seems to be writing to the divider registers during readback, which is not required or recommended during readback. I am reviewing the software for the root cause. When reading back all registers, do you ever observe the values written to be different from the values read? If readback is causing values to be overwritten with different data, we will prioritize correcting this bug for the next release.

    Regards,

  • 0 in reply to Derek Payne
    Prodigy 50 points

    Hi Derek,

    Thank you for the detailled informations. Indeed it make sense.

    I have another question.

    I used the frequency planner tool and the PLL2 loop filter tool in order to find the right PLL2 configuration for my application. These tools give me a valid VCO frequency of 5824 MHz. I sent this configuration to the LMK04610 EVM board and it works. I got the right output frequencies. But looking at the datasheet page 11, the PLL2 VCO tuning range seems to be between 5870 MHz and 6175 MHz. Do you know why the tool suggest me an under specified VCO frequency ?

    Regards,

  • 0 in reply to Nicolas Papadopoulos
    Prodigy 50 points

    I forgot to reply to your second point. I will check today if readback cause the writen values to be different from the read values.

    Regards,
    Nicolas.

  • 0 in reply to Nicolas Papadopoulos
    TI__Mastermind 28960 points

    Hi Nicolas,

    Originally in development we planned for the VCO range to be 5800MHz to 6200MHz, but we encountered some VCO centering issues during development which resulted in some devices being unable to support the full frequency range across PVT. Some devices may be able to function with the VCO at 5824MHz at room temperature, but there could be issues over temperature and across parts.

    It looks like TICS Pro is still using the old VCO range. I'll make sure this gets updated in the next version of TICS Pro.

    Let me know what you find regarding readback.

    Regards,

  • 0 in reply to Derek Payne
    Prodigy 50 points

    Hi Derek,

    Thank you for your reply.

    Regards.

  • 0 in reply to Nicolas Papadopoulos
    TI__Mastermind 28960 points

    Hi Nicolas,

    We haven't heard from you in a week, so I have to assume your issues are resolved for now. I'll flag the write during readback as something to be investigated for a potential future bugfix. Please feel free to open another thread if you need support with a different issue.

    Regards,

  • 0 in reply to Derek Payne
    Prodigy 50 points

    Hi Derek,

    Due to the coronavirus pandemic and our country's lockdown, I was unable to do further testing.

    Yes my issue is resolved thank you.

    Regards,