TMS320F28377D: Flash can be accessed, but new firmware upload is failed.

Hi Garam,

When you are programming the memory, is there an address that is given at the failure point?

Since the device erases ok, what I would first check is the linker cmd file to make sure that the application is being programmed in the correct location. 

Thanks,

Charles

Thanks for reply. Charles.

This is more detailed debugging messages.

in that, address 0x90000(length:0x5a4), this part of memory is the problem during flash writing.

in On-Chip Flash, using the Range Avoidance Settings, we could download the FW to flash memory.

But, I wonder, why is that happening?

Hi Garam,

I will need some more time to look into this, will get back to you within the next day.

Thanks,

Charles

hi Chales,

we concluded that the board is broken.

but, from now on, we need the countermeasures to prevent the breakdown for mass production.

we need the causes of that problem.(broken flash memory, emulator is using the xds200 of syncworks)

what's the cause of that happening?. (guess?)

what's improvement points to prevent that?

if we can send the broken MCU to you, can we request the fault analysis?

what's the procedure for fault analysis?

thanks.

garam

Hi Garam,

Were you able to successfully program the flash on this device at least once in your board?  

Thanks and regards,
Vamsi

Hi Vamsi

Vamsi Gudivada said:

Were you able to successfully program the flash on this device at least once in your board?  

Yes, we used it normally and worked.

we tried several times flash writing.

also, recently, we found other one(breakdown board) by same symptom.

is static electricity likely to affect the fault?

we assume two causes.

one is the emulator(xds200 - manufactured by syncworks in south korea.) (or extended debug cable(50cm) )

other one is the static electricity?

is it possible?

fining causes is very important to us. 

thanks and regards.

garam

Hi Garam,

Static may cause this I think.  Let me check with the team and confirm.

Thanks and regards,

Vamsi

Garam,

          There are a few areas to check if flash programming fails: 

Is the power stage able to supply the needed current during Erase/program (EP)? If the device is current-starved during E/P, that may result in a failure. However, if Erase succeeds every time and only programming fails, this is unlikely to be the reason. You could probe the power-supply pins during E/P to check if the voltage dips or if there is excessive ringing. 

Is there any kind of interruption to the E/P process? This could potentially corrupt the password locations. 

If you move the “faulty” device to a known-good board, does the problem follow the device? 

If you use a different debug probe type (such as XDS110), does that make a difference? 

The 50cm cable length could indeed pose problems but I would expect those problems even during regular debug sessions, not during flash E/P alone. 

Electrostatic discharge (ESD) issues tend to cause random problems. Sometimes, the device is recoverable after a reset or power-cycling but sometimes the damage is permanent. Only a Physical Failure Analysis (PFA) can conclusively tell us. PFA is done only after all other debug avenues are exhausted