search

renesas-rcar / arm-trusted-firmware

arm-trusted-firmware
Other
25 stars 39 forks source link

BL2: Failed to initialize DRAM after flashing firmware #1

Open helen-fornazier opened 7 years ago

helen-fornazier commented 7 years ago

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

I am compiling with: make PLAT=rcar LSI=M3 all dummytool

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

helen-fornazier commented 7 years ago

This seems to be a regressions as commit 1dafc36b49ba1f16c6bf2e8850c2e667c2e9ba92 "Update IPL and Secure Monitor Rev1.0.8" works

chrisbux commented 7 years ago

I am using a Salvator-X H3 board and ran into a similar issue. On the Salvator-X board, this error is resolved by setting SW7 to pin 1, which connects GP1_08/A8 to the BUKP_TRG signal.

If the H3 starter board has a similar option, you might try that.

martingkelly commented 7 years ago

@chrisbux just wanted to thank you; I had exactly this situation and you saved me :).

leon-anavi commented 6 years ago

Hi, I ended up in the same situation on m3ulcb after flashing firmware provided as part of AGL. Details are available at SPEC-1265. The M3 Starterkit that I have is No 0064. Any suggestions for a fix are appreciated.

Thanks, Leon

wang-guan commented 6 years ago

I think this issue is caused by abnormal state of PMIC, because GP1_8 connect to BKUP_TRG of PMIC via CPLD. Try to disable "RCAR_SYSTEM_SUSPEND"(RCAR_SYSTEM_SUSPEND=0) in your workspace, it will fix in cold boot forever while booting up.

leon-anavi commented 6 years ago

@wang-guan, thank you for the suggestion. Unfortunately disabling RCAR_SYSTEM_SUSPEND didn't solve the issue.

Best regards, Leon

truongtx1982 commented 5 years ago

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

I am compiling with: make PLAT=rcar LSI=M3 all dummytool

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

Hi

The issue related to SYSTEM_SUSPEND mode, you should re-build with options as below: make bl2 bl31 PLAT=rcar LSI=M3 dummytool RCAR_SYSTEM_SUSPEND=0

Regards, Truong