Date: Sun, 13 Dec 2020 17:33:45 +0100 From: =?utf-8?Q?S=C3=B8ren_Schmidt?= <soren.schmidt@gmail.com> To: Ian Lepore <ian@freebsd.org>, freebsd-arm <freebsd-arm@freebsd.org> Cc: Daniel Engberg <daniel.engberg.lists@pyret.net> Subject: Re: FreeBSD-13.0-CURRENT-arm64-aarch64-ROCKPRO64-20201210-7578a4862f0 broken ? Message-ID: <87B7940E-119D-4C7F-AB9D-0C78E7F8D3A3@gmail.com> In-Reply-To: <0D6FCA87-F101-4AA0-A1BF-6EDBA003BC9F@gmail.com> References: <a9fca4d433dadbe2d1ca490bff3b189a@pyret.net> <4434862ed87c21113fb7f98636fe4694d73856ce.camel@freebsd.org> <0D6FCA87-F101-4AA0-A1BF-6EDBA003BC9F@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 13 Dec 2020, at 11.26, S=C3=B8ren Schmidt <soren.schmidt@gmail.com> = wrote: >=20 >> On 13 Dec 2020, at 00.00, Ian Lepore <ian@freebsd.org = <mailto:ian@freebsd.org>> wrote: >>=20 >> On Sat, 2020-12-12 at 23:53 +0100, Daniel Engberg wrote: >>> Hi, >>>=20 >>> While I haven't tried the exact version you're referring to I have a=20= >>> slightly older image that I compiled myself and it runs fine. The >>> only=20 >>> difference I can tell is that the memory (RAM) seems to be configure=20= >>> different on your device. I can provide a copy of the image if you >>> want. >>>=20 >>> U-Boot TPL 2020.10 (Dec 02 2020 - 23:00:31) >>> Channel 0: LPDDR4, 50MHz >>> BW=3D32 Col=3D10 Bk=3D8 CS0 Row=3D15 CS1 Row=3D15 CS=3D2 Die BW=3D16 = Size=3D2048MB >>> Channel 1: LPDDR4, 50MHz >>> BW=3D32 Col=3D10 Bk=3D8 CS0 Row=3D15 CS1 Row=3D15 CS=3D2 Die BW=3D16 = Size=3D2048MB >>> 256B stride >>> lpddr4_set_rate: change freq to 400000000 mhz 0, 1 >>> lpddr4_set_rate: change freq to 800000000 mhz 1, 0 >>> Trying to boot from BOOTROM >>> Returning to boot ROM... >>>=20 >>=20 >> That's interesting, because my first thought was "memory config >> problem", due to the mod-after-free "error" actually appearing to be = a >> single-bit ram error (val=3Ddeadc0df vs deadc0de). >>=20 >> -- Ian >=20 >=20 > Yes, something fishy is going on with the memory setup=E2=80=A6 > =46rom a working NetBSD boot: >=20 > channel 0 training pass! > channel 1 training pass! > change freq to 800MHz 1,0 > Channel 0: LPDDR4,800MHz > Bus Width=3D32 Col=3D10 Bank=3D8 Row=3D16 CS=3D1 Die Bus-Width=3D16 = Size=3D2048MB > Channel 1: LPDDR4,800MHz > Bus Width=3D32 Col=3D10 Bank=3D8 Row=3D16 CS=3D1 Die Bus-Width=3D16 = Size=3D2048MB > 256B stride > ch 0 ddrconfig =3D 0x101, ddrsize =3D 0x40 > ch 1 ddrconfig =3D 0x101, ddrsize =3D 0x40 >=20 Just tried to use their u-boot image to boot -current, and that works = fine. So, our port of u-boot or the official one has something borked for this = combo since after 2019.10. It is running a build world now on a NVMe stick, so lets see how that = turns out=E2=80=A6 (just 4 cores the big/litte thing is still not solved = it seems).. S=C3=B8ren Schmidt sos@deepcore.dk / sos@freebsd.org "So much code to hack, so little time"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?87B7940E-119D-4C7F-AB9D-0C78E7F8D3A3>