• State TI Thinks Resolved
  • Locked Locked
  • Replies 11 replies
  • Answers 1 answer
  • Subscribers 47 subscribers
  • Views 227 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

ADS1114: EVM Usage

Mark Spring
Prodigy 120 points
Part Number: ADS1114
Other Parts Discussed in Thread: ADS1115, , ADS1113

Hello,

I implemented the ADS1114 in my design and I know have hardware on the bench. I have verified I can access and read the digital voltage value in the register. What I was hoping to do is use the ADS1115 EVM GUI to further verify my hardware before I have software available. Before I implemented the ADS1114, I purchased the ADS1115 EVM (including PAMB board). I created a breadboard to interface to the ADS1115 AIN. I used the GUI to verify all of this before I committed the design to my schematic. The process worked well. What I want to do now is remove the ADS1115 EVM from the PAMB baseboard and cable the PAMB 3.3V, GND, SCL, and SDA over to my board. However, I cannot 'connect' to my design, and I'm guessing it's because the ADS1115 EVM GUI is "looking for" the ADS1115 and not the ADS1114 that I have. Is there any way to use this GUI to connect to an ADS1114? That would be very useful.

Thanks,

Mark

  • 0
    TI__Mastermind 22950 points

    Hi Mark,

    The EVM daughter-card has an EEPROM that the GUI looks for when trying to connect. This is the reason why you are not able to connect to the GUI. Unfortunately, there is no easy way to 'trick' the GUI without the daughter-card present. In order to try and use the GUI, what you can do is still have the daughter-card present but remove the ADS1115 and fly-wire over the communication lines over from your board to the daughter-card. 

    This should do the trick. 

    Regards,

    Aaron Estrada

  • 0 in reply to Aaron Estrada
    Prodigy 120 points

    Hi Aaron,

    Thanks for your reply. So basically the GUI needs to see the EEPROM to connect. Got it. Actually, I think what I can do is I can remove the jumper from JP1 in the ADS1115V2EVM-PDK -- this will power DOWN the ADC, but keep the EEPROM alive. Then sky-wire in MY adc board.

  • 0 in reply to Mark Spring
    Prodigy 120 points

    Hi Aaron,

    I tried what I proposed above, but it didn't work. Not sure why. Since powering down the ADS1115 on the daughterboard should be the same as removing it, I don't want to even try removing it, because if that doesn't work then I have nothing operational. Are there any other 'tricks' to try? Seems like the PAMB was designed to have users place there own daughterboard on it, because the customer isn't told what, exactly, the GUI is looking for in order for it to deem a target to be "connected."

    Regards,

    Mark

  • 0 in reply to Mark Spring
    TI__Mastermind 22950 points

    Hi Mark,

    Is the main issue still that the GUI is not detecting hardware? Looking at the EVM schematic, there are a couple of things I would like to check.

    • What parts of your board are you connecting to the EVM. You want to make sure that:
      • The I2C address of your ADS1114 is the same as the ADS1115 on the EVM (Pulled LOW)
      • Be mindful of the supply voltage. Are you using 3.3V or 5V? I believe the PAMB board uses 3.3V for digital communication.
    • Do you have a diagram of your connections and/or a schematic of your board to share?

    Regards,
    Aaron Estrada

  • 0 in reply to Aaron Estrada
    Prodigy 120 points

    Hi Aaron,

    Well shoot -- I have the ADS1113 ADDR pin tied to VDD. I see on the ADS1115 EVM that it's tied to GND -- although there IS an option to resistor strap it to VDD instead. That would lead me to believe that the EVM supports both settings, but perhaps not. Does the ADDR have to be strapped to GND for the GUI to find the ADC? 

    Thanks for your help.

    Regards,
    Mark

  • 0 in reply to Mark Spring
    TI__Mastermind 22950 points

    Hi Mark,

    Let me confirm. I did not take part in the GUI development so let me see if I can track down some other potential causes. 

    Regards,
    Aaron

  • 0 in reply to Aaron Estrada
    TI__Mastermind 22950 points

    Hi Mark,

    Any luck? I did some digging and the GUI will only support one I2C address (0x48). So if the GUI is able to recognize the hardware but you cannot read/write to the DUT, then it is likely the I2C address. If you are still unable to detect the hardware with the GUI then there may be an underlying issue. 

    Regards,
    Aaron Estrada

  • 0 in reply to Aaron Estrada
    Prodigy 120 points

    Hi Aaron,

    No, no luck. The GUI simply says "No EVM detected."

    Regards,

    Mark

  • 0 in reply to Mark Spring
    TI__Mastermind 22950 points

    Hi Mark,

    Interesting. Although the address is fixed for the EVM ADC, this shouldn't affect the EEPROM. Can you verify that power is getting to the EEPROM by probing with a DMM? By removing the jumper on JP1, are you able to connect to the GUI with your board disconnected? Again, if you can provide any schematic of your board and/or how you are connecting to the EVM, that would be very helpful. 

    Regards,

    Aaron

  • 0 in reply to Aaron Estrada
    Prodigy 120 points

    Hi Aaron,

    Thanks for continue to dig into this. I realized something this morning. I'm using a "I2C to differential" converter pair to extend the length of my I2C bus across several meters of cable. As such, I cannot run the I2C faster than 100 kHz. The TI ADS1115 EVM GUI uses 400 kHz I2C. Is there a way to turn down the I2C bus speed? (I didn't see anything in the GUI.) Setup pic below.

    Regards,
    Mark

  • 0 in reply to Mark Spring
    TI__Mastermind 22950 points

    Hi Mark, 

    No problem!

    I am afraid the I2C bus speed is fixed as well. Can you reduce the length of the cabling and increase the I2C bus speed just to check to see if this resolved your communication issue?

    Regards,
    Aaron