Confusion about the Parity ECC Area initialization using Memory Hardware basedd Auto-Initialization

I will forward your question to the expert.

Regards,

Haixiao

Hello Sunil,

In the above mentioned Link, you mentioned HTU must also have Parity Check enabled in order to enable any initialization to Parity Area.

That means I am assuming without Parity Check enable, HTU Parity Are can't be written.

But if you see another link as mentioned below :

http://e2e.ti.com/support/microcontrollers/hercules/f/312/p/235475/828423.aspx#828423

Zhaohong said that whether Parity Check is enabled or not, HTU Parity Area will be updated according to DEVCR1 Register whenever there is any WRITE Action to HTU DCP RAM Area. This is expected behaviour.

Can you please confirm whether HTU Parity Area write action [Parity Initialization]  will not occur if Parity Check within HTU is not enabled?

Because two links are telling different w.r.t. HTU Parity Area write access.

I thought, HTU Parity Area can be initialized either by using MEMINIT Hardware Auto-Init or by using CPU Write Action to HTU DCP RAM because Parity Area will be always writtent whether Parity Check is enabled or not within HTU.

Zhahong didn't want to mention which peripherals have this behaviour of uncondition Parity Area write irrespective of corresponding Parity Check Bits within the Peripheral.

Please elaborate more with different behaviours for each peripheral [including ADC RAM, MIBSPI RAM, DCAN RAM].

Thank you.
Regards