Repeated EDAC SEU UE Errors on Agilex 7 AGI027FB

Hello Team,

I am booting Linux on the Agilex 7 development board (AGI027FB) using the Yocto-based Poky Linux distribution.
During boot, the kernel continuously reports the following EDAC (Error Detection and Correction) messages related to the Altera ECC Manager and the cram-seu0 block.

The messages appear at regular intervals of approximately 4–5 seconds and continue even after Linux has completed booting and reached the login prompt.

Board: Agilex 7 Development Kit (AGI027FB)
Quartus Version: Quartus Prime Pro Edition 2025.3.1

Logs snippet : 
[   12.161133] EDAC Altera: SEU UE: Count=0x8, SecAddr=0x30, ErrData=0x0
[   12.167617] EDAC DEVICE2: UE: Altera ECC Manager instance: cram-seu0 block: cram-seu0 count: 1 'cram-seu'
[   12.187218] EDAC Altera: SEU UE: Count=0x7, SecAddr=0x30, ErrData=0x0
[   12.193645] EDAC DEVICE2: UE: Altera ECC Manager instance: cram-seu0 block: cram-seu0 count: 1 'cram-seu'
[   12.213221] EDAC Altera: SEU UE: Count=0x6, SecAddr=0x30, ErrData=0x0
[   12.219650] EDAC DEVICE2: UE: Altera ECC Manager instance: cram-seu0 block: cram-seu0 count: 1 'cram-seu'
[   12.239241] EDAC Altera: SEU UE: Count=0x5, SecAddr=0x30, ErrData=0x0
[   12.245677] EDAC DEVICE2: UE: Altera ECC Manager instance: cram-seu0 block: cram-seu0 count: 1 'cram-seu'
[   12.265249] EDAC Altera: SEU UE: Count=0x4, SecAddr=0x30, ErrData=0x0
[   12.271689] EDAC DEVICE2: UE: Altera ECC Manager instance: cram-seu0 block: cram-seu0 count: 1 'cram-seu'
[   12.291270] EDAC Altera: SEU UE: Count=0x3, SecAddr=0x30, ErrData=0x0
[   12.297696] EDAC DEVICE2: UE: Altera ECC Manager instance: cram-seu0 block: cram-seu0 count: 1 'cram-seu'
[   12.317269] EDAC Altera: SEU UE: Count=0x2, SecAddr=0x30, ErrData=0x0
[   12.323698] EDAC DEVICE2: UE: Altera ECC Manager instance: cram-seu0 block: cram-seu0 count: 1 'cram-seu'
[   12.343277] EDAC Altera: SEU UE: Count=0x1, SecAddr=0x30, ErrData=0x0
[   12.349704] EDAC DEVICE2: UE: Altera ECC Manager instance: cram-seu0 block: cram-seu0 count: 1 'cram-seu'

We also tried by un-tick the "Enable error detection check" (screenshot attached). Still we get the same thing as above. Do we need any more config changes either in Quartus or anywhere during Yocto build ?
Need support for the same.

Let me know if any more information is required.

Thank You!

Best Regards,
Rajas Patil