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.

Linux/ADS5282EVM: Labview code

Part Number: ADS5282EVM
Other Parts Discussed in Thread: ADS5282

Tool/software: Linux


I am interested in programming the ADS5282EVm registers via c code. DO you have any guidelines/documents to propose?

Is the labview code of the GUI available in order to use it as a reference?



  • Hi,

    we do not have guidelines or documents for the use of the USB port on the EVM for controlling the SPI signals.  The SPI GUI installer that is on the TI web for this EVM is supposed to be a simple complete easy to use way of controlling the EVM. 

    Attached is a zip file of the labview source code for the SPI GUI for that EVM.  The hard part is getting the handle to the USB port open so that the GUI can steam the data to the USB device to make the SPI signals wiggle in the required format.  The labview code is to be accepted as-is as reference material only.


    Richard P. 

    USB SPI Labview

  • Hi Richard,

    Thank you for the prompt reply...I am interested in program the ADC (sent the corresponing values to the respective registers) via c code.

    I would like to ask you about something that it is written in the ADS5282EVM manual

    "Software Operation: Users must use the accompanying software to issue a reset command
    before taking measurements. In addition to providing the ADS528X with the initialization
    register writes detailed in the data sheet, the accompanying software also sets the state of
    ADC pins ADCRESET and PD. Failure to do so can cause improper operation."

    So besides the initialization registers that have to be written as referred to ADS5282 manual to i have to have some action about the ADCRESET and PD signals? And what should be this action?

  • Hi,

    The early silicon for the ADS5282 required a few special initialization registers to be written, with a subsequent update to the production silicon to make the special register writes no longer needed.   So the datasheet has a footnote (1) on page three saying that these special register writes are no longer needed but that if they were performed anyway then there would be no harm in doing so. 

    Since the early release of the SPI GUI might be in conjunction with an EVM with early silicon, the SPI GUI was written to do these special register writes when the reset button of the GUI was clicked.    So the User Guide said to be sure to click the reset button of the GUI.   And if you were to do so and watch the log of register writes being performed in the GUI panel, you would see these special operations being done every time you pressed the reset button.   So in your design you would just need to do whatever SPI writes are needed to set the device up in whatever mode you wish to see it in.   A reset pulse on the reset pin first or alternatively a software reset by a SPI write to the reset bit, and then whatever register writes your design might require.  That would be all.     For example, the old TSW1200 capture card was created to expect the serial data msb-first and the default for the ADS5282 was lsb-first so a SPI write was needed for setting msb-first when used with the TSW1200.  The newer TSW1400 was created to expect the data lsb-first so this SPI write is not needed for the TSW1400.   In your design, you get to choose what mode of operation you wish for the ADS5282 and program the SPI accordingly.   You could even design your FPGA interface to accept the default configuration of the ADC and simply assert the reset pin and then do no SPI operations at all.  But you may wish to use the debug features available by SPI writes such as the test patterns, or the programmable gain, etc.


    Richard P.