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.

ADS1675REF: Windows 10 Driver for the TI Analog-to-Digital Component

Part Number: ADS1675REF

In a 2012 E2E forum reply to a customer, Gregg Huff states that Texas Instruments is willing to send the FPGA source code.  Because Texas Instruments does not seem willing to help supply the proper and current information to a customer who will be buying a number of ADS1675 products plus other TI products, we feel stuck in the mud of creating a driver for our signal analyzer software to properly communicate to the ADS1675 design we created which at this point in time is linked to the USB environment via Opal Kelly XEM3010 card.  I even tried to communicate my frustration to Richard Templeton (CEO of TI) and that was a joke.  WE NEED HELP NOW from Texas Instruments!!! Please contact Chris Seberino, who is quite experienced and also has a PhD in Computer Science. or (936) 235-1139.  And remember, it is today's world we are using these Texas Instruments components in - Windows 10 64-bit Pro.  The military, who is a major user of signal analyzers, must use Windows 10, not Windows XP.

  • Hi John!

    I see that Ryan and Keith both sent the source code and VHDL files you had asked for over the last 18 months, however I don't see where you replied to either of them saying that you were having trouble with the files/documents they provided. 

    Our ADS1675REF has two different components to it, one is the ADCPro portion, which is LabView based and does the analysis portion, the other is the EVM specific 'plug-in' to ADCPro which interfaces to the Opal-Kelly FPGA card.  Can you tell us where you are having communication breakdowns? 

    We have recently been updating quite a few installers to accommodate Windows 10 and trying to envision every possible permutation of hardware given the increased security measure on signed vs. unsigned drivers, who has admin rights to the PC, IT safeguard systems on external installers, etc., it's not always possible to get things right for every use case scenario.  I'd like to understand yours a little better.

  • Hi Tom,

    As I stated previously, I have Chris Seberino in the Houston, Texas area developing the driver we need in order to have our signal analyzer software, DynamicPRO, be able to request digitized data from the ADS1675 via the Opal Kelly XEM3010 interface.  Our analyzer software operates in the Windows 10 64-bit PRO environment.  Chris can tell you what specific issues he is having, so I would sincerely appreciate if you would communicate with Chris.  His email address is:  His telephone number is: 936-235-1139.  The reason for this urgency is because we have long-term relationships with the military and we need to quickly get the new driver operational for some signal analyzers based on your TI ADS1675 delivered very soon.  If you need to charge me for the time, then so be it.  You can communicate directly with me at:

  • Hi John,

    I hope the files we provided to you and Chris get you where you want to be.  The ADS1675REF and the XEM3010 were put together as a pair of boards for use with our ADCPro tool.  The hardware, software and associated VHDL were put developed in such a way as to facilitate the functions we implemented in our ADCPro software, without much thought towards making it into a development system (short sighted as it may be, that was not our goal at the time when we released the software).  Our goal was to make an evaluation platform for the ADS1675, and then let the end user decide how to implement the device in their particular system (using a micro, DSP, FPGA, etc.) with their choice of host controller.  We can continue as needed off line, for now I am going to close out this post.