Failed to configure the DDR subsystem

[Matteo_Zini]

Good afternoon,

I am trying to boot a s32g3-rdb3 board with an sd-card image built from the auto-yocto repo (https://github.com/nxp-auto-linux/auto_yocto_bsp).

Most of the times, especially at the beginning of a new day, the execution of ATF hangs with the following error:

NOTICE: Reset status: Power-On Reset
ERROR: Failed to configure the DDR subsystem
PANIC at PC : 0x000000000000003f

On most days, after a long series of resets, at some point the boot process succeeds and from there on the board usually boots correctly for the entire day.

What could be the cause of this behavior?

I'm using the the sd-card provided in the board's box.

Thank you in advance.

Matteo Zini

[carlos_o]

Hi @Matteo_Zini,

It can be a hardware issue with the DDR, please to discard this option. Run the DDR Validation with S32 Design Studio and share the outputs.

[Matteo_Zini]

Hi, I hope I've run the test correctly, since I couldn't find many instructions. The results I obtained are summarized in the 3 attached screenshots.

Thank you.

Matteo

[carlos_o]

Hi @Matteo_Zini, 

thanks for sharing the test results. With that we can confirm that is not a hardware issue with the DDR.

Can you tell me which version of bsp are you using? Also, are you doing any modifications to the distribution? 

[Matteo_Zini]

I'm using version 43.0 (The latest I suppose). No modifications to the source.

Thank you.

[carlos_o]

Hi @Matteo_Zini, 

This RDB3 board is new? if not, when it starts to present this behavior? Can this RDB3 board boot normally and stably before?

[Matteo_Zini]

The board is new.

I think what happened is that during the first day, with the sd-card image provided on the card I found in the box, it worked without issues. Then I flashed my bsp image on the same card and it worked normally again.

Then on the second day it started behaving like that.

Thanks.

[Matteo_Zini]

Some additional information: it also happens with the GoldVIP sdcard image.

[Matteo_Zini · Accepted solution]

Ok, I think we found the issue. There is some false contact on the SoC. If we push it on the board, it always boots correctly.

[carlos_o]

Hi @Matteo_Zini, 

An apologize for the late reply, please contact your NXP sales/distributor to evaluate your case, they can help to see if it is a warranty issue. 

[carlos_o]

Hi @Matteo_Zini, 

I will review this with the internal team, this may take longer response time, we appreciate your patience. I'll come ASAP with more information.