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.

66AK2G12: Problem in high temperature operation

Genius 3215 points

Part Number: 66AK2G12

Tool/software:

Hi All,

A defect occurred in the MPU of 1 product after mass production.
・The current consumption of the 1.0 V power supply is high and the heat is high.
Normal MPU: Approx. 5 mA/°C
Problem MPU: Approx. 20 mA/°C
・When a problem occurs, CPU autonomous reset and restart are repeated.
・Ambient temperature In an environment of 50°C, the surface temperature
becomes approx. 90~96°C, which is 15~20°C higher than that of a normal MPU.
・There is no problem with current consumption other than the 1.0 V power supply.
・A cross-check was performed, and the problem was reproduced.
->It was confirmed that there was a problem with the MPU.
・The same problem occurred 3 times in 2024.
Lot number of the problem in 2024: 18P0HEQ
Lot number of the problem in 2025: 18P0ECQ

[Question]
・Has this kind of problem ever occurred?
・Has errata or other measures been taken?
・Please give us your opinion on the cause and countermeasures.

Best Regards,

Ito

  • Ito

    I checked internally and there are no indications of an issue. 

    The suggestion is to check for shorts on pins related to the high draw rail. 

    --Paul 

  • Hi Paul,

    Thank you for your reply.

    When I put a normal IC on the board where the problem occurred, the problem disappeared.
    In other words, as a result of cross-checking, I found that it was caused by the IC.
    I am having trouble finding the problem.
    Is there any way to find the problem other than looking for a short in the 1V line?
    After trying that method, there is no problem if it fails.
    If you accept the private message, I will send you the power tree.

    Best Regards,

    Ito

  • Hi Paul,

    Could you please approve my friend request so that I can send you a private message?

    I have an important announcement for you.

    Best Regards,

    Ito

  • I have not seen a friend request 

  • Hi Paul,

    Did you receive the message I sent?

    My client is inquiring about the progress.

    I've sent you a friend request, but it seems it hasn't reached you.

    Best Regards,

    Ito

  • Ito

    Apologies for the delay. 

    Do you still have the NG1-3 devices? 

    The suggestion is to return at least the NG4 device to Texas Instruments.   You can do this via this web page: 

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

    I've also included others on this E2E So they can provide input as needed. 

    --Paul 

  • Hi All,

    We have already requested the return of NG1-4 to the Japan TI Quality Team, but our request was declined.
    Please share your thoughts on the contents written in the PDF.
    At the very least, let us know whether this is a defect or not.
    If it is a defect, please provide a countermeasure.
    Based on your reaction, we suspect this might be an unexpected behavior.
    If it is difficult to respond here, we have also sent an email, so please reply to that instead.

    Best Regards,

    Ito

  • Hi Paul,

    I'm waiting for your opinion.
    I understand that TI cannot determine this issue to be a defect at this time.
    Therefore, I would like you to propose a method for us to resolve this issue.
    If you tell me there is no solution, we can propose a new device or take the next action.
    Since this support is currently pending, I simply need information at this time.

    Best Regards,

    Ito

  • Hi Ito-san,

    Can you share details on why the return request was denied by the TI Japan Field Quality team?  Can you also share who the TI contact was that you communicated with?  Please feel free to share this information with either me or Paul over private message.

    Thanks,
    Mike

  • Hi Mike,

    I sent it to your private messages.

    Best Regards,

    Ito

  • Discussion was moved to private messages and addressed there.