• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 48 subscribers
  • Views 808 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.

ADS131A04: ADS131A04 ISSUE ----Very urgency！

Eric Long1
Prodigy 20 points
Part Number: ADS131A04

Dear Sir

We used TI device ADS131A04, some issue be found.

The SCH and the detail information  as the attachment. 

This is an urgent case, could you please help to give us some advice?

Many thanks!

ADS131A04 ISSUE IFOMATION.docx  

  • 0
    TI__Guru**** 176671 points
    Hi Eric,

    Welcome to our e2e Forum! Thank you for posting your schematic and descriptive document of the setup you are using with the ADS131A04. If you can also post a screen capture from an oscilloscope showing the SPI transfer, that would be helpful.

    Today is a holiday in the US ahead of Easter Sunday. Our support staff will be in touch with you early next week when they return from the spring break.
  • 0
    TI__Guru* 95225 points
    Eric,



    In general, I think you have the communication working. The writes to the register seem to be interpreted correctly by the device and appear as reads in the next response. However, the resulting 0x2204 indicates a flag that has been set in the STATUS register. This flag indicates an reset signal path coming from a /DRDY synchronization event. Because you're using the synchonous slave mode, /DRDY is an input signal that must be pulsed at the device data rate.

    In general, I would have used this device as asynchronous interrupt mode, using /DRDY as an output from the device to indicate when to read data. If this was your intention make the change to the M0 setting and check the result. If this was not what you intended let me know how you have /DRDY set up and we can discuss it further.



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

    Hi Joseph,

    I want to join the issue to talk about the question,the intension of above  schematic is using synchronous slave mode,so we want to fix the problem in synchronous slave mode.In datasheet page45 introduce the usage of  /DRDY signal,just tied /cs to /drdy is ok.Actually,we do this based the suggestion. Now,I don't know why the device response 0x2204.Can you help me,Thanks!

  • 0 in reply to Joseph Wu
    Prodigy 20 points

    Hi,Joseph

    I changed the device as asynchronous interrupt mode today,now the device is working.I don't know whether the device issurportting synchnorous slave  mode.However,now the device is working.Thanks your suggestion.

    Neio FAN 

  • 0 in reply to user6005263
    TI__Guru* 95225 points
    Neio,


    I'm glad that you were able to get the device working.

    For the synchronous slave mode, you need to send the /DRDY as an input to the device synchronous to the data rate. The 0x2204 status indicated that the /DRDY was received at the wrong time, which set the F_RESYNC flag. Normally you would use a device in synchronous slave mode run by another device set in the synchronous master mode. This way the devices share the same clock, and the master can give the slave the correct timing.

    However, with a microcontroller as the master, slave must still receive the /DRDY and /CS at the correct time. Without another device as master, this must be done exactly at the data rate, master and the slave are not synchronous. For that to happen, the slave must count clocks and keep track of all timing so that the slave is still synchronous.

    Again, I'm glad that you were able to get the device working in asynchronous interrupt mode.



    Joseph Wu