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.

TMS320F28069: servo drive crashed

Part Number: TMS320F28069


dear

The servo drive crashed after working for some time.

We did some testing on the one we received and found that it seems to be related to unstable Flash working

If the program uses ABCDEFGH these 8 blocks, that is, the program is greater than 112K words, the CPU temperature is greater than 50 degrees, it will crash

If the program only uses the 7 blocks of ABCDEFG, that is, the program is less than 112K words, greater than 96K words, CPU temperature greater than 105 degrees will crash;

If the program only uses ABCDEF these 6 blocks, that is, the program is less than 96K words, CPU temperature is greater than 125 degrees are normal.

any advice?thanks in advance

 

 

  • Raymond,

    Thanks for reaching out to the E2E.  Based on your description I think we may want to initiate a return for failure analysis by TI.  This can be useful in determining if the device is still performing within specification, and if not the failure reason.

    Before we start this process, can you confirm that if you replace the F28069 on the return system with a new F28069 that the failure goes away, that is the PCB has no issue?  Also could you transfer the F28069 from the bad system to a known good PCB/system and confirm that the failure stays with the MCU?

    Once we have determined that it is the MCU at fault we can begin the return process.

    Best,

    Matthew

  • hi matthew pate

    ABA test and failure analysis by TI is good solution ,but the chip is encrypted and does not allow the aspect to do the testing by TI,any advice ?thanks in advance

  • Raymond,

    Understand your comment.  I would still suggest ABA in order to make sure the C2000 is faulting.  I had misunderstood  your org post regarding the temperature, I thought you were saying that the device was self heating when more flash sectors are used.  I understand now that you are saying with decreasing sectors the drive is able to operate at higher and higher temperatures.

    In terms of some more local debug; you could try and view or scanout the flash contents after raising the temperature to see if the flash in the correct state when the failure occurs or if that is the problem with rising temperature.

    Do you have any comment on how the failure presents itself in the system when it happens?  Does the C2000 go into Reset, or cause a wrong behavior in the servo drive(i.e. bad code execution).

    Also it might be helpful to understand the temp profile/power on hours the device was exposed to before failing.  How often is the flash reprogrammed, etc.

    Best,

    Matthew