From nobody Sun Sep 25 16:05:31 2022 X-Original-To: freebsd-ports@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 4Mb9hv3zZ0z4dYtB; Sun, 25 Sep 2022 16:05:35 +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 4Mb9ht1Tqvz45dJ; Sun, 25 Sep 2022 16:05:34 +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 28PG5VgN063330 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Sun, 25 Sep 2022 09:05:31 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.16.1/8.15.2/Submit) id 28PG5V70063329; Sun, 25 Sep 2022 09:05:31 -0700 (PDT) (envelope-from fbsd) Date: Sun, 25 Sep 2022 09:05:31 -0700 From: bob prohaska To: freebsd-ports@freebsd.org Cc: freebsd-arm Subject: u-boot debug, was: Re: U-boot on RPI3, sees disk but won't boot it Message-ID: <20220925160531.GA63213@www.zefox.net> References: <20220919221553.GA33878@www.zefox.net> <9A2A4E83-22F2-4441-82BF-0B8E6718ED34@yahoo.com> <20220921154240.GA37735@www.zefox.net> <8CC2A42B-21AC-44C6-BD02-44D320CADF63@yahoo.com> <20220921175026.GA45144@www.zefox.net> <5DB9C93B-B9E1-418D-ABA3-8A0CFCE85C0F@yahoo.com> <3781CF46-C4F7-4579-8655-B7558B724C0A@yahoo.com> <20220922014500.GA46697@www.zefox.net> List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220922014500.GA46697@www.zefox.net> X-Rspamd-Queue-Id: 4Mb9ht1Tqvz45dJ 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 [-1.10 / 15.00]; AUTH_NA(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.997]; MID_RHS_WWW(0.50)[]; WWW_DOT_DOMAIN(0.50)[]; MIME_GOOD(-0.10)[text/plain]; TO_DN_SOME(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US]; R_SPF_NA(0.00)[no SPF record]; MLMMJ_DEST(0.00)[freebsd-ports@freebsd.org,freebsd-arm@freebsd.org]; RCPT_COUNT_TWO(0.00)[2]; ARC_NA(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; DMARC_NA(0.00)[zefox.net]; RCVD_COUNT_THREE(0.00)[3]; RCVD_TLS_LAST(0.00)[]; MID_RHS_MATCH_FROM(0.00)[] X-ThisMailContainsUnwantedMimeParts: N On Wed, Sep 21, 2022 at 06:45:00PM -0700, bob prohaska wrote: > > After setting initial_turbo=60 in config.txt the first reboot > found the disk, the second did not. Running usb reset then > found the disk, but run bootcmd_usb0 seemingly caused a reset > that _then_ found the disk. It looks as if u-boot is somehow restarting itself unexpectedly. This is an RPi3B running stable-13, system and ports up to date as of yesterday. Here's an example session following a failed boot attempt: U-Boot> usb reset resetting USB... Bus usb@7e980000: 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> usb part [I think some information about the disk should have been displayed] U-Boot 2022.04 (Sep 23 2022 - 17:28:32 -0700) DRAM: 948 MiB [...usual startup output] Are there any debug switches for u-boot? I've looked a bit and what I find is either stale or not implemented. There's a reference to a "log" command, but it does not seem to be recognized. It does seem clear that the presence of a timeout file makes no meaningful difference. Boot succeeds rate is less than 50% This is using an unmodified u-boot-rpi-arm64 built locally. The system has no microSD installed, u-boot is started from the USB disk (which is found by firmware without trouble). If setting up a microSD to start u-boot alone would simplify matters that seems worth a try. Hints much appreciated! Once the machine boots into freebsd it seems to work just fine. The problem appears to be with u-boot only. Thanks for reading, bob prohaska