TMS320F280041-Q1: can't connect device anymore via CCS debugger after using UniFlash to erase device and device reset during erasing.

Hi Will,

What do they see in the DCSM OTP memory?  If not the CCS, are they able to see the memory in the Uniflash?

Thanks and regards,

Vamsi

Hi Vamsi, 

I need to check these two question with customer, will update here later. 

BR, 

Will 

Hi Vamsi, 

Please check the following figs.

The DCSM OTP memory are also 0x0BAD and similar errors prompted in the console of CCS. 

As for the Uniflash memory read, the results are similar. 

Regards, 

Will 

Hi Will,

Can you confirm that the customer is able to view the memory contents fine before the failed erase operation?

Thanks and regards,
Vamsi

Hi Vamsi, 

Confirmed, they can view the memory contents fine before the failed erase operation. 

BR, 

Will 

Hi Will,

Thank you for the information.

If the voltage lines are with in the datasheet spec, and the memory reads are failing (which worked previously), then I would suggest to submit the device for FA.  However, the solution is to avoid the watchdog reset during the flash erase/program operations.

Thanks and regards,

Vamsi

Hi Vamsi, 

Understood. Since this device is failed at debug phase but not from customer field, I think we can skip FA. Could you tell me the the reason why all memory (including DSCM OTP region) read with 0x0BAD, from device principle/behavior perspective? A theoretical analysis can also close this issue and skip FA. 

BR, 

Will 

Hi Vamsi, 

From my understanding, only F05 Flash technology has this constrain? Please correct me if it is not right. 

Thanks and Regards,  

Will 

Hi Will,

F05 is more susceptible.  

Below is taken from F280049 datasheet:

Thanks and regards,
Vamsi