Date: Sun, 25 Sep 2022 15:57:34 -0700 From: Mark Millard <marklmi@yahoo.com> To: bob prohaska <fbsd@www.zefox.net> Cc: FreeBSD Mailing List <freebsd-ports@freebsd.org>, freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: u-boot debug, was: Re: U-boot on RPI3, sees disk but won't boot it Message-ID: <0C5BA8D9-0EEB-421A-99E7-2E6F10D5D425@yahoo.com> In-Reply-To: <20220925193415.GA63733@www.zefox.net> References: <20220919221553.GA33878@www.zefox.net> <9A2A4E83-22F2-4441-82BF-0B8E6718ED34@yahoo.com> <20220921154240.GA37735@www.zefox.net> <8CC2A42B-21AC-44C6-BD02-44D320CADF63@yahoo.com> <20220921175026.GA45144@www.zefox.net> <5DB9C93B-B9E1-418D-ABA3-8A0CFCE85C0F@yahoo.com> <3781CF46-C4F7-4579-8655-B7558B724C0A@yahoo.com> <20220922014500.GA46697@www.zefox.net> <20220925160531.GA63213@www.zefox.net> <DBD238AA-8C65-46D2-87CC-A9875C6959BF@yahoo.com> <20220925193415.GA63733@www.zefox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2022-Sep-25, at 12:34, bob prohaska <fbsd@www.zefox.net> wrote: >=20 > . . . >=20 > IIRC I did try replacing the Sabrent enclosure with the Startech > enclosure, which worked and seemed to implicate the Sabrent as > the culprit. Thus my interest in u-boot debug information. =20 Looking at https://u-boot.readthedocs.io/en/latest/develop/logging.html it appears the logging availability has to be enabled at compile time: QUOTE Enabling logging The following options are used to enable logging at compile time: =E2=80=A2 CONFIG_LOG - Enables the logging system =E2=80=A2 CONFIG_LOG_MAX_LEVEL - Max log level to build (anything higher is compiled out) =E2=80=A2 CONFIG_LOG_CONSOLE - Enable writing log records to the console If CONFIG_LOG is not set, then no logging will be available. The above have SPL and TPL versions also, e.g. CONFIG_SPL_LOG_MAX_LEVEL and CONFIG_TPL_LOG_MAX_LEVEL. If logging is disabled, the default behaviour is to output any message at level LOGL_INFO and below. If logging is disabled and DEBUG is defined (at the very top of a C file) then any message at LOGL_DEBUG will be written. END QUOTE (There is more about "Using DEBUG" vs. LOG_DEBUG and the like that I'll not quote.) =3D=3D=3D Mark Millard marklmi at yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0C5BA8D9-0EEB-421A-99E7-2E6F10D5D425>