• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 46 subscribers
  • Views 223 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.

Original question:

ADS131E06: Compare to MCP3913

ADS131E06: Register write failure

Jeff Xie
Intellectual 1780 points
Part Number: ADS131E06

Customer meet ADS131E06 issue. They report they met ADS131E06 register write failure issue, failure rate 20%.

If the configuration of ADS131E06 fails, it will not follow ADS131E06, nor will it follow MCU. This is random. If they configure it several times (dozens of times to more than a hundred times), it will succeed.

The software and hardware have not been modified.

  • 0
    TI__Guru* 97585 points

    Jeff,


    To help debug this, I'll need a lot more information. I don't know of any write issues with this device, so the problems that you're describing could be something associated problems with the SPI or some sort of reset is going on.

    Can you give me all the information that you can about how they test this? Are they writing to the device and then reading back the register? Do they read back the all registers to see that all the registers are as they expect? When they have problems are the registers set to random values? Are they set to something close to the expected write? Or have they reverted back to the default values?

    Again, this could be a problem with the SPI communication so there will be a lot to look at. I would have them check all the SPI timing (and compare it against the timing shown in the datasheet). I would also have them look at the SPI with an oscilloscope to verify the communication and see that there isn't noise on the lines. If the register values are returning to default values, I would also check to see if a reset isn't accidentally sent. Also, I would check to see if the power supply and ground is clean, and there haven't been any glitches or brownout conditions.

    Go through my comments, check with the customer, and post back.


    Joseph Wu

  • 0 in reply to Joseph Wu
    TI__Guru* 97585 points

    Jeff,

    It's been a while since you wrote this post, and I wanted to check to see if you have gotten further along on this. In my last post, I did give some suggestions about the SPI communication and asked for a bit more information.

    Hopefully, this problem has been solved. I'll close this post for now, but if this problem needs more attention, post back and we can continue working on this.

    Joseph Wu

  • 0 in reply to Joseph Wu
    TI__Intellectual 1780 points

    Hi Joseph,

    Customer has found the root cause and is not related to our ADC, thanks.