BL2: Failed to DRAM initialize after flashing firmware from deploy/images/m3ulcb

[helen-fornazier]

Hi,

I am working with a M3 StarterKit No. 0065 (RTP0RC7796SKB00010SA03). It was booting fine with the original firmware, but just after flashing a new firmware I get the following error:

NOTICE:  BL2: R-Car Gen3 Initial Program Loader(CA57) Rev.1.0.12
NOTICE:  BL2: PRR is R-Car M3 ES1.0
NOTICE:  BL2: Boot device is HyperFlash(80MHz)
NOTICE:  BL2: LCM state is CM
NOTICE:  BL2: AVS setting succeeded. DVFS_SetVID=0x52
NOTICE:  BL2: DDR3200(rev.0.20)[WARM_BOOT]ERROR:
Warm booting...
 The potential of GP-1-8 did not switch to Low.
 If you expect the operation of cold boot,
 check the board configuration (ex, Dip-SW) and/or the H/W failure.
[BOOT_STATUS_UPDATE_ERROR]..1
NOTICE:  BL2: Failed to DRAM initialize (-1).
ERROR:
ERROR:   BL2: System WDT overflow, occured address is 0xe630d354

In my local.conf I configured the following architecture:

MACHINE ??= "m3ulcb"
SOC_FAMILY = "r8a7796"

I built the images following the instructions here with bitbake core-image-minimal

If I reset the board by pressing SW9, or pressing SW8 twice or repluging the source power and pressing SW8 I sill get warm boot detected.

I don't believe it is a hardware issue as it stopped working just after flashing the firmware using these instructions.

I would appreciate any help here
Thanks

[ygohda]

Hi
Your M3ULCB((RTP0RC7796SKB00010SA03) is a trial version.
Please ask the person who provided you the board.

Thanks,
Goda

[slawr]

Hi Helen,

All hail the Collaborans!

Goda-san is referring to the fact that there was a trial (pre-release) build of the M3 Starter Kit boards that was distributed to certain partners for some early development work. The specification was changed for the final v1 mass production board. Amongst the changes was the DDR. As it was a pre-production board it was not supported in later Yocto BSPs, hence the problem you are seeing.

If you have access to the R-Car h/w manual and the inclination you could chase down the DDR spec and add support for it, but I would suggest replacing the board with a production version. It would be a better development base.

Cheers,

Steve

[chrisbux]

For anyone that experiences this issue, you might refer to the solution in renesas-rcar/arm-trusted-firmware#1.