From nobody Wed Sep 28 01:57:21 2022 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Mcfkm5KPrz4V5Gh for ; Wed, 28 Sep 2022 01:57:20 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "www.zefox.com", Issuer "www.zefox.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Mcfkl67f8z3XB4 for ; Wed, 28 Sep 2022 01:57:19 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.16.1/8.15.2) with ESMTPS id 28S1vMsL073497 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Tue, 27 Sep 2022 18:57:22 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.16.1/8.15.2/Submit) id 28S1vMli073496; Tue, 27 Sep 2022 18:57:22 -0700 (PDT) (envelope-from fbsd) Date: Tue, 27 Sep 2022 18:57:21 -0700 From: bob prohaska To: Mark Millard Cc: Klaus K??chemann , freebsd-arm@freebsd.org Subject: Re: u-boot debug, was: Re: U-boot on RPI3, sees disk but won't boot it Message-ID: <20220928015721.GA73356@www.zefox.net> References: <67C09E9F-AD1D-4D0D-9E6F-9C1B046D8952@googlemail.com> <4154AFCB-7428-4005-843A-4EF8C0EBCCB8@googlemail.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> List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9F57D5D0-F715-4DD2-A05C-FB2B9E8B5C30@yahoo.com> X-Rspamd-Queue-Id: 4Mcfkl67f8z3XB4 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of fbsd@www.zefox.net has no SPF policy when checking 50.1.20.27) smtp.mailfrom=fbsd@www.zefox.net X-Spamd-Result: default: False [-0.71 / 15.00]; AUTH_NA(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.999]; NEURAL_HAM_SHORT(-1.00)[-0.998]; NEURAL_HAM_LONG(-0.61)[-0.608]; MID_RHS_WWW(0.50)[]; WWW_DOT_DOMAIN(0.50)[]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; FREEMAIL_TO(0.00)[yahoo.com]; R_DKIM_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US]; MIME_TRACE(0.00)[0:+]; TO_MATCH_ENVRCPT_SOME(0.00)[]; R_SPF_NA(0.00)[no SPF record]; FREEMAIL_CC(0.00)[googlemail.com,freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; DMARC_NA(0.00)[zefox.net]; RCVD_TLS_LAST(0.00)[] X-ThisMailContainsUnwantedMimeParts: N On Tue, Sep 27, 2022 at 05:14:54PM -0700, Mark Millard wrote: > On 2022-Sep-27, at 16:29, bob prohaska wrote: > > > 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> > > > > Issuing > > U-Boot> run bootcmd_usb0 > > > > Device 0: > > > > [tens of seconds pause, looks like u-boot started over] > > > > U-Boot 2022.04 (Sep 27 2022 - 15:47:57 -0700) > . . . > > Do you have RPi* firmware debug output ennabled such that > you would see messages from it if the RPi* firmware started > over? > I do now, enable_uart=1 is set in config.txt > In other words, can you tell if . . . > > A) The RPi* firmware and then U-Boot both restarted > vs. > B) Just U-Boot restarted, not the RPi* firmware? > > If you can tell, which was it? > Looks to me as if A) is the case. After the Device 0: line comes Raspberry Pi Bootcode Read File: config.txt, 239 Read File: start.elf, 2952960 (bytes) Read File: fixup.dat, 7314 (bytes) MESS:00:00:21.191824:0: brfs: File read: /mfs/sd/config.txt MESS:00:00:21.196253:0: brfs: File read: 239 bytes MESS:00:00:21.252921:0: HDMI0:EDID error reading EDID block 0 attempt 0 The machine is headless, so I think the HDMI errors are normal. Following the self-inflicted reboot the machine reached multi-user. I'll see if I can figure out how to apply your patches shortly. Thank you! bob prohaska