Re: 5.3-rc2: Found incompatible CPU

From: Anup Patel <anup@brainfault.org>
To: Andreas Schwab <schwab@suse.de>
Cc: Atish Patra <Atish.Patra@wdc.com>,
	"linux-riscv@lists.infradead.org"
	<linux-riscv@lists.infradead.org>
Subject: Re: 5.3-rc2: Found incompatible CPU
Date: Wed, 31 Jul 2019 13:42:37 +0530	[thread overview]
Message-ID: <CAAhSdy0NdStsJ+Lgo22VT=gzdiOnv40y0abxc-Cvt4cewMOpaQ@mail.gmail.com> (raw)
In-Reply-To: <mvmsgqm8xlc.fsf@suse.de>

On Wed, Jul 31, 2019 at 1:06 PM Andreas Schwab <schwab@suse.de> wrote:
>
> On Jul 31 2019, Atish Patra <Atish.Patra@wdc.com> wrote:
>
> > On 7/30/19, 5:51 AM, "linux-riscv on behalf of Andreas Schwab" <linux-riscv-bounces@lists.infradead.org on behalf of schwab@suse.de> wrote:
> >
> >     Trying to boot 5.3-rc2 on the HiFive I'm getting "Found incompatible
> >     CPU" for each cpu, which means that of_device_is_compatible(node,
> >     "riscv") is failing.  Any idea?
> >
> > Probably wrong DT ? If you are using OpenSBI, you need to point to the correct DT built by kernel by using FW_PAYLOAD_FDT_PATH.
>
> I don't see any difference between the 5.2 and 5.3 DTs.

Sorry for delay in response...

I had seen this issue when booting 5.3-rc1 from U-Boot.

Eventually, I figured that Linux-5.3-rc1 is placing some data structures at
end of RAM which is corrupting DTB placed at end of RAM.

A simple fix for this is to explicitly TFTP DTB to ${fdt_addr_r} on U-Boot
and pass ${fdt_addr_r} as DTB address.

You can also copying DTB from ${fdtcontroladdr} to ${fdt_addr_r} and
pass ${fdt_addr_t} as DTB address.

I have already send documentation update patch to U-Boot:
https://www.mail-archive.com/u-boot@lists.denx.de/msg335882.html

Regards,
Anup

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv