Date: Sat, 1 Oct 2022 14:50:48 -0700 From: Mark Millard <marklmi@yahoo.com> To: bob prohaska <fbsd@www.zefox.net> Cc: freebsd-arm <freebsd-arm@freebsd.org>, freebsd-uboot@freebsd.org Subject: Re: u-boot debug, was: Re: U-boot on RPI3, sees disk but won't boot it Message-ID: <DDCDC4AC-FF23-44FD-8FFC-3CE7A9FEA5E5@yahoo.com> In-Reply-To: <20221001212155.GA98793@www.zefox.net> References: <20220928234341.GA77046@www.zefox.net> <20220929002131.GA77106@www.zefox.net> <197D3C46-063B-4C67-AB1A-A3A072521D7F@yahoo.com> <A8C2BA4E-4520-4B34-9614-DDC4D8BEB097@yahoo.com> <6AA65AE6-41F1-405F-A592-7D641EA4C9CF@yahoo.com> <E3A1C678-8C47-4283-9F9F-4C9011DB8A2B@yahoo.com> <20221001174724.GA98055@www.zefox.net> <ABFDD634-5CB6-4DAE-B4DE-629CE7E4FE06@yahoo.com> <20221001193033.GA98348@www.zefox.net> <46226720-D867-4AD3-9559-A4365FAC28C4@yahoo.com> <20221001212155.GA98793@www.zefox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2022-Oct-1, at 14:21, bob prohaska <fbsd@www.zefox.net> wrote: > On Sat, Oct 01, 2022 at 12:58:00PM -0700, Mark Millard wrote: >> >> What you report for behavior below suggests that you got >> an appropriate u-boot.bin in place. >> > > That's a relief! > >> >> Given the "no failures to find a boot device", >> I suggest an experiment of (temporarily?) >> reverting to the official rpi_arm64_fragment >> (to disable the U-Boot logging) and seeing how >> it behaves without the extra messages. >> > > Done, using a copy of rpi_arm64_fragment from > another FreeBSD box that's dated April 5th. > I didn't think it'd be that old, hope not! > > Out of 14 boot attempts, about 7 ended in loops. > Only two shutdown -r now attempts succeeded. The > transcipt is at > http://nemesis.zefox.com/~fbsd/pelorus_console.txt7_orig_fragment > > I'll resume experiments in the morning after checking email. I had sent a note about that file still showing debug output. The experiment needs to have no debug output but to have the 3 mdelay(...) calls in question in place. Anything else is a different type of test. So you can look in files generated to see if the debug output had been avoided. (The status of the mdelay's is less obvious.) === Mark Millard marklmi at yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?DDCDC4AC-FF23-44FD-8FFC-3CE7A9FEA5E5>