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

From: Mark Millard <marklmi_at_yahoo.com>
Date: Wed, 28 Sep 2022 01:59:29 UTC 
On 2022-Sep-27, at 16:29, bob prohaska <fbsd@www.zefox.net> wrote:

> On Tue, Sep 27, 2022 at 03:27:10PM -0700, Mark Millard wrote:
>> 
>> Until the following are changed to have appropriate
>> values at the overall configuration level, it does
>> not appear that LOG_DEBUG and/or DEBUG will do
>> anything:
>> 
>> QUOTE
>> 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
>> END QUOTE
>> 
>> I expect that means having them set appropriately
>> in rpi_arm64_defconfig for the experiments.
>> 
> At long last I did it correctly and got a u-boot.bin
> that's just under 600kB. After issuing shutdown -r now
> part of the output includes
> 
> Uptime: 1h38m7s
> Resetting system ... 

Note the lack of output from the RPi* firmware at
the point in the sequence.

This answered an earlier question: you can not tell
a full RPi* reset with the RPi* firmware starting
over before U-Boot starts over vs. just U-Boot
starting over.

I expect that when you have said/shown U-Boot as
starting over that in fact the RPi* reset and the
RPi* firmware also started over (before it starts
U-Boot again).

It would help to enable getting some output from
the RPi* firmware as well so that you have evidence
for when it is (re)running.

> U-Boot 2022.04 (Sep 27 2022 - 15:47:57 -0700)
> 
> DRAM:  948 MiB
> RPI 3 Model B (0xa02082)



===
Mark Millard
marklmi at yahoo.com