eenurkka opened a new pull request, #10461:
URL: https://github.com/apache/nuttx/pull/10461

   SiFive document: "ECC Error Handling Guide" states:
   
   "Any SRAM block or cache memory containing ECC functionality needs to be 
initialized prior to use. ECC will correct defective bits based on memory 
contents, so if memory is not first initialized to a known state, then ECC will 
not operate as expected. It is recommended to use a DMA, if available, to write 
the entire SRAM or cache to zeros prior to enabling ECC reporting. If no DMA is 
present, use store instructions issued from the processor."
   
   Clean the cache at this early stage so no ECC errors will be flooding later.
   
   ## Summary
   
   If ECC reporting is turned on, it initially reports many pointless errors; 
for example if that's enabled in Linux. Uninitialized L2LIM area is where the 
trouble comes from.
   
   ## Impact
   
   L2 ECC reporting enabled, all Polarfire devices
   
   ## Testing
   
   Throughout testing with several boards that had ECC reporting turned on in 
Linux
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to