From nobody Mon Jul 03 12:31:33 2023 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 4QvlfL0FN6z4l9xm for ; Mon, 3 Jul 2023 12:31:38 +0000 (UTC) (envelope-from fred@thegalacticzoo.com) Received: from nmtao201.oxsus-vadesecure.net (mta-231a.oxsus-vadesecure.net [15.204.3.4]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4QvlfK18WJz4MFT for ; Mon, 3 Jul 2023 12:31:37 +0000 (UTC) (envelope-from fred@thegalacticzoo.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=webcom.xion.oxcs.net header.s=mail1 header.b=WrSUlDUH; spf=pass (mx1.freebsd.org: domain of fred@thegalacticzoo.com designates 15.204.3.4 as permitted sender) smtp.mailfrom=fred@thegalacticzoo.com; dmarc=pass (policy=quarantine) header.from=thegalacticzoo.com DKIM-Signature: v=1; a=rsa-sha256; bh=/1qFBEW1UdANFhQQkJhc6lwm2NvIBAU9W+KXV1 UhSGQ=; c=relaxed/relaxed; d=webcom.xion.oxcs.net; h=from:reply-to: subject:date:to:cc:resent-date:resent-from:resent-to:resent-cc: in-reply-to:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:list-owner:list-archive; q=dns/txt; s=mail1; t=1688387495; x=1688992295; b=WrSUlDUHVUzxEGTD5LH5MSrKUL0byJvxICGuRKlRP p1qTFqvsv6GK19XV+/BltqPn1vXntX+dOFcPnKqGTp4Hxsbal3LU8KF7qqqro7cWQioR9rG 2oOV8NH5yg25GbYg/R69w9a8ojXgvedOAHm4zTP4UJV7T29moq3ClandtxPNOo/he+UoOu6 lpzUGMNtSqWGoLVnXoZ7/8PCW916lLfFOWaqgVw8PgBFBhY/RPkgidj12vpV3mQ3SI0ypnH x39rozWJaVrAJA7NM9oJ2zi9EuF6wCkc8a6xpvvWhau2wLm4O0DMPuXPXVakncK/wYnDZeD YAzFWnAy1ZYuFZNdw== Received: from proxy-17.proxy.cloudus.ewr.xion.oxcs.net ([76.14.239.229]) by oxsus2nmtao01p.internal.vadesecure.com with ngmta id fff726b2-176e5b7b4134844e; Mon, 03 Jul 2023 12:31:35 +0000 To: freebsd-arm@freebsd.org From: "Fred G. Finster" Subject: USB Flash drive booting from June 22,2023 RPI Snapshot FreeBSD 14.0 Message-ID: Date: Mon, 3 Jul 2023 05:31:33 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0 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=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Spamd-Result: default: False [-4.39 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.987]; DMARC_POLICY_ALLOW(-0.50)[thegalacticzoo.com,quarantine]; RWL_MAILSPIKE_EXCELLENT(-0.40)[15.204.3.4:from]; R_SPF_ALLOW(-0.20)[+ip4:15.204.3.4/30]; R_DKIM_ALLOW(-0.20)[webcom.xion.oxcs.net:s=mail1]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:16276, ipnet:15.204.0.0/17, country:FR]; MIME_TRACE(0.00)[0:+]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[15.204.3.4:from]; ARC_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_HAS_DN(0.00)[]; DKIM_TRACE(0.00)[webcom.xion.oxcs.net:+]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; TO_DN_NONE(0.00)[]; MID_RHS_MATCH_FROM(0.00)[] X-Rspamd-Queue-Id: 4QvlfK18WJz4MFT X-Spamd-Bar: ---- X-ThisMailContainsUnwantedMimeParts: N Hello and Happy 4th of July Holiday I downloaded this June 22, 2023 version of the  RPI snapshot and burned to a USB flash drive to test on my Raspberry Pi 4B with 8 GB https://www.freebsd.org/where/ https://download.freebsd.org/snapshots/arm64/aarch64/ISO-IMAGES/14.0/ https://download.freebsd.org/snapshots/arm64/aarch64/ISO-IMAGES/14.0/FreeBSD-14.0-CURRENT-arm64-aarch64-RPI-20230622-b95d2237af40-263748.img.xz Is there a recipe that some machine follow to build this image? Can I have that recipe to verify the build process?  What should I do about the It try to TFTP  boot an image,  I was not setup for yet.  I will google and find some docs and webpages to help me out. EFI boot manager: Cannot load any image Found EFI removable media binary efi/boot/bootaa64.efi ** Reading file would overwrite reserved memory ** Failed to load 'efi/boot/bootaa64.efi' No UEFI binary known at 0x00080000 EFI LOAD FAILED: continuing... Yes, I can take a working  bootaa64.efi file and replace this one version  Then see if I can boot my raspberry pi 4B. What else do you suggest to do to check or verify.  My system was booting the older version of FreeBSD 14.0 from my 500GB SSD.  See my blogpost for details.  Yes, snapshots of 14.0-CURRENT can have problems, so I just wish to share my experience. I am afraid I over looked some small simple detail that I did not change or setup.  My apology in advance. I am interested to learn how to use this nice 2023.01 U-BOOT and learn to debug by PXE booting the Raspberry Pi. Is there a  website tutorial about using U-BOOT>  to test and learn about your ARM64 Hardware?  RTFM manual Anyone else encountering this particular issue from a snapshot image? https://ghostbsd-arm64.blogspot.com/2022/02/booting-500-gb-ssd-on-freebsd-arm64-140.html https://ghostbsd-arm64.blogspot.com/2022/09/freebsd-140-compiling-kernel-for.html Sorry to share this long listing with details: Here is a a partial listing of the board dump  bdinfo command issued to 'U-BOOT>'  prompt lmb_dump_all:  memory.cnt  = 0x3  memory[0]      [0x0-0x3b2fffff], 0x3b300000 bytes flags: 0  memory[1]      [0x40000000-0xfbffffff], 0xbEFI boot manager: Cannot load any image Found EFI removable media binary efi/boot/bootaa64.efi ** Reading file would overwrite reserved memory ** Failed to load 'efi/boot/bootaa64.efi' No UEFI binary known at 0x00080000 EFI LOAD FAILED: continuing...c000000 bytes flags: 0  memory[2]      [0x100000000-0x1ffffffff], 0x100000000 bytes flags: 0  reserved.cnt  = 0x8  reserved[0]    [0x0-0xfff], 0x00001000 bytes flags: 0  reserved[1]    [0x7ef0000-0x7f0ffff], 0x00020000 bytes flags: 0  reserved[2]    [0x39c28000-0x3b2fffff], 0x016d8000 bytes flags: 0  reserved[3]    [0x3ac3c380-0x3b0fffff], 0x004c3c80 bytes flags: 0  reserved[4]    [0x3ee5c0a0-0x3ee5c164], 0x000000c5 bytes flags: 4  reserved[5]    [0x40000000-0xfbffffff], 0xbc000000 bytes flags: 0  reserved[6]    [0xfe100000-0xfe100fff], 0x00001000 bytes flags: 0  reserved[7]    [0x100000000-0x1ffffffff], 0x100000000 bytes flags: 0 devicetree  = board arch_number = 0x0000000000000000 TLB addr    = 0x000000003b0f0000 irq_sp      = 0x000000003ac40820 sp start    = 0x000000003ac40820 Early malloc usage: 878 / 2000 U-Boot> boot Card did not respond to voltage select! : -110 MMC Device 1 not found no mmc device at slot 1 MMC Device 2 not found no mmc device at slot 2 Device 0: Vendor: Verbatim Rev: PMAP Prod: ClickUSB             Type: Removable Hard Disk             Capacity: 14776.0 MB = 14.4 GB (30261248 x 512) ... is now current device Scanning usb 0:1... BootOrder not defined EFI boot manager: Cannot load any image Found EFI removable media binary efi/boot/bootaa64.efi ** Reading file would overwrite reserved memory ** Failed to load 'efi/boot/bootaa64.efi' No UEFI binary known at 0x00080000 EFI LOAD FAILED: continuing... BOOTP broadcast 1 DHCP client bound to address 192.168.1.7 (8 ms) *** Warning: no boot file name; using 'C0A80107.img' Using ethernet@7d580000 device TFTP from server 192.168.1.1; our IP address is 192.168.1.7 Filename 'C0A80107.img'. Load address: 0x1000000 Loading: T T T T T Abort missing environment variable: pxeuuid