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.

LMX2594EVM: About power consumption and spurious in the actual test

Part Number: LMX2594EVM
Other Parts Discussed in Thread: LMX2594

Hello team,

I have a question about LMX2594EVM.

  1. Relation between register settings and power consumption

Datasheet 8.5.1 describes that I have to wait 10ms before writing R0. When I didn't put wait time between writing R1 and R0, the power consumption decreased about 20mA.(425mA -> 405mA) Is this behavior expected? If it is, is the TICS Pro GUI supported?

  2. Spurious when enabled both outputs

When I enabled both outputs A, B at the same time, both outputs had spurious of about -30dBc which is very high than when I enabled either one. Are these seems to be crosstalk spurious? If yes, is the board related, or inside the IC?

Best Regards,

Ryotaro Fukui

  • Hi Ryotaro,

    1. It seems you are giving a delay (10ms wait) after R1 and writing R0 after that. But it should be write all registers till R0 and then rewrite R0 after 10ms wait, that should show the actual power consumption and lock the device proper.

    2. LMX2594 RFout A and B has the isolation -50dBc and it should be in this range. The crosstalk can also be depends on the board trace routing and need to follow the layout guidelines mentioned in datasheet to reduce the crosstalk between the traces.

    Thanks!

    Regards,

    Ajeet Pal

  • Hi Ajeet,

    Sorry for the late response. Thanks to your advice, we were able to properly validate the spurious performance of the EVM. I would like to declare this case closed.

    1. Relation between register settings and power consumption

    Verified stable power consumption by following register write sequence.

    2. Spurious when enabled both outputs

    Confirmed that spurious would normally be around -50dBc, but that crosstalk would make it worse in actual usage.

    Best Regards,

    Ryotaro Fukui