KE18F512VLH16 ECC RAM Single Bit Correction

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

KE18F512VLH16 ECC RAM Single Bit Correction

38 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
0 Replies
%3CLINGO-SUB%20id%3D%22lingo-sub-2404369%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3EKE18F512VLH16%20ECC%20RAM%20Single%20Bit%20Correction%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2404369%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EI%20have%20a%20follow%20up%20question%20related%20to%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fcommunity.nxp.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F90401%22%20target%3D%22_blank%22%3E%40sean_dvorscak%3C%2FA%3E's%20post%20the%20other%20day%20(%3CA%20href%3D%22https%3A%2F%2Fcommunity.nxp.com%2Ft5%2FKinetis-Microcontrollers%2FKE1-ECC-RAM-Single-Bit-Corrrection%2Fm-p%2F2399360%23M68449%22%20target%3D%22_blank%22%3EKE1%20ECC%20RAM%20Single%20Bit%20Corrrection%3C%2FA%3E).%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fcommunity.nxp.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F237877%22%20target%3D%22_blank%22%3E%40Celeste_Liu%3C%2FA%3E%26nbsp%3Breplied%2C%3CBR%20%2F%3E%3CSPAN%3E-%26gt%3B%26gt%3B%26nbsp%3BIf%20implementing%20an%20optional%20scrub%2C%20please%20align%20the%20access%20according%20to%20the%20actual%20access%20size%20or%20scrub%20granularity%2C%20not%20blindly%20to%20the%20raw%20MCM_LMFAR%20value.%20Also%20don't%20use%20a%20fixed%204-byte%20access%20unless%20you%20first%20align%20the%20address%20appropriately%20and%20confirm%20the%20access%20size%20is%20valid.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3ECan%26nbsp%3BMCM_LMFATR%5BPEFSIZE%5D%20be%20used%20to%20determine%20the%20access%20size%3F%20If%20so%2C%20can%20this%20be%20used%20in%20tandem%20with%26nbsp%3BMCM_LMFAR%20to%20implement%20a%26nbsp%3Bread-correct-writeback%20operation%3F%20For%20example%2C%20if%26nbsp%3BMCM_LMFATR%5BPEFSIZE%5D%20is%203'b000%20indicating%20an%208-bit%20access%2C%20can%20I%20perform%20an%208-bit%20read%20from%20the%20address%20indicated%20by%26nbsp%3BMCM_LMFAR%20then%20perform%20an%208-bit%20write%20to%20the%20same%20address%20to%20correct%20the%20error.%20Similarly%2C%20if%26nbsp%3BMCM_LMFATR%5BPEFSIZE%5D%20is%203'b010%20indicating%20a%2032-bit%20access%2C%20can%20I%20perform%20a%2032-bit%20write%20to%20the%20address%20indicated%20by%20MCM_LMFAR%20without%20worrying%20about%20alignment%3F%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E