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.

ADC122S021: Extra tracking pulse before data readout

Part Number: ADC122S021

ADC122S021_fail.pdf

With a new lot of produced PCBs we see a failure with the ADC122S021, which previous were working OK (same PCB, same SW).

As can be seen on attached file, an extra tracking pulse is required, which gives an offset in the reading of data. However, if the temperature of the ADC122S021 is increased (not much with a heatgun) the failure dissapears. Also adding some capacity to the SCLK seems to have a positive effect. I have studied the timing and cannot find any obvious reason. Is any reason/solution known for this problem? Thanks.

  • Hello,

    It seems that the attachment did not go through correctly. Would you please try again using the icons/selection tools provided through the text box.

    You have confirmed that timing, PCB layout, and software haves all remained the same from previous build to this build?

    I am not sure what you mean by "tracking pulse" but from your comment it sounds to be an extra pulse appears in the DOUT data?

    please include a scope shot of the extra pulse in the attachments

    Regards

    Cynthia

  • Hi Cynthia

    Thanks for your reply. I will try to do the attachment once more, -æ now both as PDF and PPT.

    Yes, it is same software and same PCB version. I have searched for other wrong/failing components, but without luck.

    Neither I cannot see, which of these should be able to make this fail, then the signals and their integrity seem OK.

    According to the datasheet the first 3 clk cycles (after CS) are the tracking mode (SCLK is low by CS-start and therfore directly into trackmode).

    MSB is clocked out on the 4th clock, as shown in the top figure of the attacment, which is what I will consider as the correct case. 

    However, in the "cold case" (room temperature) the MSB is first present on the 5th clock, which gives an offset in the reading of the frame. 

    Hope this made the issue more clear.

    /CarstenADC_fail.pptx0310.ADC122S021_fail.pdf

  • Thanks Carsten,

    The scope shots are very helpful. It does look like the SDO is shifted over one clock pulse.

    Let's start by eliminating the new boards/set up

    Can you remove the failing device from the new boards to a board from an older build that had not shown any failures? If the fail follows the device then we have eliminated the new build.

    After that, we can start debugging it.

    It seems that this is only affecting the first conversion after CS falling edge. From the scope shot, the second conversion result seemed correct. Is this correct? I would like to use an input at max positive scale. This will clearly show when the SDO line is outputting zeros and valid SDO data.

    I have some general questions. How many devices are failing? Does temperature have a big effect? For example, do you see it at colder temperatures, and does it get worse?

    Regards

    Cynthia

  • ADCs_read_OK.pdfADCs_read_fail.pdfIsolator_difference.pdf

    Hi Cynthia

    As suggested I tried to exchange the ADC between two failing- and two OK-boards. The fail follow the boards. You can see how the readings are affected on attached plot. Then I tried to derive more information from the timing and saw a difference in the CE signal falltime (app 2us=working, 5us=bad). Then I tried to exchange the driver (opto-isolator) and that made the OK board bad and vice versa. So that must be the root course. Now I need to figure out why the CTR apparently has gone so low for this device, but for that I cannot blame the ADCs. However, in the ADC spec there is no limit for the CE-falltime, but only to the "deadtime" surrounding this. Is it correct? Anyway, thanks for the effort you have put into this case.

    /Carsten

  • So glad to hear Carsten, that you are getting closer and closer to fixing the issue.

    As for the ADC timing, there might not be a fall time requirement for CS, but with the unexpected delay in CS falling, this could be violating other timing requirement. The CS is not clocked at low until it is at 0.8V, before you were expecting this to happen ~3us before it actually is doing it. This than can propagate  and affect other timing requirements that were not thought as issues before.

    Of course, if you need anymore help we are here

    Regards

    Cynthia

  • Thanks Cynthia. I will concentrate on the Isolator and close down this ADC case for now.... /Carsten