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: L2RAMW/L2FMC control and command parity

Part Number: TMS570LC4357


Dear Hercules Support Team,

In Table 6-46 in the TMS570LC4357 Datasheet there are several different parity errors mentioned fort he L2RAMW and the L2FMC (marked in the image). There seems to be little information in the documentation about the control and command parity.

 

If I understand correctly the control parity is the parity for the control bus, but I can’t find any information on the command parity and the „command parity error on idle“:

Q1: What is the command parity and why is there only a „command parity error on idle“?

Q2: Is the L2FMC „Mcmd parity error on Idle command“ the same as the L2RAMW „command parity error on idle“, but for the L2FMC?

Q3: Is the L2FMC „internal parity error“ the same as a control parity error?

Thanks in advance and best regards,

Max

  • Hi Max,

    Q1: What is the command parity and why is there only a „command parity error on idle“?

    The CPU calculates a parity bit that includes the address and control signals. This parity bit is sent to the slave module that receives the transaction (Flash/ RAM), which then decodes this parity bit based on its own calculation based on the address and control signals. "IDLE" is the command defined in the OCP (on-chip networking protocol) when a bus master is not performing a read or a write to memory. A parity error during this command is treated separately and is captured in the RAM/Flash error status register as well as output to the ESM. The parity error on other commands is a separate signal (ESM 3.13 and 3.15).

    Q2: Is the L2FMC „Mcmd parity error on Idle command“ the same as the L2RAMW „command parity error on idle“, but for the L2FMC?

    Yes, that is correct.

    Q3: Is the L2FMC „internal parity error“ the same as a control parity error?

    The L2FMC block checks the parity on an incoming address from the CPU. It also keeps checking the parity for all "transfers" of this address information within the L2FMC sub-blocks. Any parity error detected during these internal transfers is also flagged as an address parity error (ESM 2.17).

    Hope this helps.

    Regards, Sunil

  • Hi Sunil,

    Thank you for Clarifying! This helps alot.

    Best Regards,

    Max