TMS570LS1114: EEPROM 2 sectors 7 lines cannot be erased

Hi Honle,

I checked on my board same address

I can see all 0xFF only, 

Can you give more details on how you were triggered this issue? Are you writing any data to this address using TI-FEE module?

If this happened with any code, then can you share your code?

--
Thanks & Regards,
Jagadish.

HI Honle,

Honle Zhao said:

At present, it is suspected that the internal hardware of the chip is faulty.

Understood.

Dears，

Does this faulty chip need to be sent to you for analysis？

Hi Honle,

QJ is on leave, lets discuss with QJ once regarding this. If QJ want me to analyze, then you can send me the board. QJ will be back on this wednesday.

--

Thanks & Regards,
Jagadish.

Dears， 

  After discussion with QJ, do you need to return the faulty chip for this problem?

Let me discuss with QJ and QJ will make decision. I will update status by the EoD.

--

Thanks & Regards,
Jagadish.

Hi Honle,

A small doubt,

can you please confirm whether the customer enabled below option or not in UNIFLASH

If this option not enabled, then entire flash will not get erased before programming the selected Hex file.

--

Thanks & Regards,
Jagadish.

Dears，
The item is enabled, but an error is still prompted when erasing. 2 Sector 7 lines cannot be erased.

Hi Honle,

Thanks for checking, i mailed to QJ and waiting for this feedback on this.

--

Thanks & Regards,
Jagadish.

Dears，

Thank you. I'll wait for your message.

Hi Honle,

Do you know how many units have this kind of issue? Does the PCB board have a steady VCCP flash pump power supply (3.3V) when erasing flash?

Dears，

At present, there is one case of this problem. The customer VCCP is terminated with a 100nf capacitor.

If further failure analysis is needed, please follow the TI formal RMA process.

Honle Zhao said:

The 7 lines in 2 sectors of EEPROM cannot be erased,

I am not very clear about "7 lines in 2 sectors".

From your snapshot, the issue happens in 3rd sector (0xF0208000~0xF020C000). I'd like to know if the issue happens every 0x80 bytes in 3rd sector (sector 2):

0xf020_8080~0xF020_8100

0xf020_8180~0xF020_8200

...

0xf020_9480~0xF020_9500

0xf020_9580~0xF020_9600

...

0xf020_BF80~0xF020_C000

Any issue in other sectors (sector 0, 1, and 3)?

Can you write data to locations of this flash sector (3rd sector) whose content is 0xFFFFFFFF? For example, write data to 0xF0209400.

Dears，

1.Sector 0,1,3 of the faulty component can be erased and written normally for many times.

2.Failed to erase sector 2 of the faulty component with Uniflash, as shown in the figure.

3.We write data according to the actual way of using this sector. We divide the sector into three parts:

（1）0XF020_8000~0XF020_9400 ,
（2）0XF020_9400-0xF020_A800,
（3）0XF020_A800-0XF020_C000。

Write in sector2 area: this sector (1) writes normally, (2) 0x0XF020_ 9400-0xf0209480 is normally written, but cannot be written after the fault data. (3) Write normally.

Erase sector2 area: (1) in this sector can be erased, (2) 0x0XF020_ 9400-0xf0209480 is normally erased, and fault data and subsequent data cannot be erased. (3) It cannot be erased.

When writing to the sector2 area again, the writing fails. According to the debugging information, it is found that "Fapi_getFsmStatus" returns a negative value.

We guess that the write failed because some areas to be written are not erased. Again, we only write data to the FFFFFFFF area, and the results are the same.

Thanks for your clarification and explanation. Can I know your customer name? I will check with PE team if further analysis is needed.

Dears，

MAA NAME:SIMCONTEC SHENYANG CORP

E-mail:he.meng@simcontec.com

Can I know the response time of you or your team on this question？

I will keep you updated.

Hi Honle,

Does TI-Shanghai or TI-Shenzhen have the tools for failure analysis? 

I submitted the FA application and was rejected, please help to advise

Dears，

I submitted two FA applications, which were rejected，please help to advise。

Similar situations have occurred several times during our use:

1. The FLAS area is damaged and the application program cannot run;

2. The EEPROM area is damaged, and the contents in the EEPROM cannot be erased.

We want to know what causes this problem, so that we can avoid the recurrence of this problem in the future.

Do you know why your request is rejected? Did you follow the official procedure? 

Please refer to the screenshot comments,The problem I'm facing is not a solution, it's not a solution,

The comments are correct: we never heard this kind of issue before. Did the EEPROM on this faulty device at the beginning? 

Dear QJ

         The customer has a problem with the product. How can you help the customer find the problem?TI cannot provide a solution now, nor can it assist FA,

Hi Honle,

Can you please check if the EEPROM on the faulty device had been erased and programmed successfully?  To be honest, I don't know the root cause so far. 

Honle Zhao said:

（1）0XF020_8000~0XF020_9400 ,
（2）0XF020_9400-0xF020_A800,
（3）0XF020_A800-0XF020_C000。

Write in sector2 area: this sector (1) writes normally, (2) 0x0XF020_ 9400-0xf0209480 is normally written, but cannot be written after the fault data. (3) Write normally.

Erase sector2 area: (1) in this sector can be erased, (2) 0x0XF020_ 9400-0xf0209480 is normally erased, and fault data and subsequent data cannot be erased. (3) It cannot be erased.

I'd like to know if the data below was written by customer. 

Dear QJ

This data was recorded by the application, when the vehicle broke down, but the writing logic was wrong, it was inconsistent with the requirements,

The problem now is that this part of the code can not be erased again, resulting in subsequent data cannot be written

Hi Honle,

I discussed with PE experts last week, and the electric analysis is recommended. Please check with local QA team how to file this request.