Date: Sun, 2 Oct 2022 11:20:49 -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: <20221002182049.GA2255@www.zefox.net> In-Reply-To: <6DB88FC9-629C-43E6-9673-32640FC547F7@yahoo.com> References: <20220929002131.GA77106@www.zefox.net> <197D3C46-063B-4C67-AB1A-A3A072521D7F@yahoo.com> <A8C2BA4E-4520-4B34-9614-DDC4D8BEB097@yahoo.com> <6AA65AE6-41F1-405F-A592-7D641EA4C9CF@yahoo.com> <E3A1C678-8C47-4283-9F9F-4C9011DB8A2B@yahoo.com> <20221001174724.GA98055@www.zefox.net> <ABFDD634-5CB6-4DAE-B4DE-629CE7E4FE06@yahoo.com> <20221001193033.GA98348@www.zefox.net> <46226720-D867-4AD3-9559-A4365FAC28C4@yahoo.com> <6DB88FC9-629C-43E6-9673-32640FC547F7@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Oct 01, 2022 at 02:21:42PM -0700, Mark Millard wrote: > > http://nemesis.zefox.com/~fbsd/pelorus_console.txt7_orig_fragment > > still shows all the debug output. It did not > avoid the timing changes. > > You might need to not use either of: > > patch-common_usb__hub.c > patch-common_usb__storage.c > > and to disable the LOG_DEBUG and DEBUG lines in: > > patch-common_usb.c > > via turning them into comments by adding // as > indicated below: > > +//#define LOG_DEBUG > +//#define DEBUG > I think the changes were successful, u-boot compiles and runs. There's no extra output, and unfortunately only one successful reboot so far. Bus scanning seems quite slow. Storage devices are rarely found on reset, but usb reset does sometimes work. Run bootcmd_usb0 paused for minutes at Device 0: and paused again after reporting ..current device. No echo from the console, ctrl-C did nothing. The attempt sequence was SRBSPRMRPRRPUPPRRUPUCUUC where S is shutdown -r R is reset of u-boot U is usb reset P is powercycle M is stop at mountroot C is run bootcmd_usb0 The console log is at http://nemesis.zefox.com/~fbsd/pelorus_console.txt8_no_debug It now appears that the run bootcmd_usb0 rather reliably gets stuck, with the disk LED on steadily (no activity). Maybe in one of the loops seen earlier? Thanks again for all your help! bob prohaska
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20221002182049.GA2255>