• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 46 subscribers
  • Views 332 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

HSMC-ADC Bridge Rev A with ADS6445EVM

John Brady
Prodigy 70 points
Other Parts Discussed in Thread: ADS6445

My research group purchased two ADS6445EVM and HSMC-ADC Bridges for use with Terasic DE-4 development board. We received Rev A. HSMC-ADC Bridges. While the documentation link on the website says the documents are for Rev A., the actual documents are for Rev B. It seems that Rev. A routes the ADC frame clock to the CLKIN_p1/n1 differential pair rather than the TX_p16/n16 pair as in Rev B. Since the clock pin does not have a deserializer, this makes it impossible for us to deserialize the frame clock and perform pattern checking to properly align the data. How can we resolve this issue.

  • 0
    TI__Mastermind 29220 points

    Hi,

    We can swap out your revA hardware for the revB hardware.  Actually, we have just gone to rev C which is the same as the revB except that the ADC connector was uograded to the locking Samtec connector that has an RT-1 in the part number to indicate retaining clips.   You could use either the revB or the newer rev C.  Both will plug into your EVMs.  

    The original adapter pin assignment was set for us by an Altera guy who looked at the signal named FCLK and naturally wanted to put that on a clock input.  And depending on how you want to use the signal, some people do want it on a clock input.  For my FPGA implementation, I latch in FCLK like any other data channel that meets setup and hold time around the bit clock so I want to see the signal on a data pair as you do.   But I have seen app notes from other sources that treat the FCLK as a clock input, so I guess there is not one solution that will please everybody.

    The literature number on the web says revA because it was revised since the first release.  So that document saying revA does not tie it to the hardware that was revA.  That is an unfortunate bit of confusion there.  Our hardware started with revA and the document with no revision, then the hardware goes to revB and the document goes to revA. 

    For the ADS6445 the revision A is the current and only revision of the EVM.

    If you can provide me with your contact info then I will try to round up two of the revB or revC boards.

    Regards,

    Richard P.