: [Boot Issue] Cubie A7Z stuck in reboot loop: "magic error" & "DRAM Pstate 0 training fail"

​Hi everyone,

​I recently received a brand new Radxa Cubie A7Z, but I am completely unable to get it to boot. Right out of the box, it is stuck in a continuous reboot loop. The system seems to crash exactly at the RAM initialization phase every single time.

​Here are the specific errors showing on my monitor (a photo of the full boot screen is attached):

​boot param - magic error

​DRAM Pstate 0 training, frequency is 1800 Mhz

​DRAM Pstate 0 training fail, fail result is 0xff!

​init dram fail

​To isolate the issue, I have already tried the following troubleshooting steps:

​Multiple SD Cards: I tested with different, known-working SD cards to rule out worn-out memory sectors or a failing card.

​Multiple OS Versions: I flashed several different versions of the official CLI image, including older stable releases and the newer RSDK pre-releases (both r4 and r5). The exact same error persists across all of them.

​Power Supply: I am powering the board with a high-quality 5V/3A wall adapter, so it shouldn’t be a voltage drop/brownout during the 1800 Mhz DRAM power spike.

​Because the system consistently throws the magic error and fails to train the DRAM regardless of the OS version or the SD card used, I am starting to suspect this specific board has a physical hardware defect with the memory chip or the boot sector.

​Has anyone else encountered this exact loop on recent batches of the A7Z? Is there a specific U-Boot workaround I might be missing, or should I just proceed with an RMA with my supplier?

​Thanks in advance for any insights!

​(Error screenshot attached below)

Can you try lightly pressing the memory chip and see if it can boot? If so then you have bad connection on memory chip.

yes - that sounds a bit like the problem i had: A7z quality control issues@RadxaYuntian just fyi: i returned my broken a7z via aliexpress and got refunded - not sure if it will find its way back to radxa so that you can analyze the problem on it directly