From nobody Wed Sep 28 04:51:45 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 4Mckc01gjVz4YNvg for ; Wed, 28 Sep 2022 04:51:44 +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 4Mckbz2SDMz3kwr for ; Wed, 28 Sep 2022 04:51:43 +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 28S4pkP7074027 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Tue, 27 Sep 2022 21:51:46 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.16.1/8.15.2/Submit) id 28S4pkUe074026; Tue, 27 Sep 2022 21:51:46 -0700 (PDT) (envelope-from fbsd) Date: Tue, 27 Sep 2022 21:51:45 -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: <20220928045145.GB73356@www.zefox.net> References: <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> <20220928015721.GA73356@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: X-Rspamd-Queue-Id: 4Mckbz2SDMz3kwr 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_SHORT(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-0.996]; 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 07:25:09PM -0700, Mark Millard wrote: > > Beyond enable_uart=1 there is, quoting from: [snip] > "uart_2ndstage=1" Also added to config.txt > > For the current purposes, dtdebug=1 probably does > not provide anything of interest. But it is > available to enable as well. Added to config.txt as well. In general there isn't much additional output from u-boot. On a successful try I see what begins as (I think) bootcode.bin output: ..... MESS:00:00:24.909927:0: Device tree loaded to 0x4000 (size 0x7374) MESS:00:00:24.918100:0: uart: Set PL011 baud rate to 103448.300000 Hz MESS:00:00:24.924351:0: uart: Baud rate change done... MESS:00:00:24.927765:0: uart: Baud rate change done... Next u-boot takes over U-Boot 2022.04 (Sep 27 2022 - 20:04:31 -0700) DRAM: 948 MiB RPI 3 Model B (0xa02082) Core: 69 devices, 10 uclasses, devicetree: board MMC: mmc@7e300000: 2 Loading Environment from FAT... In: serial Out: vidconsole Err: vidconsole Net: No ethernet found. starting 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 Hit any key to stop autoboot: 0 MMC Device 0 not found no mmc device at slot 0 MMC Device 1 not found no mmc device at slot 1 Card did not respond to voltage select! : -110 Device 0: Vendor: SABRENT Rev: 1214 Prod: Type: Hard Disk Capacity: 953869.7 MB = 931.5 GB (1953525168 x 512) ... is now current device Scanning usb 0:1... libfdt fdt_check_header(): FDT_ERR_BADMAGIC Card did not respond to voltage select! : -110 Scanning disk mmc@7e300000.blk... Disk mmc@7e300000.blk not ready Scanning disk usb_mass_storage.lun0... Found 3 disks Missing RNG device for EFI_RNG_PROTOCOL No EFI system partition BootOrder not defined EFI boot manager: Cannot load any image Found EFI removable media binary efi/boot/bootaa64.efi 1262604 bytes read in 38 ms (31.7 MiB/s) libfdt fdt_check_header(): FDT_ERR_BADMAGIC Booting /efi\boot\bootaa64.efi But, that's it. Is that what one would expect? Failed attempts are more terse: U-Boot 2022.04 (Sep 27 2022 - 20:04:31 -0700) DRAM: 948 MiB RPI 3 Model B (0xa02082) Core: 69 devices, 10 uclasses, devicetree: board MMC: mmc@7e300000: 2 Loading Environment from FAT... In: serial Out: vidconsole Err: vidconsole Net: No ethernet found. starting USB... Bus usb@7e980000: USB DWC2 scanning bus usb@7e980000 for devices... 6 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Hit any key to stop autoboot: 0 MMC Device 0 not found no mmc device at slot 0 MMC Device 1 not found no mmc device at slot 1 Card did not respond to voltage select! : -110 Device 0: unknown device Waiting for Ethernet connection... done. I imagined u-boot would be more talkative, similar to the MESS..... output from bootcode.bin The output from make reports ===> Applying extra patch patches for u-boot-rpi-arm64-2022.04_1 from /usr/ports/sysutils/u-boot-rpi-arm64/files/ No such line 209 in input file, ignoring Strangely, it doesn't report which patch didn't work. The directory contains patch-common_usb.c patch-common_usb__storage.c patch-lib_efi__loader_efi__console.c patch-common_usb__hub.c patch-include_configs_rpi.h rpi_arm64_fragment No idea whether it matters. Thanks for reading, bob prohaska