• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 2 answers
  • Subscribers 46 subscribers
  • Views 504 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.

ADS130E08: Sample program (interface)

Dallin Lloyd
Prodigy 160 points
Part Number: ADS130E08

Hello

I'm looking for basic sample code of interfacing with the ADS130E08. I have been unsuccessful finding any online. However i have found other threads where it was talked about.

Please let me know if this is available.

  • 0
    TI__Guru* 97775 points
    Hi,


    I believe the example code discussed in previous posts is now packaged with the installer for the EVM-PDK. You'll need to download this from the TI website. Starting from the ADS130E08EVM-PDK product page here:

    www.ti.com/.../ads130e08evm-pdk

    You can find the download for the ADS130E08EVM-PDK-SW within the Order Now section. Once you download and unzip it, let me know that you found the folder for the source code.


    Joseph Wu
  • 0 in reply to Joseph Wu
    Prodigy 160 points

    Thank you for your comment.

    We are trying to interface the ADS130E08 with a Raspberry Pi for our test station we are making. We are having difficultly getting a response from the ADS. I was unable to find anything helpful to diagnose why it is not working properly. I have followed the board layout documentation as well. Is there any advice you can give us to get this communicating? we are currently sending it 0x12. there is no response. 

    with best regards,

    Dallin

  • 0 in reply to Dallin Lloyd
    TI__Guru* 97775 points

    Dallin,


    There are many things that can impede communications to the device. To debug any kind of digital communication, there are several things I would try.

    First, I would certainly use an oscilloscope or logic analyzer to view the communication lines coming out of the device. This is the fastest way to ensure that the communication waveforms coming out of the master are as you expect. You can also verify the digital timing. If you can view this, and are still having problems, you can post the plot back in this thread.

    One quick check would be to verify the mode of SPI used to communicate with the device. This device uses CPOL=0 and CPHA=1 for the SPI, meaning that the SCLK dwells low at idle, and data is clocked in at the falling edge of the SCLK (you can see this in figure 1 of the datasheet and you should verify that the communication looks like this as well). I would then check to see that START, /RESET, and /PDWN are all high when using this device.

    If the device is operational and converting, I would check the /DRDY pin also. There should be a small /DRDY indication for each completed conversion. I think this device operates at a default of 8kSPS, so there should be a narrow /DRDY pulse every 125us.

    Instead of reading data, you may also try reading from the registers instead. For the RREG command, you should be able to read the registers, which should be a known default value at start up. If you can read from the registers, then I would check the WREG to write to the register and confirm that you are able to do that also.


    Joseph Wu

  • 0 in reply to Joseph Wu
    TI__Guru* 97775 points
    Dallin,


    I haven't heard from you for a while, so I thought I'd check on your communication issues with the ADS130E08. Hopefully, using a logic analyzer or oscilloscope helped you better debug the digital communications between the master and the device.

    I'll close this post for now, but if you continue to have problems, you can post back and we can return to debugging. Just have a few scope shots to show for the SPI communications.
  • 0 in reply to Joseph Wu
    Prodigy 160 points

    Joseph,

    We still do not have active communications. I have gone through our board layout multiple times now, and we are debugging with a logic analyzer. still not getting a response. I believe we have shocked the part, as it is unresponsive. If we have more questions i will post

    Thank you for your time.

  • 0 in reply to Dallin Lloyd
    TI__Guru* 97775 points
    Hi,


    I'm sorry to hear that your weren't able to get through communications and may have damaged the device.

    I'll close this thread for now, but if you want to, post back with the schematic and we can discuss the connections to the device and we'll see about getting you up and running. There might be some other issue, so I'd encourage you to post back.


    Joseph Wu