Date: Sun, 11 Oct 2020 21:06:25 +0200 From: Klaus Cucinauomo <maciphone2@googlemail.com> To: Robert Crowston <crowston@protonmail.com>, Kyle Evans <kevans@freebsd.org>, Mark Millard <marklmi@yahoo.com>, freebsd-arm@freebsd.org, "gonzo@freebsd.org" <gonzo@FreeBSD.org> Subject: Re: RPi4B: modern firmware vs. Device tree loaded to 0x4000 (size 0xbe0c) [fails] vs. to 0x1f0000 (size 0xbd90) [works]? Message-ID: <22B0D423-CEF4-4B74-846D-6F668A0F0B9F@googlemail.com> In-Reply-To: <0m0EOJpW7j-ziTjqjNz5Ldul7r8DT9bCjmgmsm5-kr9dX5pt2PEoQrZcFJ9nxtB8YXpqdrBk2ecMIjfijv3DEV26M9fzu3nwwQ90msFZBmw=@protonmail.com> References: <2B1B21CB-1A63-42CE-8917-98870C88CACE@yahoo.com> <F8DBF042-FD57-4AE3-8F98-0E36945469A9@yahoo.com> <3E9D015B-5702-4A52-9366-49E20BDDA5F4@googlemail.com> <tN5C4jzmxPmrt22GDxOfVidCT4I48oCyxVjfwxOdPAZpkQC1qBbhegOnnbkamnvGD-x81AxG5CorI1NIzfLf-91zcgOmQR0WtLrJ83PJJtI=@protonmail.com> <E07B6781-50E3-4A52-B582-F9EE81FE6743@googlemail.com> <cbC3hMQdQvaguB9vLBwvByx3_6cRzhxoJrMKL56_7RBNdwwPBudHiZpwfDEqUz2w34Ksv-fuo-5Iq-_0L_lfNdR5YEZDYudY1YGvshFl3Co=@protonmail.com> <79AA6AB2-9FE6-4A80-9E72-F6D7B7E6803F@googlemail.com> <3577889D-3102-4B50-955B-798717F93F92@googlemail.com> <0m0EOJpW7j-ziTjqjNz5Ldul7r8DT9bCjmgmsm5-kr9dX5pt2PEoQrZcFJ9nxtB8YXpqdrBk2ecMIjfijv3DEV26M9fzu3nwwQ90msFZBmw=@protonmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Am 11.10.2020 um 17:50 schrieb Robert Crowston = <crowston@protonmail.com>: > =E2=80=A6=E2=80=A6. > I am surprised that you can boot without the armstub. Can you post the = dmesg? > =E2=80=A6.. The absolute latest rpi-FW-master is only "bootable" without armstub and = only with the 4GB-model (8GB will need extra-patch) and only until 'No PSCI/SMCCC call function found ,it was the dmesg I = had sent :=20 https://dmesgd.nycbug.org/index.cgi?do=3Dview&id=3D5702=20 (In the dmesg-uart_2ndstage=3D1-output you can see that there=E2=80=99s = no armstub loaded) >=20 > Am 11.10.2020 um 18:05 schrieb Kyle Evans <kevans@freebsd.org>: > =E2=80=A6.. > mmel@ has mentioned that it may not be terribly hard to implement this > with spin tables instead. =E2=80=A6 sounds good ! > Am 11.10.2020 um 19:01 schrieb Robert Crowston = <crowston@protonmail.com>: > =E2=80=A6=E2=80=A6. > I upgraded to the latest (head) version of u-boot. Now when I try to = boot, I get stuck in malloc(). Anyone else see this? >=20 Did you exclude armstub from msdos-part ? Is it the 4GB(with VL805-fw-chip)? If it`s the 8GB : = https://patchwork.ozlabs.org/project/linux-pci/patch/20200629161845.6021-4= -nsaenzjulienne@suse.de/ = https://patchwork.ozlabs.org/project/linux-pci/patch/20200629161845.6021-5= -nsaenzjulienne@suse.de/ > Snipped... > Hit any key to stop autoboot: 0 > switch to partitions #0, OK > mmc0 is current device should not be mmc0 if you boot from USB/SSD Regards K.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?22B0D423-CEF4-4B74-846D-6F668A0F0B9F>