2401598_en-US

[#1]

Regarding the "MPC5777C-1b+2b_RAM_ECC_error_injection GHS614" example code

Hello. I am currently developing based on the MPC5777C MCU.

I have a question regarding the development process.

I designed code to perform ECC checks based on the "MPC5777C-1b+2b_RAM_ECC_error_injection GHS614" example code.

Under normal circumstances, this code performs the ECC checks correctly.

However, when running the ECC check code with a debugger like Trace32 connected to the MCU, errors often occur where bit errors are not detected.

Is it possible that the "GHS614" example code as a whole does not function correctly when connected to a debugger such as Trace32?

Thank you.

Re: Regarding the "MPC5777C-1b+2b_RAM_ECC_error_injection GHS614" example code

Hello.

Assuming the Trace32 debugger is connected and the dump window is open, and my custom application code is running, is it possible for a case to occur where a bit error is not detected within the ECC check function, which was designed referencing GHS614?

Re: Regarding the "MPC5777C-1b+2b_RAM_ECC_error_injection GHS614" example code

Hello,

I am not sure what your setup is, but have in mind that any open dump window in the Trace is constantly reading the memory and will rise the ECC fault immediately if detected.

ECC errors will never happen on the not corrupted address. As ECC mechanism is also guarded by EDC. Such is simply not possible.

Best regards,

Peter