From nobody Wed Oct 27 16:28:52 2021 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 21AD718109E5; Wed, 27 Oct 2021 16:29:02 +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 4HfYzd1jLDz3q9j; Wed, 27 Oct 2021 16:29:01 +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 19RGSrEe016115 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Wed, 27 Oct 2021 09:28:53 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.16.1/8.15.2/Submit) id 19RGSqwq016114; Wed, 27 Oct 2021 09:28:52 -0700 (PDT) (envelope-from fbsd) Date: Wed, 27 Oct 2021 09:28:52 -0700 From: bob prohaska To: freebsd-arm@freebsd.org, freebsd-ports@freebsd.org Cc: bob prohaska Subject: Re: Troubles booting Pi2 from USB using bootcode.bin method Message-ID: <20211027162852.GA16010@www.zefox.net> References: <20211025034332.GA8398@www.zefox.net> 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: <20211025034332.GA8398@www.zefox.net> X-Rspamd-Queue-Id: 4HfYzd1jLDz3q9j 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.90 / 15.00]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; WWW_DOT_DOMAIN(0.50)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[zefox.net]; AUTH_NA(1.00)[]; NEURAL_SPAM_SHORT(1.00)[1.000]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_SPF_NA(0.00)[no SPF record]; 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]; RCVD_COUNT_TWO(0.00)[2]; MID_RHS_WWW(0.50)[] X-ThisMailContainsUnwantedMimeParts: N On Sun, Oct 24, 2021 at 08:43:32PM -0700, bob prohaska wrote: > I've got an early Pi2B (not plus) that has been booting reliably > from a USB2 disk connected via a USB3 hub using just bootcode.bin > and timeout on the DOS partition of the microSD card. > It turns out the USB3 disk boots normally _provided_ the old USB2 disk remains connected. I didn't try that initially both because I didn't need both disks and because the boot order couldn't be obviously controlled. It turns out the new disk is discovered first and boots as desired, so the system is busy building an up-to-date world and kernel. There's room for a ports tree on this disk. Does the ports version of u-boot include support for the bootcode.bin-only mode of USB booting? Right now I'm using the version of bootcode.bin offered at https://www.raspberrypi.com/documentation/computers/raspberry-pi.html#special-bootcode-bin-only-boot-mode Without having the USB2 disk connected the serial console hangs with what looks like "cb" as the only output. It's unclear if u-boot is starting at all. The red and green LEDs remain lit, seemingly indefinitely. Thanks for reading, and any ideas. bob prohaska > >