From nobody Thu Sep 22 01:45:00 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 4MXylJ5R3Lz4cwY1 for ; Thu, 22 Sep 2022 01:45:00 +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 4MXylH4K0qz3CFX for ; Thu, 22 Sep 2022 01:44:59 +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 28M1j0cI047090 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Wed, 21 Sep 2022 18:45:00 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.16.1/8.15.2/Submit) id 28M1j0oI047089; Wed, 21 Sep 2022 18:45:00 -0700 (PDT) (envelope-from fbsd) Date: Wed, 21 Sep 2022 18:45:00 -0700 From: bob prohaska To: Mark Millard Cc: freebsd-arm Subject: Re: U-boot on RPI3, sees disk but won't boot it Message-ID: <20220922014500.GA46697@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> 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: <3781CF46-C4F7-4579-8655-B7558B724C0A@yahoo.com> X-Rspamd-Queue-Id: 4MXylH4K0qz3CFX 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_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-0.999]; NEURAL_HAM_SHORT(-1.00)[-0.999]; MID_RHS_WWW(0.50)[]; WWW_DOT_DOMAIN(0.50)[]; MIME_GOOD(-0.10)[text/plain]; FREEMAIL_TO(0.00)[yahoo.com]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; MIME_TRACE(0.00)[0:+]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_TLS_LAST(0.00)[]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; TO_DN_ALL(0.00)[]; R_SPF_NA(0.00)[no SPF record]; RCVD_COUNT_THREE(0.00)[3]; DMARC_NA(0.00)[zefox.net]; MID_RHS_MATCH_FROM(0.00)[] X-ThisMailContainsUnwantedMimeParts: N On Wed, Sep 21, 2022 at 01:27:45PM -0700, Mark Millard wrote: > I used: > > tar -xf /usr/ports/distfiles/u-boot/u-boot-2022.04.tar.bz2 u-boot-2022.04/include/configs/rpi.h > > to create a local u-boot-2022.04/include/configs/rpi.h > in order to look at the modern file. The > ENV_DEVICE_SETTINGS line from: > > #define CONFIG_EXTRA_ENV_SETTINGS \ > "dhcpuboot=usb start; dhcp u-boot.uimg; bootm\0" \ > ENV_DEVICE_SETTINGS \ > ENV_DFU_SETTINGS \ > ENV_MEM_LAYOUT_SETTINGS \ > BOOTENV > > appears to be at line 173. > > A correct patch file finds the matching lines despite the > difference in line numbers, a difference that is not too > large by its matching criteria (given correct text matches). > > The modern FreeBSD lists might allow text attachments so > I'll try that publicly. (It still has the 210 line number.) > The patch emailed as an attachment applied without a problem. Better still, it seemed to help with mass storage device discovery for the first five or so tries. Around try six, the system lost the ability to recognize the USB mass storage device and then seemed to get stuck in a loop, with repeated attempts failing. 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. The display of usb tree output isn't always the same. On a failed try it looked like USB device tree: 1 Hub (480 Mb/s, 0mA) | U-Boot Root Hub | +-2 Hub (480 Mb/s, 2mA) | +-3 Vendor specific (12 Mb/s, 90mA) | FTDI FT232R USB UART AM00KE3E | +-4 Vendor specific (480 Mb/s, 2mA) | +-5 Hub (480 Mb/s, 100mA) | GenesysLogic USB2.1 Hub | +-6 Mass Storage (480 Mb/s, 500mA) JMicron On a successful try it looked like scanning usb for storage devices... 1 Storage Device(s) found Hit any key to stop autoboot: 0 U-Boot> usb tree USB device tree: 1 Hub (480 Mb/s, 0mA) | U-Boot Root Hub | +-2 Hub (480 Mb/s, 2mA) | +-3 Hub (480 Mb/s, 100mA) | | GenesysLogic USB2.1 Hub | | | +-6 Mass Storage (480 Mb/s, 500mA) | JMicron SABRENT 000000000000A | +-4 Vendor specific (12 Mb/s, 90mA) | FTDI FT232R USB UART AM00KE3E | +-5 Vendor specific (480 Mb/s, 2mA) Not sure if this is even relevant, but it does seem odd. Thanks for all your help! bob prohaska