S12XEQ512 eeeprom hangs

[MichalPolrola]

Hi all,

I've issue in some devices that log data using EEEPROM. After several months it stops flushing data to EEEPROM that is enabled during start without any errors (query returns no dead secors, 4 sectors ready, ECOUNT = 306) . But after writing data to EEE RAM ETAG register never goes to zero. Then loop waiting for ETAG == 0 never ends. Error registers are zero...

Re-format of DFLASH solve this issue but how to investigate cause? ECOUNT is far below the limit. 

Mask set 0M12S

[lama]

Hi,

Before E/W EEEPROM it should not be any problem with changing EEPROM clock. The problem can be caused if there is any E/W from any reason.

The main issue I see you write it happens after few months so the lab tests are not easy to perform.

The easiest way how to point to the issue is to create an test code which will only use EEEPROM. Some code examples can be found here…

https://community.nxp.com/t5/S12-MagniV-Microcontrollers/LAMA-s-S12XE-unofficial-examples/ta-p/11007...

(XEP100 is a master device of the family … memory map attached)

If it works correctly then the issue can be in the application code and I can not imagine how to find the solution except code minimizing till it start works without issue and the think about next steps what they cause.

If the test code fails then the only way is to perform warranty return to the official distributor where you bought the device.

Moreover, i would also look at the errata list for used mask set of the device whether everything is served.

S12XE MCUs|16-Bit Microcontroller | NXP Semiconductors

... go to documentation and select errata ...

Best regards,

Ladislav

[MichalPolrola]

I've found in the meantime, some of these devices had software that incorrectly set flash frequency for a while. Software starting sequence was: correc setting - incorrect - correct again - eeeprom enabled. May that cause error that cannot be fixed, even if software was fixed? I've fixed this bug in software and applied to devices that had issue but existing eeeprom errors wasn't fixed. 

regards

Michal

[lama]

Hi,

It is really hard to answer. The issue can be in anything and I am afraid you will have to use simplification method to find where the issue is. (expluding application features)

There are some hints in my mind to share:

- Wrong flash frequency set

- The behavior can only be a symptom of another issue .... for example accidentaly disabled emulation of the EEE.

- There could be an application problem od EEE usage ...

https://www.nxp.com/docs/en/application-note/AN3490.pdf

I have discussed he issue with my colleagues and we see no problem which should cause this issue if the EEE is correctly used. So, if you are sure that the code is absolutely OK then the last solution is warranty return to the official distributor where you bought the device.

We could imagine the issue during debugging when you read while write (or you have currently written DFLASH in the memory window of the debugger)

Of course the same can happen in the application if you accidentally read the DFLASH which is currently E/W but this needs deeper investigation.

Best regards,

Ladislav