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.

LMX2694EPEVM: Communication Issue - Board not identified

Part Number: LMX2694EPEVM
Other Parts Discussed in Thread: USB2ANY,

I am currently working on a development board for a PLL (lmx2694epevm) and I am not able to interact with via USB2ANY.

I have connected the 3.3V power (max 1A) to the board. Then I have connected a 100MHz reference clock at 0dbm, the programming cable and the RDOUTBM sma is connected to a high frequency oscilloscope.

However, USB2ANY is not able to identify the board after blinking.

I tested the power supply and it is 3.3V.

I measured some voltages on the board and it is

  • 2.5V between VDD and GND and
  • 3.3V between VDD and CE pin.

The oscilloscope at 40GHz is able to detect a different level of noise when it is powered up, however applying the FFT this is a low frequency noise.

Is there any way to understand if the board is functional or should I directly ask for a RMA?

Thanks in advance for any help.

  • Hi Giacomo,

    Did you follow the EVM user's guide to setup the board? There is a Troubleshooting Guide section in the user's guide, could you follow the flow chart to identify the problem?

  • Hi Noel,
    I am finally able to shutdown and reset the board and read the registry values. However I am now sure TicsPro is not updated to handle this board.

    All the configuration generated by TicsPro are not correct if compared with the official documentation (SNAS785D) of the LMX2694.

    Indeed if I try to load the configuration from the registries of board at the startup, these values are not evalued correctly by TicsPro simulation graph.

  • Hi Giacomo,

    TICS Pro default configuration is used to match the EVM, so that by using the default configuration, the EVM will lock to 7GHz output. 

    Please note, the register values after a reset are the silicon default register values. To use the device, we may need to program it to a different value. For example: