KE18F512VLH16 ECC RAM Single Bit Correction

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

KE18F512VLH16 ECC RAM Single Bit Correction

196 Views
rseigle77
Contributor I

I have a follow up question related to @sean_dvorscak's post the other day (KE1 ECC RAM Single Bit Corrrection).

@Celeste_Liu replied,
->> If implementing an optional scrub, please align the access according to the actual access size or scrub granularity, not blindly to the raw MCM_LMFAR value. Also don't use a fixed 4-byte access unless you first align the address appropriately and confirm the access size is valid.

Can MCM_LMFATR[PEFSIZE] be used to determine the access size? If so, can this be used in tandem with MCM_LMFAR to implement a read-correct-writeback operation? For example, if MCM_LMFATR[PEFSIZE] is 3'b000 indicating an 8-bit access, can I perform an 8-bit read from the address indicated by MCM_LMFAR then perform an 8-bit write to the same address to correct the error. Similarly, if MCM_LMFATR[PEFSIZE] is 3'b010 indicating a 32-bit access, can I perform a 32-bit write to the address indicated by MCM_LMFAR without worrying about alignment?

0 Kudos
Reply
3 Replies

107 Views
Celeste_Liu
NXP Employee
NXP Employee

Hello @rseigle77 ,

Regarding your question, I need to escalate it to our internal team for further investigation. According to our process, please provide the end application name.

Thanks for your cooperation.

BR

Celeste

0 Kudos
Reply

93 Views
rseigle77
Contributor I

Hi @Celeste_Liu  - P7 is the name of the end application.

0 Kudos
Reply

127 Views
Celeste_Liu
NXP Employee
NXP Employee

Hello @rseigle77 ,

I have seen your post. Let me spend some time investigating this issue, and I will get back to you once I have more information.

BR

Celeste

0 Kudos
Reply