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.

LMX2694-EP: LMX2694-EP Lock Detect

Part Number: LMX2694-EP
Other Parts Discussed in Thread: LMX2594,

Hello,

I have an application using VCO4 at a single clock frequency. We were using the LMX2594, however once the LMX2694-EP became available, we moved to that. I am wondering about the difference between lock detect on the LMX2594 and LMX2694-EP. From the previous post and evaluation of the eval boards, it appears that the LMX2694-EP does not detect a "reference not attached - unlocked condition" on the mux line while the LMX2594 does.

From the previous post it sounds like a Ref IN is required to detect lock effectively on the mux pin in lock detect mode for the LMX2694-EP.

I am also wondering about the best way to utilize the LMX2694-EP for lock detect and its limitations.

It seems like a robust lock detect using no external circuits would be:

  • Utilize Vtune and VCOCal on startup over the mux line as "Lock Detect".
  • Once the chip has been programed and has had a chance to lock, periodically query R110's rb_LD_VTUNE register for loss of lock in "Readback" mode as part of BIT (built in test) routine

Does this seem reasonable?

Related post: https://e2e.ti.com/support/clock-and-timing/f/clock-timing-forum/980839/lmx2694-ep-muxout-still-functions-as-lock-detect-for-oscin-loss-after-calibration-during-operation?tisearch=e2e-sitesearch&keymatch=LMX2694-EP#

  • Bill

    The issue with the lock detect is that the state machine clock is rune by OSCin.  If OSCin is removed (on the LMX2694), then this can stop the state machine clock before the part has a chance to detect that the device is out of lock.

    "Vtune" lock detect actually does not directly measure the tuning voltage on the Vtune pin.  Rather, this based on something that is supposed to mimic that voltage.  However, if the input reference is removed, it will fool the Vtune lock detect and rb_LD_VTUNE.

    REgards,

    Dean