Date: Tue, 4 Oct 2022 01:25:17 -0700 From: Mark Millard <marklmi@yahoo.com> To: bob prohaska <fbsd@www.zefox.net> Cc: Klaus K??chemann <maciphone2@googlemail.com>, freebsd-arm@freebsd.org Subject: Re: u-boot debug, was: Re: U-boot on RPI3, sees disk but won't boot it Message-ID: <1DE565E3-3906-4C53-83C8-EBC20A4E3C95@yahoo.com> In-Reply-To: <62F8D709-BBC3-41C4-B1A9-939B2001BA52@yahoo.com> References: <ABFDD634-5CB6-4DAE-B4DE-629CE7E4FE06@yahoo.com> <20221001193033.GA98348@www.zefox.net> <46226720-D867-4AD3-9559-A4365FAC28C4@yahoo.com> <6DB88FC9-629C-43E6-9673-32640FC547F7@yahoo.com> <20221002182049.GA2255@www.zefox.net> <5FFDAA6A-AD8C-4E40-A2EB-4082E5086679@googlemail.com> <38DFEB91-AC60-4FD1-8088-95B0A06C5E5D@yahoo.com> <EEC43DA1-6B68-4FDD-A68A-A3055E86E407@googlemail.com> <20221003004624.GA3381@www.zefox.net> <B32F06DD-DFAF-4CB7-A973-7C07846F6E8E@yahoo.com> <20221004001857.GA7109@www.zefox.net> <62F8D709-BBC3-41C4-B1A9-939B2001BA52@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I found a configuration that gets the RPi3 EDK2 and FreeBSD combination to have the serial console working. You can try booting and operating via the RPi3 EDK2 UEFI materials. However, microsd cards should still not be mounted/used from a FreeBSD that has been booted via RPi3 EDK2. Bluetooth is disabled as part of getting a working serial console. I ended up with a RPi3 EDK2 microsd card for use in booting that has: # mount -onoatime -tmsdosfs /dev/da3s1 /mnt # find /mnt -print /mnt /mnt/RPI_EFI.fd /mnt/bootcode.bin /mnt/config.txt /mnt/fixup.dat /mnt/start.elf /mnt/Readme.md /mnt/bcm2710-rpi-3-b-plus.dtb /mnt/bcm2710-rpi-3-b.dtb /mnt/bcm2710-rpi-cm3.dtb /mnt/firmware /mnt/firmware/Readme.txt /mnt/firmware/brcmfmac43455-sdio.txt /mnt/firmware/brcmfmac43455-sdio.bin /mnt/firmware/brcmfmac43455-sdio.clm_blob /mnt/firmware/LICENCE_bin+clm_blob.txt /mnt/firmware/brcmfmac43430-sdio.clm_blob /mnt/firmware/brcmfmac43430-sdio.txt /mnt/firmware/brcmfmac43430-sdio.bin /mnt/firmware/LICENSE_txt.txt /mnt/overlays /mnt/overlays/disable-bt.dtbo All but the 2 "overlays" lines are based on the content of: = https://github.com/pftf/RPi3/releases/download/v1.37/RPi3_UEFI_Firmware_v1= .37.zip disable-bt.dtbo is a copy of one from a RPi* firmware used for booting FreeBSD on RPi*s. It is not in the .zip file. I adjusted config.txt to indicate to use the disable-bt.dtbo : # more /mnt/config.txt arm_64bit=3D1 disable_commandline_tags=3D2 disable_overscan=3D1 enable_uart=3D1 uart_2ndstage=3D1 armstub=3DRPI_EFI.fd device_tree_address=3D0x1f0000 device_tree_end=3D0x200000 # # Local addition(s): dtoverlay=3Ddisable-bt (The file has a carriage returns at the end of each line. Some editors show such characters as ^M . The characters could be deleted if desired.) I'll note that the firmware/* content is likely of no use for FreeBSD at this point but I did not remove it. It should be okay to not have it present. I'll note that the output from "uart_2ndstage=3D1" does not actually display during the boot sequence. (Sent to the wrong internal UART, as if dtoverlay=3Ddisable-bt had not been used, from what I understand.) Using that microsd card in the RPi3B should try to boot. The EFI prompt will timeout and continue to the next stage (so far as it is successful, anyway). If it all works, it will get to the "login: " prompt. I'm not familiar with what the error reporting would be like if it also has troubles with your equipment. You hit the return key to explicitly continue at the EFI prompt. The Escape key can be used instead to get into the menu system for controlling the UEFI settings. If it gets far enough, the UEFI will try to find the EFI/BOOT/* on your USB media's msdosfs. If found, it will then load the FreeBSD loader and then start it --and things would then be back in familiar territory. The above actually boots via a default setting that likely should be replaced. The related menu/field nesting is: Device Manager Raspberry Pi Configuration Advanced Configuration System Table Selection <ACPI + Devicetree> Picking just Devicetree instead, then saving, and then exiting the nested menus via a sequence of Escape key presses, until back to the initial display, one can then select Reset and it will start over based on the new setting. The save actually updates an area in the RPI_EFI.fd file. (The issue is that the ACPI information is odd: Microsoft specific, not standard. So if the ACPI information is used things are possibly not complete/correct.) =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?1DE565E3-3906-4C53-83C8-EBC20A4E3C95>