This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TMS570LC4357: ESM1.12 ("FlexRay RAM - ECC uncorrectable error") sometimes set after FlexRay FTU MPU violation

Part Number: TMS570LC4357

Hello,

I'm doing some simple FTU diagnostic testing where I intentionally setup a transfer to be blocked by FTU memory protection. Basically I'm using the register sequence from SPNA145 to write a header to CC RAM and back, but I'm intentionally disallowing FTU CC access to the buffer sometimes and then verifying the memory protection violation is flagged.

Everything pretty much works as expected, except for one side effect. In about one out of every ten memory protection violations I trigger, I find ESM1 bit 12 ("FlexRay RAM - ECC uncorrectable error") unexpectedly set (this is in addition to ESM1 bit 16 becoming set as expected). All of the other status bits (e.g. MPV) look fine, PEADR is zero, ECCDSTAT is zero. So I'm confused at what's happening here and I'm wondering if a false ECC error is being flagged somehow during memory protection violation. Are there any known issues here?

  • Hi,

    Thanks for your post. Due to the Easter Holiday in the US, we will not be able to get back to you until early next week. We're sorry for the delay.
  • I'm still struggling with this. Note that the ESM error is signaled despite GCS.PEL = 0. How is that possible? "Figure 26-26. Parity/ECC Structure" of the TRM shows TU_UCT_err gated by TCR ECC being on.
  • Hi Ninja,

    The ESM1.12 is ECC error for flexray CC RAM. GCS.PEL=0 is to enable the ECC protection for TCR.

    For ECC multi-bit error,The corresponding error flag in the message handler status (MHDS) register is set and the faulty message buffer is indicated.

    Please refer to 26.2.13.2 of TRM and check the related registers. Before using Flexray RAM, please initialize the flexray memory