Date: Wed, 28 Sep 2022 10:57:41 -0700 From: Mark Millard <marklmi@yahoo.com> To: bob prohaska <fbsd@www.zefox.net> Cc: freebsd-arm <freebsd-arm@freebsd.org>, freebsd-uboot@freebsd.org Subject: Re: u-boot debug, was: Re: U-boot on RPI3, sees disk but won't boot it Message-ID: <62A7FD9D-DFAD-46B2-8681-F6EF0E5AC0DE@yahoo.com> In-Reply-To: <20220928172839.GA75564@www.zefox.net> References: <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> <C657BE65-ADCC-479B-B756-445D0825E0FA@yahoo.com> <E0BDFF06-3998-48E0-B04D-3B4A11F4A9AE@yahoo.com> <20220928045145.GB73356@www.zefox.net> <81F58716-72CE-45E8-951A-B7B92AD0FE95@yahoo.com> <20220928172839.GA75564@www.zefox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2022-Sep-28, at 10:28, bob prohaska <fbsd@www.zefox.net> wrote: > [removed Klaus from cc, added freebsd-uboot@freebsd.org]=20 > On Tue, Sep 27, 2022 at 10:45:36PM -0700, Mark Millard wrote: >>=20 >> There are almost 2 hours between 20:04:31 -0700 >> and the 21:51 when your Email arrived. >>=20 >=20 > The delay between compile and email seems ok.=20 >=20 >> None of the output that I reported as showing up >> shows in your report. YOu can look at: >>=20 >> = https://lists.freebsd.org/archives/freebsd-arm/2022-September/001804.html >>=20 >> to see the U-Boot output that I got (via use in >> an RPi4B). >>=20 >> Are you sure that the u-boot.bin on the msdosfs >> has the new content? >>=20 >=20 > I'm still doing something wrong, but haven't found it yet.=20 If the patch files are in place for what poudriere uses for /usr/ports/sysutils/u-boot-rpi-arm64/ , poudriere based port building should then work. Is there a log file of the port build output that you could post? For manual make activity one can use something like the script command to also have the output sent out to a log file. > After cleaninug up old files and re-running make and make=20 > install, find locates: The output during the make would be a good cross check on what is in the build and if the patches are being applied to a fresh extraction of the source code. > root@pelorus:~ # sum /boot/msdos/u-boot.bin > 4933 570 /boot/msdos/u-boot.bin Those 570's indicate the smaller file size. The larger size from being a debug build is likely to be more like 587. (Your and my checksums would be unlikely to match due to details of build environment differences that control some aspects of code generation. But the sizes should be similar.) The sum output, of itself, does not show file timestamps and more detailed size figures that would also be evidence. > root@pelorus:~ # sum = /usr/local/share/u-boot/u-boot-rpi-arm64/u-boot.bin > 4933 570 /usr/local/share/u-boot/u-boot-rpi-arm64/u-boot.bin >=20 > root@pelorus:~ # sum = /usr/ports/sysutils/u-boot-rpi-arm64/work/u-boot-2022.04/u-boot.bin > 4933 570 = /usr/ports/sysutils/u-boot-rpi-arm64/work/u-boot-2022.04/u-boot.bin >=20 > root@pelorus:~ # sum = /usr/ports/sysutils/u-boot-rpi-arm64/work/stage/usr/local/share/u-boot/u-b= oot-rpi-arm64/u-boot.bin > 4933 570 = /usr/ports/sysutils/u-boot-rpi-arm64/work/stage/usr/local/share/u-boot/u-b= oot-rpi-arm64/u-boot.bin >=20 > At the same time: > root@pelorus:~ # ls /usr/ports/sysutils/u-boot-rpi-arm64/files > 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 Did the build sequence re-extract the source code and apply all the patch files to the result? > There' still no additional output from u-boot, As expected, given the u-boot.bin is too small to be a debug build. Until you produce the bigger variant of the file, there will be no debug or other logging. Probably no reason to even copy over the smaller file variants to the boot media. > although with enough > re-trying the machine still boots:=20 >=20 > U-Boot 2022.04 (Sep 28 2022 - 09:02:56 -0700) >=20 > 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=20 > 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 >=20 > Device 0: Vendor: SABRENT Rev: 1214 Prod:=20 > Type: Hard Disk > Capacity: 953869.7 MB =3D 931.5 GB (1953525168 x 512) > [normal boot follows] >=20 > A file copying error on my part seems most likely. I'll try again > this afternoon. =3D=3D=3D Mark Millard marklmi at yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?62A7FD9D-DFAD-46B2-8681-F6EF0E5AC0DE>