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.

TMS320F28062: Flash programming issue

Expert 2030 points
Part Number: TMS320F28062
Other Parts Discussed in Thread: UNIFLASH

Partnunber: TMS320F28062PZT

Programming tools: XDS100 V2

Problem: 

Mass produced, most of them without problem.

There are 10 defective products in total, 1~4 of which have abnormal DI status. 5~10 pieces cannot burn program.

Help me figure out what's going on, thsnks!

  • Can you clarify what is meant by DI status?  If you could also comment on what tool you are using to program the devices and the error it returns on the bad devices it will help us understand the issue more clearly.

    Best,

    Matthew

  • Reed,

                  The information you have provided is insufficient for meaningful debug. Please answer each one the following questions carefully:

    1. How long has this setup been used to program devices?
    2. How many devices have been programmed till date?
    3. In how many devices is this problem seen? What is the DPPM value?
    4. You have mentioned XDS100v2. Do you use CCS-flash tools plugin or UniFlash or some other method?
    5. On a failed device, are you able to connect it to CCS to examine the flash content?
    6. If so, are you able to determine the extent of flash corruption? For example, do you see a few bits flipped or a few words or few sectors?
    7. Are you able to reprogram the device?
    8. Have you looked into the possibility that the device may be current-starved during flash programming? (especially if the application is running)
    9. Have you looked at https://e2e.ti.com/support/microcontrollers/c2000/f/171/t/757585? 
    10. Did anything change in the programming hardware or software?
  • ,

    thsnks!

    Total units run : 50000
    Failure rate (ppm) : 200

    error info.

    The following is the video of burning error.

    The following is the video burned normally after replacing a new MCU.

  • Reed,

      You have not answered all the questions in my post. Without that information, we cannot proceed with the debug.

  • Thanks, I'll let the client try to join in the introduction.