• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 47 subscribers
  • Views 133 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.

ADS8686S: ADC868S busy high issue

Shravani N
Prodigy 10 points
Part Number: ADS8686S

Tool/software:

Hi,

I'm using ADC ADS8686s in my design.

I was trying to read data using ADC. But as soon as I enable convert start signal, busy signal is being high. It is never coming to zero after that command.

Can you please help me in resolving this issue.

One more thing is, when I'm trying to read register default values I'm receiving register content in return. But Register address is not being displayed. Please give your comments on this also.

  • 0
    TI__Guru**** 180961 points

    Hi Shravani,

    Welcome to our e2e forum!  Can we start with you providing some detail about how you are using the ADS8686S?  Are you using hardware or software control?  Serial or parallel interface?  Can you provide a schematic and a timing capture from oscilloscope or logic analyzer?

  • 0 in reply to Tom Hendrick
    Prodigy 10 points

    Hi,
    I'm using software control. Serial single wire mode.
    Hardware design side, all the things captured according to the datasheet.
    Software side, I have set SPI mode as polarity 1 and phase 0. Then only I could get register default contents except register address.
    Please clarify whether we will get only data or data with register address also in register read operation.
    And whenever I issue a convert start pulse I'm not seeing busy behavior as expected.

  • 0 in reply to Shravani N
    TI__Guru**** 180961 points

    Can you please provide a timing screen capture and schematic?  

  • 0
    Prodigy 20 points

    I had the same issue that BUSY went high after a CONVST pulse and stayed high forever.

    In my case, this was caused by an incorrect interface timing (the delay between CSN rising edge to CONVST rising edge was less than the value required by the data sheet: 50 ns).

    I guess that BUSY staying high indicates a digital interface timing error.