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

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