From owner-freebsd-arm@freebsd.org Sun Jan 3 18:29:45 2021 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 6C7CD4D9CA8 for ; Sun, 3 Jan 2021 18:29:45 +0000 (UTC) (envelope-from ajm@ip-ether.net) Received: from balrog.mythic-beasts.com (balrog.mythic-beasts.com [IPv6:2a00:1098:0:82:1000:0:2:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4D86k05PCkz3nDl; Sun, 3 Jan 2021 18:29:44 +0000 (UTC) (envelope-from ajm@ip-ether.net) Received: from [5.83.10.113] (port=61651 helo=[10.0.30.30]) by balrog.mythic-beasts.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92.3) (envelope-from ) id 1kw88I-0002E0-Kn; Sun, 03 Jan 2021 18:29:42 +0000 Subject: Re: RPi4b 8GB 13.0-Current, XHCI broken, wrong U-Boot ? To: freebsd-arm@freebsd.org References: <007c8658-b7b6-6852-536c-9c36af64506b@ip-ether.net> <5B626DCC-6F7C-4554-803C-F488A1ED9BEB@googlemail.com> <56d10ea4-3284-3e4c-9521-8bf1008caa2b@ip-ether.net> <26D146B8-0362-4008-9A1F-A6CD6B1479BB@googlemail.com> <6610c9a3-1e61-b7e5-c537-3080dd7ee8ae@ip-ether.net> From: Andy McClements Cc: Emmanuel Vadot , =?UTF-8?Q?Klaus_K=c3=bcchemann?= Message-ID: Date: Sun, 3 Jan 2021 18:29:34 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1 MIME-Version: 1.0 In-Reply-To: <6610c9a3-1e61-b7e5-c537-3080dd7ee8ae@ip-ether.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BlackCat-Spam-Score: 9 X-Spam-Status: No, score=0.9 X-Rspamd-Queue-Id: 4D86k05PCkz3nDl X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of ajm@ip-ether.net designates 2a00:1098:0:82:1000:0:2:1 as permitted sender) smtp.mailfrom=ajm@ip-ether.net X-Spamd-Result: default: False [-2.50 / 15.00]; RCVD_TLS_ALL(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1098::82:1000:0:2:1]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[ip-ether.net]; ARC_NA(0.00)[]; SPAMHAUS_ZRD(0.00)[2a00:1098:0:82:1000:0:2:1:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[2a00:1098:0:82:1000:0:2:1:from]; RCVD_IN_DNSWL_MED(-0.20)[2a00:1098:0:82:1000:0:2:1:from]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:44684, ipnet:2a00:1098::/32, country:GB]; MIME_TRACE(0.00)[0:+]; MAILMAN_DEST(0.00)[freebsd-arm]; FREEMAIL_CC(0.00)[freebsd.org,googlemail.com] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jan 2021 18:29:45 -0000 On 03/01/2021 11:43, Andy McClements wrote: > HW: RPi4b 8GB, late 2020 purchase, Sept 3rd EEPROM > OS: > FreeBSD-13.0-CURRENT-arm64-aarch64-RPI-20201224-3cc0c0d66a0-255241.img.xz > Boot device: 128GB USB3 SSD > I am happy to say that, WITH PATCH D26853, all of these will > successfully allow FreeBSD 20201224 to boot from USB SSD. Also that the > vanilla 20201224 img (which I have checked includes the 20201201 > firmware) also works fine, WITH PATCH D26853. > > I have also double-checked that the current firmware release, 20201227, > with the patch, DOES NOT WORK. As previously reported, I just see a > crash-loop in U-boot, if attempting to boot from USB SSD. Further on this, I have just done another test by replacing only: bcm2711-rpi-4-b.dtb on the FreeBSD 13.0-CURRENT 20201224 img, with the one from the RPI firmware 20201227 release. This **allows booting from USB**, which fails on the stock 20201224 img. So it seems to me that patch D26853 **is not required**, if the upstream file is now working OK. HOWEVER, the 20201227 firmware release appears to introduce some other problem, as already reported if ALL the files on the DOS partition are replaced with those from 20201227, it results in a crash in U-boot. To summarise then, on the hardware mentioned above: 1. Vanilla FreeBSD-13.0-CURRENT-arm64-aarch64-RPI-20201224 " starting USB... Bus xhci_pci: probe failed, error -110 No working controllers found " Result: disk boot fails, RPi attempts to net boot. 2. Vanilla FreeBSD-13.0-CURRENT-arm64-aarch64-RPI-20201224 + REPLACE ONLY bcm2711-rpi-4-b.dtb with the version from the 20201227 release. "starting USB... Bus xhci_pci: Register 5000420 NbrPorts 5 Starting the controller USB XHCI 1.00 scanning bus xhci_pci for devices... 3 USB Device(s) found scanning usb for storage devices... 1 Storage Device(s) found" Result: disk boot succeeds 3. Vanilla FreeBSD-13.0-CURRENT-arm64-aarch64-RPI-20201224 + REPLACE ALL FIRMWARE FILES with the versions from the 20201227 firmware release. Result: U-Boot crashes: U-Boot 2020.10 (Dec 24 2020 - 04:18:29 +0000) DRAM: 7.9 GiB RPI 4 Model B (0xd03114) MMC: mmc@7e300000: 1, emmc2@7e340000: 0 Loading Environment from FAT... In: serial Out: serial Err: serial Net: eth0: ethernet@7d580000 PCIe BRCM: link up, 5.0 Gbps x1 (SSC) starting USB... Bus xhci_pci: probe failed, error -110 No working controllers found Hit any key to stop autoboot: 0 Card did not respond to voltage select! starting USB... Bus xhci_pci: probe failed, error -110 No working controllers found USB is stopped. Please issue 'usb start' first. "Synchronous Abort" handler, esr 0x96000004 elr: 000000000009bae0 lr : 00000000000919dc (reloc) elr: 000000003b278ae0 lr : 000000003b26e9dc x0 : 0000000b00000000 x1 : 0000000b00000030 x2 : 000000003aee9e00 x3 : fffffff53aee9d70 x4 : 000000003b2d30b0 x5 : 000000003aee9da0 x6 : 000000003b2d30c0 x7 : 000000003aee9dd0 x8 : 000000003ae4bd20 x9 : 0000000000000008 x10: 00000000ffffffd0 x11: 0000000000000006 x12: 000000000001869f x13: 00000000000069c4 x14: 0000000000000000 x15: 00000000fffffffe x16: 0000000000004110 x17: 0000000000000000 x18: 000000003ae58d90 x19: 0000000000000000 x20: 0000000000000000 x21: 000000003aee9db0 x22: 0000000000000000 x23: 0000000000000002 x24: 0000000000000000 x25: 0000000000000000 x26: 0000000000000028 x27: 0000000000000003 x28: 000000003b2e4e94 x29: 000000003ae4c1c0 Code: f85f0000 91004086 cb000063 8b000021 (f9400860) Resetting CPU ...