Re: r8a77950-salvator-x does nto boot since cfa7ede20f133cc81cef01dc3a516dda3a9721ee arm64: set TEXT_OFFSET to 0x0 in preparation for removing it entirely

Corentin Labbe
2021-01-05T11:49:40Z

Le Tue, Jan 05, 2021 at 11:13:03AM +0100, Geert Uytterhoeven a écrit :
> Hi Corentin,
>
> On Tue, Jan 5, 2021 at 10:52 AM Corentin Labbe
> <clabbe.montjoie@gmail.com> wrote:
> > Due to DTB renaming, salvatorX was not booted since a long time in kernelCI.
> > Now the rename is handled, the board fail to boot.
> >
> > I have bisected the problem:
>
> > # first bad commit: [cfa7ede20f133cc81cef01dc3a516dda3a9721ee] arm64: set TEXT_OFFSET to 0x0 in preparation for removing it entirely
> >
> > This is the interesting part of uboot log:
> > [ 0.000292] NOTI[ 0.000292] NOTICE: BL2: R-Car Gen3 Initial Program Loader(CA57) Rev.1.0.16
> > [ 0.005855] NOTICE: BL2: PRR is R-Car H3 Ver1.1
> > [ 0.010437] NOTICE: BL2: Board is Salvator-X Rev1.0
> > [ 0.015379] NOTICE: BL2: Boot device is HyperFlash(80MHz)
> > [ 0.020804] NOTICE: BL2: LCM state is CM
> > [ 0.024847] NOTICE: BL2: AVS setting succeeded. DVFS_SetVID=0x53
> > [ 0.030891] NOTICE: BL2: DDR1600(rev.0.27)NOTICE: [COLD_BOOT]NOTICE: ..0
> > [ 0.066311] NOTICE: BL2: DRAM Split is 4ch
> > [ 0.070195] NOTICE: BL2: QoS is default setting(rev.0.37)
> > [ 0.075697] NOTICE: BL2: Lossy Decomp areas
> > [ 0.079872] NOTICE: Entry 0: DCMPAREACRAx:0x80000540 DCMPAREACRBx:0x570
> > [ 0.086957] NOTICE: Entry 1: DCMPAREACRAx:0x40000000 DCMPAREACRBx:0x0
> > [ 0.093869] NOTICE: Entry 2: DCMPAREACRAx:0x20000000 DCMPAREACRBx:0x0
> > [ 0.100785] NOTICE: BL2: v1.3(release):b330e0e
> > [ 0.105274] NOTICE: BL2: Built : 15:26:51, Dec 6 2017
> > [ 0.110462] NOTICE: BL2: Normal boot
> > [ 0.114103] NOTICE: BL2: dst=0xe6320208 src=0x8180000 len=512(0x200)
> > [ 0.120652] NOTICE: BL2: dst=0x43f00000 src=0x8180400 len=6144(0x1800)
> > [ 0.127110] NOTICE: BL2: dst=0x44000000 src=0x81c0000 len=65536(0x10000)
> > [ 0.134336] NOTICE: BL2: dst=0x44100000 src=0x8200000 len=524288(0x80000)
> > [ 0.144816] NOTICE: BL2: dst=0x50000000 src=0x8640000 len=1048576(0x100000)
> > U-Boot 2015.04 (Dec 06 2017 - 15:26:59)
> > CPU: Renesas Electronics R8A7795 rev 1.1
> > Board: Salvator-X
> > I2C: ready
> > DRAM: 3.9 GiB
> > MMC: sh-sdhi: 0, sh-sdhi: 1, sh-sdhi: 2
> > In: serial
> > Out: serial
> > Err: serial
> > Net: ravb
> >
> > [...]
> >
> > booti 0x48080000 0x4a000000 0x48000000
> ^^^^^
> I take it this is the problem?
>
> For R-Car H3 ES1.0, I currently use the addresses below:
>
> tftpboot 0x60000000 h3-salvator-x/Image
> tftpboot 0x68000000 h3-salvator-x/r8a77950-salvator-x.dtb
> booti 0x60000000 - 0x68000000
>
> For R-Car H3 ES2.0 (and other R-Car Gen3 SoCs), I use other addresses:
>
> tftpboot 0x50000000 h3-salvator-xs/Image
> tftpboot 0x58000000 h3-salvator-xs/r8a77951-salvator-xs.dtb
> booti 0x50000000 - 0x58000000
>
> The firmware on your H3 ES1.1 board (Rev.1.0.16) is newer than on my
> ES1.0 board (Rev.1.0.12), so it's possible the second version works on
> your board, too.
>
> If these work for you, I'll update https://elinux.org/R-Car/Boards/Salvator-X[S]
>

Hello

Thanks, changing kernel/dtb address made it boot.
when testing, I have also discovered that r8a7796-m3ulcb hit the same issue than the salvatorX and that thoses address made it boot.

Regards