Date: Wed, 28 Sep 2022 19:35:04 -0700 From: bob prohaska <fbsd@www.zefox.net> To: Mark Millard <marklmi@yahoo.com> 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: <20220929023504.GA77327@www.zefox.net> In-Reply-To: <197D3C46-063B-4C67-AB1A-A3A072521D7F@yahoo.com> References: <C657BE65-ADCC-479B-B756-445D0825E0FA@yahoo.com> <E0BDFF06-3998-48E0-B04D-3B4A11F4A9AE@yahoo.com> <20220928045145.GB73356@www.zefox.net> <81F58716-72CE-45E8-951A-B7B92AD0FE95@yahoo.com> <20220928172839.GA75564@www.zefox.net> <62A7FD9D-DFAD-46B2-8681-F6EF0E5AC0DE@yahoo.com> <8CB25EDF-704A-4F86-B0D4-40818291C161@yahoo.com> <20220928234341.GA77046@www.zefox.net> <20220929002131.GA77106@www.zefox.net> <197D3C46-063B-4C67-AB1A-A3A072521D7F@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Sep 28, 2022 at 06:03:23PM -0700, Mark Millard wrote: > > We apparently do not have enough output enabled to see the debug > routine's output. We are seeing the printf output. > > There might be a way to set the output message levels while at a > U-Boot prompt, up to the maximum compiled in. But it may also be > that we would need, say, > > CONFIG_LOG_MAX_LEVEL=8 > > instead of the 7 we are now using. > Somewhere I got the idea that 7 was max, but I've replaced CONFIG_LOG_MAX_LEVEL=7 with =8 in rpi_arm64_fragment and recompiled. It didn't make an obvious difference, but you know better what to look for The output is at http://www.zefox.net/~fbsd/rpi3/u-boot/u-boot-fail-level-8 The warning message "...cannot read configuration..." does not appear in the new output and the disk isn't found anyway. That's a bit surprising. I just noticed there's still no log command at the u-boot prompt. IIUC there should be. Maybe another missing config? Thanks for reading! bob prohaska
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20220929023504.GA77327>