Re: u-boot debug, was: Re: U-boot on RPI3, sees disk but won't boot it

From: Mark Millard <>
Date: Sun, 25 Sep 2022 22:57:34 UTC
On 2022-Sep-25, at 12:34, bob prohaska <> wrote:
> . . .
> 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.  

Looking at
it appears the logging availability has to be enabled at compile time:

Enabling logging

The following options are used to enable logging
at compile time:

	• CONFIG_LOG - Enables the logging system
	• CONFIG_LOG_MAX_LEVEL - Max log level to
		build (anything higher is compiled out)
	• 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.

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.

(There is more about "Using DEBUG" vs. LOG_DEBUG and the like that
I'll not quote.)

Mark Millard
marklmi at