ARM-CGT: SFO Supplier Log Failure Analysis no:SFOEI2413151- Item-242280004092>MOUSER ELECTRONICS INC // SO #273900

Hi TI Team,

We require your support in conducting a Failure Analysis for the reported IC as it is not functioning well during our analysis. Pl expedite and share your feedback asap.

Regards

Yamuna

Hi Christian Espinoza,

We had purchased the part from Authorised Distributor- Mouser Electronics.

Regards

Yamuna

Alphonsa P K said:

At the customer that had reported with issue of Position tracking not working & showing 0 values for all movements. During their analysis the board was installed externally & system was restarted 5 times out of which it was in error state on 3 occasions thus confirming that issue is in the Motion Control Board.

 

We have tested the units in our test setup and failed (COM not detected). This is expected as the board is loaded with the final production bootloader. Then we erased the unit, loaded the testing bootloader then tried retesting. But still not detecting and the unit recognized as unknown COM6. This happens when the U13 (P/N#242280004092)  IC is not functioning properly.

Hi,

  Please elaborate what the issue is at MCU level and please understand for an outsider, I have no idea about your applications as to what the Motion Control Board is doing. Focus your problem description on the MCU.

Which MCU peripheral(s) are you using for position tracking?

Which UART are you using for COM port? 

Are you able to load a simple UART example and still see the COM port failure?

Have you done ABA swap test? This is identify if the problem is on the MCU or the board. What is the ABA swap test result?

The A-B-A Swap Method is a simple cross check test, which can confirm the observed issue is not systemic.

• A-B-A Swap Method
  (1) Remove the suspected component (A) from the original failing board.
  (2) Replace the suspected component (A) with a known good component (B) and check if the original board now works properly.
  (3) Mount the suspected component (A) to a known good board and see if the same failure occurs on the good board.

Step 3 is important because it helps us to exclude any possibility that the issue is caused by a systemic issue or the interaction of multiple slightly bad components on a good board.