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.

F29H850TU: Is there a document describing precisely the ERAD ?

Part Number: F29H850TU

Hello,

On the F29, I am trying to use the ERAD to protect the stack.

For that, I need a detailed description of all the registers of the ERAD, of the behavior of the ERAD...

I cannot find this information in the Technical Reference Manual of the F29.

So, is there a document describing precisely the ERAD ?

And I don't want to use the SDK, I don't want to do some reverse engineering of the SDK either.

Thanks

  • Hi,

    Details for ERAD is already present in ERAD Chapter of F29 technical reference manual.

    Please reach out to your field representative that can help you get the ERAD register descriptions that is missing in the ERAD chapter documentation we will update that in next publication.

    Thanks

  • Hello,

    I am using "SPRUJ79A – NOVEMBER 2024 – REVISED DECEMBER 2025" which seems to be the latest TRM available and in this document, as said previously, the ERAD (and especially the EBC) is not described as it should be: no description of the registers, no detailed description of the behavior of the EBC, no detailed description of the impact of each field of each register. This kind of information is what we can expect from a precise documentation.

    Now, the document being as it is (and I hope this will be updated in the next release), is there any other document (ERAD specific user manual, detailed application note...) that could help understand how this feature is working. This is especially important and critical as we have to use this feature in a safety context.

    Thank you

    Ronan

  • I have shared the ERAD register description with Francois, and this will be updated for next revision of Technical reference manual. We missed adding the register description due to document tooling issue at our end.

    Thanks

  • Thank you, Prarthan. I am closing this discussion.