Date: Tue, 27 Sep 2022 19:25:09 -0700 From: Mark Millard <marklmi@yahoo.com> To: bob prohaska <fbsd@www.zefox.net> Cc: Klaus K??chemann <maciphone2@googlemail.com>, freebsd-arm@freebsd.org Subject: Re: u-boot debug, was: Re: U-boot on RPI3, sees disk but won't boot it Message-ID: <E0BDFF06-3998-48E0-B04D-3B4A11F4A9AE@yahoo.com> In-Reply-To: <C657BE65-ADCC-479B-B756-445D0825E0FA@yahoo.com> References: <67C09E9F-AD1D-4D0D-9E6F-9C1B046D8952@googlemail.com> <4154AFCB-7428-4005-843A-4EF8C0EBCCB8@googlemail.com> <D8708275-D396-4D2F-9461-B305E522BCCE@yahoo.com> <9A3609DF-D873-4712-A61D-C351C162EF2A@googlemail.com> <61CFA9D4-8DFD-41C5-A2B4-E5B3CD78C327@yahoo.com> <650FD030-783D-46C4-8CC9-50D608569898@yahoo.com> <81C8A094-8492-41DC-A74E-486A9225A2A3@googlemail.com> <760FE9D5-7A1D-40C2-B4CC-E90B300F5B3B@yahoo.com> <20220927232930.GC72077@www.zefox.net> <9F57D5D0-F715-4DD2-A05C-FB2B9E8B5C30@yahoo.com> <20220928015721.GA73356@www.zefox.net> <C657BE65-ADCC-479B-B756-445D0825E0FA@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2022-Sep-27, at 19:13, Mark Millard <marklmi@yahoo.com> wrote: > On 2022-Sep-27, at 18:57, bob prohaska <fbsd@www.zefox.net> wrote: >=20 >> On Tue, Sep 27, 2022 at 05:14:54PM -0700, Mark Millard wrote: >>> On 2022-Sep-27, at 16:29, bob prohaska <fbsd@www.zefox.net> wrote: >>>=20 >>>> On Tue, Sep 27, 2022 at 03:27:10PM -0700, Mark Millard wrote: >>>>> . . . >>>> . . . >>>> U-Boot> usb reset >>>> resetting USB... >>>> Bus usb@7e980000: dwc2_usb usb@7e980000: Can't get reset: -2 >>>> USB DWC2 >>>> scanning bus usb@7e980000 for devices... 6 USB Device(s) found >>>> scanning usb for storage devices... 1 Storage Device(s) found >>>> U-Boot>=20 >>>>=20 >>>> Issuing >>>> U-Boot> run bootcmd_usb0 >>>>=20 >>>> Device 0:=20 >>>>=20 >>>> [tens of seconds pause, looks like u-boot started over] >>>>=20 >>>> U-Boot 2022.04 (Sep 27 2022 - 15:47:57 -0700) >>> . . . >>>=20 >>> Do you have RPi* firmware debug output ennabled such that >>> you would see messages from it if the RPi* firmware started >>> over? >>>=20 >> I do now, enable_uart=3D1 is set in config.txt >=20 > Good. Beyond enable_uart=3D1 there is, quoting from: https://github.com/raspberrypi/firmware/issues/1301 QUOTE "uart_2ndstage=3D1" causes the second-stage loader (bootcode.bin, Pi 4 = EEPROM) and the main firmware (start*.elf) to output diagnostic = information to UART0. Output is likely to interfere with Bluetooth = operation unless disabled ("dtoverlay=3Ddisable-bt") or switched to the = other UART ("dtoverlay=3Dminiuart-bt"), and if the UART is accessed = simultaneously to output from Linux then data loss could occur, so this = is not a feature to activate except when trying to diagnose a loading = problem. END QUOTE It is possible that this extra output might put out messages about watchdog activity if such is involved in the restarts. For the current purposes, dtdebug=3D1 probably does not provide anything of interest. But it is available to enable as well. =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?E0BDFF06-3998-48E0-B04D-3B4A11F4A9AE>