Hi,
I just purchased the ADS5263EVM and TSW1250EVM to give the new ADS5263 a try. The evaluation has been rockier than expected, and I'd appreciate any assistance!
1) The ADS5263EVM has input SMA connectors labeled CLK_INP and CLK_INN. I (wrongly) assumed that meant a standard differential LVPECL input clock could be used (such as the CDCM6100xEVM outputs). My mistake there, but when I went to use an LVCMOS clock from the CDCM6100xEVM connected to the ADS5263EVM's CDCLVP1102, I found that SLAU344 does not mention that LVPECL biasing resistors must be added, nor is VAC_REF connected to INN, which seems to be necessary. OK, this wasn't a question, but probably useful for others nonetheless, unless I'm missing something obvious.
2) I am providing a 100MHz clock to the ADS5263EVM. I've installed the latest GUI software packages for the ADS5263EVM and TSW1250EVM, and connected them via USB. Communication seems functional - I see things change when modifying registers in the ADS5263EVM GUI, and doing a "Capture Data" in the TSW1250EVM does indeed capture data. However, the data is garbled. When using the ADS5263 register settings called out in the user guide (page 12 of SLAU344), it appears that the upper and lower byte are swapped, and both upper and lower bytes have been rotated by 1 bit. Thus bit 0 is coming out at bit 9, etc, both in the GUI and on the test headers on the TSW1250EVM. I've confirmed this mapping by using the custom test patterns and setting a single bit at a time. My best guess is that the TSW1250EVM's FPGA is not correctly deserializing the datastream from the ADS5263EVM. Is there a particular sample rate I should be running at? Is there newer firmware for the TSW1250EVM I'm unaware of? The guide shows 80MHz in some of the screenshots, so I'll try that next.
3) The ADS5263EVM GUI debug function "Write Register" works. However, "Read Register" always returns FFFF (even with Reg Read set to enabled on the first tab). Is this a known bug?
Thanks in advance for any help!
-Greg