Open fisaksen opened 6 years ago
Hello,
Thank you for report.
Using Rev.1.0.19 (commit: 3f4912a) is working.
We found R-Car H3 Ver.1.1 DDR setting bug in Rev.1.0.20(commit: 1eee0ad). It was fixed in Rev 1.0.21(commit: c71e1be).
Regards,
I got same error using rev 1.0.20 (commit: 0340c68) and later. 1.0.19 rev2 (commit: 3f4912a) works fine. The board is Salvator-XS with R-Car H3 ver2.0.
[ 0.000062] INFO: ARM GICv2 driver initialized
[ 0.003345] NOTICE: BL2: R-Car Gen3 Initial Program Loader(CA57) Rev.1.0.20
[ 0.010292] NOTICE: BL2: PRR is R-Car H3 Ver2.0
[ 0.015032] NOTICE: BL2: Board is Salvator-XS Rev1.0
[ 0.019892] NOTICE: BL2: Boot device is HyperFlash(80MHz)
[ 0.025323] NOTICE: BL2: LCM state is CM
[ 0.029357] NOTICE: BL2: AVS setting succeeded. DVFS_SetVID=0x53
[ 0.035376] NOTICE: BL2: DDR1600(rev.0.31rc02)NOTICE: [COLD_BOOT]NOTICE: ..1
[ 0.057088] NOTICE: BL2: Failed to DRAM initialize (-1).
Hello,
[ 0.010292] NOTICE: BL2: PRR is R-Car H3 Ver2.0 [ 0.035376] NOTICE: BL2: DDR1600(rev.0.31rc02)NOTICE: [COLD_BOOT]NOTICE: ..1
DDR 3200 mode is expected for Salvator-XS with R-Car H3 ver2.0. Could you check Salvator-XS DDR clock frequency (SW10:MD19 and MD17)?
Regards,
I only have the Salavtor-X with ver 1.1. Is DDR 3200 supposed to work with that as well ?
Hi, hosoya
On your advice, I changed PIN 3, 4 to ON from OFF in SW10 and succeeded to boot kernel. Thanks!!
Hello,
[ 0.005843] NOTICE: BL2: PRR is R-Car H3 Ver1.1
I only have the Salavtor-X with ver 1.1. Is DDR 3200 supposed to work with that as well ?
R-Car H3 Ver1.1 supports to DDR2400.
regards,
I got same error using rev 1.0.20 (commit: 0340c68) and later. 1.0.19 rev2 (commit: 3f4912a) works fine. The board is Salvator-XS with R-Car H3 ver2.0.
[ 0.000062] INFO: ARM GICv2 driver initialized [ 0.003345] NOTICE: BL2: R-Car Gen3 Initial Program Loader(CA57) Rev.1.0.20 [ 0.010292] NOTICE: BL2: PRR is R-Car H3 Ver2.0 [ 0.015032] NOTICE: BL2: Board is Salvator-XS Rev1.0 [ 0.019892] NOTICE: BL2: Boot device is HyperFlash(80MHz) [ 0.025323] NOTICE: BL2: LCM state is CM [ 0.029357] NOTICE: BL2: AVS setting succeeded. DVFS_SetVID=0x53 [ 0.035376] NOTICE: BL2: DDR1600(rev.0.31rc02)NOTICE: [COLD_BOOT]NOTICE: ..1 [ 0.057088] NOTICE: BL2: Failed to DRAM initialize (-1).
hi, I've got a similar error on salavtor-xs as following print info, any body have ideas about this? 0.000163] NOTICE: BL2: R-Car Gen3 Initial Program Loader(CA57) Rev.1.0.20 [ 0.005736] NOTICE: BL2: PRR is R-Car H3 Ver3.0 [ 0.010326] NOTICE: BL2: Board is Salvator-XS Rev1.0 [ 0.015361] NOTICE: BL2: Boot device is HyperFlash(160MHz) [ 0.020883] NOTICE: BL2: LCM state is CM [ 0.024928] NOTICE: BL2: AVS setting succeeded. DVFS_SetVID=0x53 [ 0.030913] NOTICE: BL2: CH0: 0x400000000 - 0x440000000, 1 GiB [ 0.036784] NOTICE: BL2: CH1: 0x500000000 - 0x540000000, 1 GiB [ 0.042668] NOTICE: BL2: CH2: 0x600000000 - 0x640000000, 1 GiB [ 0.048553] NOTICE: BL2: CH3: 0x700000000 - 0x740000000, 1 GiB [ 0.054478] NOTICE: BL2: DDR3200(rev.0.31)NOTICE: [WARM_BOOT]ERROR: Warm booting... The potential of BKUP_TRG 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. [ 0.087737] NOTICE: [BOOT_STATUS_UPDATE_ERROR]NOTICE: ..1 [ 0.093277] NOTICE: BL2: Failed to DRAM initialize (-1). [ 5.007798] ERROR: [ 5.008592] ERROR: BL2: System WDT overflow, occured address is 0xe6312c78
I got same error using rev 1.0.20 (commit: 0340c68) and later. 1.0.19 rev2 (commit: 3f4912a) works fine. The board is Salvator-XS with R-Car H3 ver2.0.
[ 0.000062] INFO: ARM GICv2 driver initialized [ 0.003345] NOTICE: BL2: R-Car Gen3 Initial Program Loader(CA57) Rev.1.0.20 [ 0.010292] NOTICE: BL2: PRR is R-Car H3 Ver2.0 [ 0.015032] NOTICE: BL2: Board is Salvator-XS Rev1.0 [ 0.019892] NOTICE: BL2: Boot device is HyperFlash(80MHz) [ 0.025323] NOTICE: BL2: LCM state is CM [ 0.029357] NOTICE: BL2: AVS setting succeeded. DVFS_SetVID=0x53 [ 0.035376] NOTICE: BL2: DDR1600(rev.0.31rc02)NOTICE: [COLD_BOOT]NOTICE: ..1 [ 0.057088] NOTICE: BL2: Failed to DRAM initialize (-1).
Hi
You can try to re-build it with option as below, so It may related to DDR size on the board, this command to build for H3 Salvator 4G DDR, make PLAT=rcar LSI=H3 RCAR_SYSTEM_SUSPEND=0 RCAR_DRAM_LPDDR4_MEMCONF=0
Regards, Truong
I got same error using rev 1.0.20 (commit: 0340c68) and later. 1.0.19 rev2 (commit: 3f4912a) works fine. The board is Salvator-XS with R-Car H3 ver2.0.
[ 0.000062] INFO: ARM GICv2 driver initialized [ 0.003345] NOTICE: BL2: R-Car Gen3 Initial Program Loader(CA57) Rev.1.0.20 [ 0.010292] NOTICE: BL2: PRR is R-Car H3 Ver2.0 [ 0.015032] NOTICE: BL2: Board is Salvator-XS Rev1.0 [ 0.019892] NOTICE: BL2: Boot device is HyperFlash(80MHz) [ 0.025323] NOTICE: BL2: LCM state is CM [ 0.029357] NOTICE: BL2: AVS setting succeeded. DVFS_SetVID=0x53 [ 0.035376] NOTICE: BL2: DDR1600(rev.0.31rc02)NOTICE: [COLD_BOOT]NOTICE: ..1 [ 0.057088] NOTICE: BL2: Failed to DRAM initialize (-1).
Hi
You can try to re-build it with option as below, so It may related to DDR size on the board, this command to build for H3 Salvator 4G DDR, make PLAT=rcar LSI=H3 RCAR_SYSTEM_SUSPEND=0 RCAR_DRAM_LPDDR4_MEMCONF=0
Regards, Truong
That's OK! Thanks!!!
I just built the latest version (Rev.1.0.20) fromhttps://github.com/renesas-rcar/arm-trusted-firmware.git
and initializing DDR fails:
[ 0.000283] NOTICE: BL2: R-Car Gen3 Initial Program Loader(CA57) Rev.1.0.20 [ 0.005843] NOTICE: BL2: PRR is R-Car H3 Ver1.1 [ 0.010426] NOTICE: BL2: Board is Salvator-X Rev1.0 [ 0.015368] NOTICE: BL2: Boot device is HyperFlash(80MHz) [ 0.020793] NOTICE: BL2: LCM state is CM [ 0.024838] NOTICE: BL2: AVS setting succeeded. DVFS_SetVID=0x53 [ 0.030887] NOTICE: BL2: DDR2400(rev.0.31)NOTICE: [COLD_BOOT]NOTICE: ..1 [ 0.162859] NOTICE: BL2: Failed to DRAM initialize (-1).
Using Rev.1.0.19 (commit: 3f4912a3199c19ac3253dc95a1e3ecd5af8f0efd) is working.