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.

DRV8872-Q1: DRV8872DDARQ1

Part Number: DRV8872-Q1
Other Parts Discussed in Thread: DRV8872

MPN: DRV8872DDARQ1

failure rate: 1.4%

. Board level failure mode板级的失效模式:

Failure mode 1: When MCU setting logic inputs signal IN1=1 and IN2=0, the motor can’t driver forward running, and output port OUT1 is low level respect to GND, but to drive reverse running is ok.

Failure mode 2: When MCU setting logic inputs signal IN1=0 and IN2=1, the motor can’t driver reverse running, and output port OUT2 is low level respect to GND. but to drive forward running is ok.

Failure mode 3: driving motor to forward or reverse is failed while setting logic input signal IN1=1 and IN2=0 or IN1=0 and IN2=1.

 

  1. Customer testing methods/conditions (applied V/I, temperature, etc.)

(Please specify at which step the units failed and the corresponding testing conditions)

客户测试条件或方法(请指出失效是发生在测试的哪一步骤,以及当时的测试条件):

Set DC input voltage to DC27V, OUT1 and OUT2 of DRV8872 are connected to DC 24V Motor during testing. Then to toggle the forward and reverse signal separately, the MCU’s two I/O ports will set related logic inputs signal level to IN1 and IN2 of DRV8872 within15sec for DC motor forward and reverse. However the DC motor can’t normal operated.

 

  1. Customer diagnosis procedure(including swap test) 客户诊断的过程(包括交叉验证)
  • Check input signal and output voltage, For some defective products, while Pin3_IN1 / Pin2_IN2 input signal IN1=0 / IN2=1, but Pin6_OUT1 is not Low / Pin8_OUT2 is not high; For some defective products, while Pin3_IN1 / Pin2_IN2 input signal IN1=1 / IN2=0, but  Pin6_OUT1 is not high / Pin8_OUT2 is not high;
  • After replacing DRV8872, the product work normal.
    1. TI device level failure mode芯片级别的失效模式
  • Please specify:

    1. which function cannot meet TI datasheet or which pins have the abnormal behavior
    2. Customer testing limits
    3. Customer measured value (failed vs. good), if waveform is appreciated.

    请定位出哪个功能/参数/引脚不符合TI规格书,提供相应的客户测试规范和好坏样品的测试数值(波形)对比

    Pin6_OUT1 / Pin8_OUT2 output does not meet datasheet chapter 7.3.1 Bridge control.

     TI device level failure mode芯片级别的失效模式

    Please specify:

    1. which function cannot meet TI datasheet or which pins have the abnormal behavior
    2. Customer testing limits
    3. Customer measured value (failed vs. good), if waveform is appreciated.

    请定位出哪个功能/参数/引脚不符合TI规格书,提供相应的客户测试规范和好坏样品的测试数值(波形)对比

    Pin6_OUT1 / Pin8_OUT2 output does not meet datasheet chapter 7.3.1 Bridge control.

    1. Schematics 客户的电路原理图

      1. TI device level failure mode芯片级别的失效模式

      Please specify:

      1. which function cannot meet TI datasheet or which pins have the abnormal behavior
      2. Customer testing limits
      3. Customer measured value (failed vs. good), if waveform is appreciated.

      请定位出哪个功能/参数/引脚不符合TI规格书,提供相应的客户测试规范和好坏样品的测试数值(波形)对比

      Pin6_OUT1 / Pin8_OUT2 output does not meet datasheet chapter 7.3.1 Bridge control.

       

      1. Failure history review 失效历史回顾:

      For this failure mode, please provide the failure rate(failed qty/production qty) of this device in recent six months on customer’s production line请提供近6个月客户生产线同一问题的失效率(失效数量/生产总数量)

      Recently we have produced total 34,000pcswe and no find this kind of issues, but for this batch total 3888pcs, we found the defective, and the failure rate to up to 1.4%

       

       

     

  • Hi,

    Thank you for your question. This E2E is intended to technical support for functionality. According to your post, it is 1.4% failure analysis request.  Please refer this link and follow the instructions.

    https://www.ti.com/support-quality/additional-information/customer-returns.html

    regards

    Shinya Morita

  • hi Shinya,

    we have submitted this request to the link you provided before and was sugested to contact E2E expert to resolve this issue.

    would you help to review the situation posted and advise if it's sth related to application issue and how CTM can fix it?

    thank you!

  • Hi ,

    Thank you for your question. If DRV works fine before and turned to failure, DRV could be damaged. Was DRV working correctly before?

    If DRV does not work from the begging, I recommend to check nFAULT signal. Please add pull up resister externally to ~3.3V like bellow.

     

    After VM supply (IN1=IN2=0v), nFAULT pin should be ~3.3V.  If nFAULT goes low after IN1 or IN2 = 1, some fault condition should be detected then motor does not spin. Please refer datasheet 7.3.5 protection circuit for debug.

    I recommend to check VM voltage stability. You may need external cap ~47uF +0.1uF as above example shown.

    If DRV works fine before but turned to failure, DRV could be damaged. 

    -May overstress situation happens. I suggest to check VM voltage does not have hick up while motor starting/spining/stopping.

    -Please make sure thermal pad connected to GND plane though the thermal via. 

     

    regards

    Shinya Morita

  • Dear Shinya,

    pls help to check feedback from end user and advise how should we resolve this issue, thank you!

    Thank you for your question. If DRV works fine before and turned to failure, DRV could be damaged. Was DRV working correctly before?

    If DRV does not work from the begging, I recommend to check nFAULT signal. Please add pull up resister externally to ~3.3V like bellow.

    DSZ-Answer: the DRV8872 does not work from the begging. In fact, MCU power supply voltage is +5.0V, there is having a pull-up resister(10kohm) to +5.0V on the nFAULT pin, and then nFAULT pin connect to I/O pin of MCU via a serial resistor of 1kohm, to measure the nFAULT pin, it is always is a high-level (+5V).

     <![if !vml]><![endif]>

    After VM supply (IN1=IN2=0v), nFAULT pin should be ~3.3V.  If nFAULT goes low after IN1 or IN2 = 1, some fault condition should be detected then motor does not spin. Please refer datasheet 7.3.5 protection circuit for debug.

    DSZ-Answer: actually, nFAULT pin is always high-level after VM supply (IN1=IN2=0V), so no any system fault occurs.

     

    I recommend to check VM voltage stability. You may need external cap ~47uF +0.1uF as above example shown.

    DSZ-Answer: an aluminum electrolytic capacitor 100uF + MLCC capacitor 100nF have been put to pin5/VW of DRV8872 for our application.

     

    If DRV works fine before but turned to failure, DRV could be damaged. 

    DSZ-Answer: we suspect that DRV8872 could be failure at internal control logic unit or gate driver. It needs to further analysis by TI.

     

    -May overstress situation happens. I suggest to check VM voltage does not have hick up while motor starting/spining/stopping.

    DSZ-Answer: we have used the DC power supply for EOL testing. the max. tested voltage of 36V apply to DRV8872_VW pin during performing over-voltage protection function test. However, according to the datasheet of DRV8872, the allowed max. power supply voltage is up to 45V.

     

    -Please make sure thermal pad connected to GND plane though the thermal via.

    DSZ-Answer: the thermal pad has connected to board ground for good thermal dissipation.

  • Hi,

    Thank you for your feedback/question. I will reply to this within a few days.

    regards

    Shinya Morita

  • Hi,

    I have reviewed your feedback. 

    >>the DRV8872 does not work from the begging.

    I think this is important information. So you meant the failure units have on of 3 failure mode from the beginning? Did customer tried ABA swap?

    After ABA swap, if failure follows IC, again I recommend to follow this link instruction. Then you can share ABA swap result. Failure analysis is not supported by E2E. 

    Please refer this link and follow the instructions.

    https://www.ti.com/support-quality/additional-information/customer-returns.html

    After ABA swap, if issue does not follow to IC, this could be caused by not IC, something else.

    regards

    Shinya Morita

  • Leeya,

    Did this get resolved?

    Regards,

    Ryan