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.

TMS470MF06607: None

Part Number: TMS470MF06607
Other Parts Discussed in Thread: UNIFLASH,

Tool/software:

Hi,

  UniFlash reported a failure when using the XDS100V3 program.

  [ERROR] CortexM3_0: File Loader: Memory write failed: Timed out waiting for target to halt while execyting wr_pll.alg.

  Normal power supply.

  What might cause this peoblem.

  • Hi,

      Which Uniflash version did you use?

  • UniFlash 8.5.0

  • Hi,

    A few suggestions:

    1. In UniFlash, can you turn on Verbose in the console and try loading the image again, and see what console output you get?

    2. Can you see if standalone Erase works? "Settings & Utilities" -> "Erase Flash"

    3. Try turning on "System Reset on Connect" checkbox and see if it helps.

    4. Do you have more than one TMS470MF06607 board? It might be good to see if you can determine if it is a board specific issue.

    Thanks,

    Ricky

  • Hi,

    This chip cannot erase. 

    Uniflash keep reporting this error.

    We found the same problem on five of the 13 boards.

    Could you please help us to identify what causes this phenomenon.

    Thank you!

  • Thanks for providing the additional information. We will review and provide an update soon.

  • We found the same problem on five of the 13 boards.

    Hi,

      Can you confirm that using the same Uniflash version, you can successfully program and erase the other eight boards? If only five boards have the problem, can you please do a ABA swap test? The ABA swap test will verify if the issue traces to the the MCU or other components on the board. 

    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 faliure 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.

  • Hi,

      We have finished the A-B-A Swap test.

      The results show that the MCU on the original failing board is broken.

      How do we go to the next step?

    Thanks.

  • Hi,

      Please confirm the number of failures.

      Please tell us where did you purchase the devices from. Did you purchase directly from TI or through a legitimate TI authorized distributor?

      The next step would be for you to return the device for analysis if you confirm that the failure is due to the MCU. You can contact your local TI representative or you visit this TI customer return website for instructions on how to return the parts. https://www.ti.com/support-quality/additional-information/customer-returns.html