Under what conditions will the MPC5644 flash be damaged?

[ZEROOO]

Hi

  When the Lauterbach debug is used for two MPC5644 microcontroller, it will be disconnected from Lauterbach when running to a certain address.The ABA test excluded the influence of the rest of the board hardware, and confirmed that the fault is the MCU itself.Therefore, it is suspected to be related to the damage of MCU flash. I would like to ask under what circumstances flash damage will occur, such as some abnormal operations.

Best regards

Qi

[davidtosenovjan]

Is the issue being solved by re-flashing of software or not? Please provide details.

[ZEROOO]

Hi

    re-flash has been tried, but the emulator cannot be connected. Judging from the can message receiving, the program is running all the time.

[davidtosenovjan]

It means there is no issue issue with the flash. If you cannot connect it may be for instance due to that access is protected by password (censorship). Is it possible it is the case?

[ZEROOO]

We did not set a password. The original fault phenomenon was that the program would stop itself after running for a while, and it might resume running after being powered on and off again. Therefore, we wanted to use Lauterbach debugging to check the problem, but Lauterbach debugging would automatically disconnect when running to a certain address.

[davidtosenovjan]

I see. It would be needed to analyze what instructions causing the issue does. Typically manipulating with clock setting (for instance setting fvco out of tolerance, ..) may cause such issue. It is suitable to have enabled proper exceptions system responses.

This device required also proper wait-state setting for SRAM. Pay attention to base example code below:

https://community.nxp.com/t5/MPC5xxx-Knowledge-Base/Example-XPC564AKIT-PinToggleStationery-CW210/ta-...

[ZEROOO]

Hi

    At the beginning, it was found that the final disconnection location was in the peripheral chip initialization process during the inspection with Lauterbach. Later, ABA verification ruled out the problem of other hardware on the board. However, the board with the replacement of the faulty MCU could no longer connect to Lauterbach, so it was suspected that it was related to MCU.

[davidtosenovjan]

It is not clear to me how ABA test can rule out board issue when new MCU device with this board does not work.

You can also have issue with both sides, board and MCU. That's hard to say.