From nobody Tue Jan 16 10:34:22 2024 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 4TDlkQ0l3sz57N6T for ; Tue, 16 Jan 2024 10:34:38 +0000 (UTC) (envelope-from andrew.hankinson@gmail.com) Received: from mail-wm1-x332.google.com (mail-wm1-x332.google.com [IPv6:2a00:1450:4864:20::332]) (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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4TDlkP4FjRz4jDQ for ; Tue, 16 Jan 2024 10:34:37 +0000 (UTC) (envelope-from andrew.hankinson@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-wm1-x332.google.com with SMTP id 5b1f17b1804b1-40e5f746ac4so61973505e9.1 for ; Tue, 16 Jan 2024 02:34:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1705401274; x=1706006074; darn=freebsd.org; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=QT36EaJEz2jENYZxmh3+MIRZS5Ug7p1klhzKqQn9+2A=; b=H6J7qEATCn2Lx81vYZOkSilwtPzjCtigIfUDs1w0UJ5SwI0rsBZTxGYkGhQFaJQ4a+ VFQkHfZinyYUY2VQaxvejcLMYSgRnikKRO0M0xwlekwZu7v1sfC4BW2JUkFHWJfiprsb 1TQQZm8QsY+5eqOY8cz42g69fhmlfoFGK0BYfyM0jKo5ML5LhGmaf0cPejiJ0MxEQha6 sGNVV7CBhqgfETn2SX+GmETSPHnUh62QnydB6+qqHGK3CpooXTVZp+AkzXfUfQJL1ikV JciwZa7M6jozmqaYE+WN2+7qPhl4vPX3pldb4I2zW7T8TaK9TJV34Bj6gRzczCkB1Q8S eRzA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1705401274; x=1706006074; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=QT36EaJEz2jENYZxmh3+MIRZS5Ug7p1klhzKqQn9+2A=; b=RyfJIpoE/mYGVhCy+waqCEq74pdedk52Xxnd8fnq7IaZrHn5C+vEctzQy14tYuFf9+ fivrbRsxF2OGPNki3EFNl7evcPTablMO+g0yPhDSMe4oG/abMMtyMdZZrR451dVA3F6s Q9jHwuEp96lAMeI1vt6kqTC7DXzDEjkHsfBGuKdMbPQdaftlGHn6uo0vVLvwYMRZPQa9 XzrcFdoIFg2j04LU8xMTnG5mZhajBLYTy877Eeb1uNm9BCSuRq1hM2UT0NWvzfh+dq5P Ix5uKP3VWVHmYmBs8tgPklDtKaAuLyh7o17LA+MX1FLLtR4qh47BfwlZZPsf1MEn1KB3 qmdQ== X-Gm-Message-State: AOJu0YwI/kVA9lAgfNiPJLu/YmlCThZeSSQYVnccrAmfVFucroNnOdFH HuzVPWG+wVl1TcYwnmLYHDdZjxmsjn0= X-Google-Smtp-Source: AGHT+IGKkn+c7wXBFQElxUFTqcoUFjb10XxCtXI8X2sjBavpeNnh4dqyuGlYpOEIUl6inMpRB6h+VQ== X-Received: by 2002:a05:600c:3646:b0:40e:6e67:36ac with SMTP id y6-20020a05600c364600b0040e6e6736acmr2820269wmq.52.1705401274058; Tue, 16 Jan 2024 02:34:34 -0800 (PST) Received: from smtpclient.apple ([2001:1600:10:100::65a]) by smtp.gmail.com with ESMTPSA id bv27-20020a0560001f1b00b00337b0374a3dsm2340436wrb.57.2024.01.16.02.34.33 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 16 Jan 2024 02:34:33 -0800 (PST) Content-Type: text/plain; charset=utf-8 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 (Mac OS X Mail 16.0 \(3774.100.2.1.4\)) Subject: Re: Nanobsd for RPI4 From: Andrew Hankinson In-Reply-To: Date: Tue, 16 Jan 2024 11:34:22 +0100 Cc: freebsd-arm@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <6803045E-76EE-47FA-A355-CADDE4E6BD65@gmail.com> References: <3c3c23dc-dd28-4c0c-984e-7654e115c1e2@madpilot.net> <53E50A6F-11A4-40D8-B71F-D742FBC06D29@gmail.com> To: Guido Falsi X-Mailer: Apple Mail (2.3774.100.2.1.4) X-Rspamd-Queue-Id: 4TDlkP4FjRz4jDQ X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; TAGGED_FROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] > On 16 Jan 2024, at 10:46, Guido Falsi wrote: >=20 > On 16/01/24 10:30, Andrew Hankinson wrote: >>> On 16 Jan 2024, at 10:03, Guido Falsi wrote: >>>=20 >>> On 16/01/24 09:52, Andrew Hankinson wrote: >>>> Hello, >>>> I saw a recent posting to this list about nanobsd for RPI3: >>>> Re: Nanobsd builds for rpi3 out of embedded blow up during build = >>>> lists.freebsd.org = >>>> favicon.ico = >>>> = >>>> I just wanted to chime in to say I am seeing the exact same thing = for a RPI4 build with both 14.0 release and 15.0 current. I asked about = it on the forums, but there didn=E2=80=99t seem to be any solution. >>>> Has anyone here managed to get a nanobsd build working? >>>=20 >>> I am using nanobsd with RPi3. Never tried RPi4. I did some = customization to the nanobsd scripts and configuration to get it working = though. >>>=20 >>> Last time I rebuilt my image was in mid december. I'm going to build = a new image in the next pair of weeks. >>>=20 >>> Is the problem limited to the boot code? >> I haven't been able to get past the boot code bit, but up until this = point it works OK. I've simply copied the RPI3.cfg file and changed a = few variables. >> My build stops with the following logs: >> # cat /usr/embedded/rpi4/_.cust.dos_boot_part >> + dos_boot_part >> + local 'd=3D/usr/local/share/u-boot/u-boot-rpi4' >> + local 'f=3D/usr/embedded/rpi4/_.fat' >> + rm -rf /usr/embedded/rpi4/_.fat >> + mkdir /usr/embedded/rpi4/_.fat >> + chdir /usr/embedded/rpi4/_.fat >> + cp /usr/local/share/u-boot/u-boot-rpi4/README = /usr/local/share/u-boot/u-boot-rpi4/metadata = /usr/local/share/u-boot/u-boot-rpi4/u-boot.bin . >> + touch uEnv.txt >> + cp '/usr/embedded/rpi4/_.w/boot/dtb/*.dtb' . >> cp: /usr/embedded/rpi4/_.w/boot/dtb/*.dtb: No such file or directory >> This seems to be a problem with the dos_boot_part() function in = /usr/src/tools/tools/nanobsd/embedded/common. >> Your code seems to bypass this and uses the rpi-firmware package = .dtbo files. >=20 > I was seeing problems simlar to what you are describing, so I wrote my = own function. >=20 >> So I guess my questions are: >> 1. What changed that the .dtb files are no longer created in the = regular build? >> 2. Should the dos_boot_part() function be changed to take the files = from the rpi-firmware pkg instead? >> Not being familiar with the nanobsd building process, I'm not really = sure what is the best way to go. >=20 > I wrote this code some time ago and I don't remember the details, = anyway my code does take the files from the pkg. >=20 > I took idea from the release scripts for aarch64 from: >=20 > src/release/release.sh > src/release/arm64/aarch64.conf > src/release/tools/arm.subr >=20 > which have more current code. Would you be willing to share your full nanobsd config file? Or is that = the only custom part you needed to get it working? >=20 > --=20 > Guido Falsi >=20