From owner-freebsd-arm@freebsd.org Sat Mar 27 21:49:16 2021 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id B14E05A9603 for ; Sat, 27 Mar 2021 21:49:16 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic307-55.consmr.mail.gq1.yahoo.com (sonic307-55.consmr.mail.gq1.yahoo.com [98.137.64.31]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4F7CCs2MfTz4kpw for ; Sat, 27 Mar 2021 21:49:12 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1616881751; bh=vnvnQzSD6a/5lAaMpBGnD1WQVYSFKuRlro/O1JA+FZg=; h=X-Sonic-MF:Subject:From:Date:To:From:Subject; b=PAzsmkmPhwh/YuQee9etiI01IbU9NkO0VYDq75BUFyqu5uO+NwR/jCZuxSiQ1mo4OmhiI30xq2JdcnXuFRF5/+ejejmfB2VCGbVGog96hHl+JbjymyqQLpy9hVRUa+T7pab1wGq7JIMWEUqhbO25ZxYLuuWVGhWqHKJo+v1gw38seoYhzSlKm+lPZIvsfHm9ov5lMJyul7vprOLsvBZVR2CNm10P/1RfkcZQpmzu1LFGpyCanvMcPtFIOE2ulG6ksClnbyfZ8LEna7ZEFiUHc6qZhb6V67DqOAyHHmUek3vQLf7G4nTf7YUMASstnZu2Pxmw3V+k16y3bPjrWt60Ag== X-YMail-OSG: gG7SiioVM1nmkyBHCTnUKvqfpu6wyYbCQeIp98LQlAm1ogdAvyetpyUZTIUHkqn xmn7Oae1FHureQ5BsREfU5Mvso15znVINvGIfbc6ei9ZaU4ZG1ez0Ij.CZv07aQ3NdAbmGbo4FFg LRnq1hyhGQSHKWbGQZ.JZ4O0jZi9nY4bmZIbPZjfgBtS91nmqPZobDIMz1ztrt6KmfPVwn4Noqej _ysF6wcKBR92z3Xn5d2Ztd249tTZX.u5ekbnXtUQ88ycyasLnHrWKMyr3Zq2etkhfr.RZsIwebCx iUnmYN4UcYlOkOHJJJnjoV6iVIkEBxYzf2M6m9bkORyZnnrRsaUEXXbh6_gsNLGN2hgEY9fb90H8 AiLWWq2L6TBUEMzyBFdOS2RiSOjUtuAaFY4L50QKDtN7q8xZT_YLmENRcU2CDjQRTUrz9WwzXO2e tqbNCOcZXQ3fDtyChEdwc1Txaoi3Bd5NI0B6BAK5WqWB7n.7r4CsojPHZmaBm1gtG4jR8ZpF7AA3 lJIoF3dH6iq6LUtfqhjV6YfwTf9qbKxg6_7sdqea5GhQ0VvxPIkIwKrS5FqLm2mazWYHASfd9fit Wl8SaRKlu1eaRdhvKSzrg8XQhv3IhizEAU8QHJ8AtbVSX1QCEhF5u4yBl8YQYLq7UB9mfy3ZwvLn yJBL8PhEr_.3HJtPsaojcGIaJbW3bOx7WQtz8BgnNQp3.UPLYHVPsZNFH7Q0F8ul17r6.kJ6jiOF btxZyMjNZNTZ1hQQKlBXort_LkvHvQcGQZPw5.nrKw3W8i2mU_D3XU0Y9_S74LaaLSxOkKUcH.1q mt0bFaHcnE4UsXG6ZvbLVZ.t247q9lztgIEwwTFPEWQ.ch.eFiWNib1yy0Wn7iTUKq3qTcxxM8iE KZdPUufi2GZtijbXLwJm_DxmrMod1qzimeOPE4OEvEFRytdAg81UEEuSLKT_Q.P2.4YtkcYot7sB 6gOwsQfWOTiu9idPzBO74DT9wO8tnY1r9BTq8Ye30oaAPIb7eOWUOC0Fw7_.SKUPRjAKirbINsrV oa3rZ38_ZjZdgZFaqcChuxcsy.SHk4H3e3RjkrJ3UlKdysRbISi8ChBjGgSNOlePe.UcyI1xVpMH Z87yThkJk3rUyE_UyRfd6SXNnLmkOqDabFqJlHSyhh.orr1qA6VcT_eGA417qp7TC2TuWp9M.rdP u0XHLMI6KW2DQFUfWsIfXBDSKvuv8DPIRLgRSB3l89EBiXrPN8RuWY9FE964VkbkGaOBs2jl_2dt fWo.A5GjlqnYMXnU5PwRq_NKWQ1R9Dj.5IFYmUhravYhMYJ50NqYRHQY5BZ2F95L1ab6h_KIn6Ko 0_GXFbK6Xa1Z_0N_izxOeQ4GwVXVzHEFhJN4PW2g6oHbSM.sQPFer6X6UoqFZGPs5KjQDfUQGkeA MwQzkuDSbO70BM7UPHOEH1GyIrn5j7t6crkp78_lhFo1JaRl6YPFyjl0uZoHw8siQjNXLAR77thD SvJAx4NMoMO0wDxexstHaufsMxfdbyF50.L8nL3Z8o6MrWVAEs3RnHxc8Tn.rx39C5EC_0_OfhCw UWlOwhyc057HyNQAqIryfg_MH2nAkm_HfHYDCManEhbY..WOpRxlVRS6TvIHX3eOnmz54TEejW7L YH31xLYCnz3v4t9kxEqDpZ50a9C4_3ibgOHTuTGeywhUnbRV7XY9ZZEq2eVcCcxANeZcmwho4QPE WiFtPaL100REJdfO9mdYaZusjeldtdXT5k6Kb.5k1BP6GUnZoesu_GO.JHdDJWkrCyYcClJjVl1. CMzkNLppyTxZZwyhF5HwF4z5EojbH24F660V0WYxOH8UBJWtV_dQXFCFGAmYY17.R0Jfu5hRI55. jebSMsC5hpH9t59uuWVJ_ehUEVOrJCgwoaJjTh04iIgqT_NCxjXsKrsTkOMovXEzuOaqs3grDeaQ oPNFxQYHfumuJWwvR5GonJonMe81sWj9TmEExvRzdtJKhO0XiTlc41cX_DHmNCdXqPkaN4W6DF71 uc.E5hQH_aEwwgLbte6gBro22p6yij6EPyWw4iM4Xusm5Y0YzbcetY48IZpVu4GTe6ZFHkbzzqmi .iSEMtebpmJiE0cMRi0K8ynKxb9hgzRaeMYS.RcSNQCjYvZTAfdqZg3ciN0gSsq603luJoYurJWn 3pdNnrq9xRLDYRNRWa.UcLRvPBPzGgrXwYhIjf9tg_24q8VcwKDLVZ2AoAHgVaXpUASPEvs7D21Y oWDtQiYdCnRmdfL0aWDx4ICxCuqecUugiBX49IFi87V50fWZttJgc_A37MVWyvuc0aGc87TWGiuF mbkc_O6F_FSzbTQNW2adlORgKYJw7llbc2.lLKqbS0Pm5tWP2mV49XLKq0pJ2D9zLeJGfwfUsafG 1HpSUT6EfW_EpM5If9VSaMqqBnvBxVrO3sN7oYVP0DLOl9bRwjwgV4KKqZyobkAuyaQ2N.ZcXG1e iTBswJlBo0zPuJqQg_V1PSLcv_yWLlqPLgreUllMYXdH6nh5iZR.nPSsDr9UXlyUeYnWsRfn2WwA Q9dMFM.KSALyOpOxZQTFSOThp.dYtayqxB3qAbHWmVcBBSB343_1JK9GAeYxUDGN6WMTCwuFgdPd U X-Sonic-MF: Received: from sonic.gate.mail.ne1.yahoo.com by sonic307.consmr.mail.gq1.yahoo.com with HTTP; Sat, 27 Mar 2021 21:49:11 +0000 Received: by kubenode570.mail-prod1.omega.gq1.yahoo.com (VZM Hermes SMTP Server) with ESMTPA ID 74ab3ef1038bc19cf1978bb5bb0e94a8; Sat, 27 Mar 2021 21:49:08 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\)) Subject: Re: Any good alternative to Raspberry for Arm64? From: Mark Millard In-Reply-To: <21BE83BC-0667-44F7-83E4-1664A2BC6017@icloud.com> Date: Sat, 27 Mar 2021 14:49:08 -0700 Cc: freebsd-arm@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <2C868C60-80CB-4A4A-A12B-9CC0F3A1F531@yahoo.com> References: <21BE83BC-0667-44F7-83E4-1664A2BC6017@icloud.com> To: Andrew Mitchell X-Mailer: Apple Mail (2.3654.60.0.2.21) X-Rspamd-Queue-Id: 4F7CCs2MfTz4kpw X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.50 / 15.00]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[yahoo.com]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; DKIM_TRACE(0.00)[yahoo.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FREEMAIL_TO(0.00)[icloud.com]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/20, country:US]; RBL_DBL_DONT_QUERY_IPS(0.00)[98.137.64.31:from]; DWL_DNSWL_NONE(0.00)[yahoo.com:dkim]; SUBJECT_ENDS_QUESTION(1.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; SPAMHAUS_ZRD(0.00)[98.137.64.31:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[98.137.64.31:from]; RWL_MAILSPIKE_POSSIBLE(0.00)[98.137.64.31:from]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-arm] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Porting FreeBSD to ARM processors List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Mar 2021 21:49:16 -0000 On 2021-Mar-27, at 10:26, Andrew Mitchell via freebsd-arm wrote: > Hi everyone, > I've seen that there are arm machines for FreeBSD other than = Raspberry. I've been using it with 14.0-CURRENT, and my skills are too = limited for patching it. So, I've decided to find a machine on which a = RELEASE or STABLE version would work. To my knowledge, and after many = tries, it seems that there are no FreeBSD working smoothly on RPI4 B.=20 > So, if you have any suggestions for a working FreeBSD on any machine, = I'd be grateful. > I won't discard 14.0 CURRENT, as I've done quite a few things which = were much fun. It's just for getting other experiences. The only aarch64 images with a pre-supplied u-boot (or whatever all is involved beyond FreeBSD itself) in the modern available images are: aarch64 RPI aarch64 PINE64 aarch64 PINE64-LTS aarch64 PINEBOOK aarch64 ROCK64 aarch64 ROCKPRO64 Beyond those requires establishing an appropriate u-boot(+) on the media. It is not clear if you are comfortable with doing such activity. If not, you may be limited to the above alternatives if you are to use FreeBSD. Unless you start from scratch in order to update, as far as I know you are always responsible for updating u-boot on media once the initial u-boot becomes too old to work well. So, long term I'm not sure that you can avoid dealing with u-boot updates if from-scratch-updates is too extreme to deal with. You have not made clear if you have RAM size or other requirements that could limit the possibilities. Do you want to avoid doing your own buildworld buildkernel installkernel installworld activity going forward vs. using a form of pkg update that also updates the operating system? (This might go with avoiding patch activity.) Probably within the next couple of weeks the 13.0-RELEASE builds of the above should become available. For now there is the 13.0-RC3 . When I tested a microsd card with the image dd'd to it, it booted the 8 GiByte RPi4B just fine. I've not tried a Rock64 image but probably could. (I normally do my own non-debug builds of main [14].) I do not have working hardware for the others in the above list. Since you have one of the above devices, if you get it working temporarily you can use it to help bootstrap a different type of device if you are switching, such as installing pre-built ports that supply u-boot materials that you could dd to media. Otherwise you might be making the media via a different operating system. The list of u-boot ports is long but a lot of them are for older devices. (u-boot-master is material shared by the u-boot's for devices. The ones with *qemu* names are not for hardware. I've not tried to avoid listing armv7/armv6 contexts as well.) /usr/ports/sysutils/u-boot-a13-olinuxino /usr/ports/sysutils/u-boot-a64-olinuxino /usr/ports/sysutils/u-boot-bananapi /usr/ports/sysutils/u-boot-bananapim2 /usr/ports/sysutils/u-boot-beaglebone /usr/ports/sysutils/u-boot-chip /usr/ports/sysutils/u-boot-clearfog /usr/ports/sysutils/u-boot-cubieboard /usr/ports/sysutils/u-boot-cubieboard2 /usr/ports/sysutils/u-boot-cubox-hummingboard /usr/ports/sysutils/u-boot-duovero /usr/ports/sysutils/u-boot-firefly-rk3399 /usr/ports/sysutils/u-boot-imx-serial-loader /usr/ports/sysutils/u-boot-master /usr/ports/sysutils/u-boot-nanopi-a64 /usr/ports/sysutils/u-boot-nanopi-m1plus /usr/ports/sysutils/u-boot-nanopi-neo /usr/ports/sysutils/u-boot-nanopi-neo-air /usr/ports/sysutils/u-boot-nanopi-neo2 /usr/ports/sysutils/u-boot-olimex-a20-som-evb /usr/ports/sysutils/u-boot-olinuxino-lime /usr/ports/sysutils/u-boot-olinuxino-lime2 /usr/ports/sysutils/u-boot-olinuxino-lime2-emmc /usr/ports/sysutils/u-boot-orangepi-one /usr/ports/sysutils/u-boot-orangepi-pc /usr/ports/sysutils/u-boot-orangepi-pc-plus /usr/ports/sysutils/u-boot-orangepi-pc2 /usr/ports/sysutils/u-boot-orangepi-plus-2e /usr/ports/sysutils/u-boot-orangepi-r1 /usr/ports/sysutils/u-boot-orangepi-zero /usr/ports/sysutils/u-boot-orangepi-zero-plus /usr/ports/sysutils/u-boot-pandaboard /usr/ports/sysutils/u-boot-pcduino3 /usr/ports/sysutils/u-boot-pine-h64 /usr/ports/sysutils/u-boot-pine64 /usr/ports/sysutils/u-boot-pine64-lts /usr/ports/sysutils/u-boot-pinebook /usr/ports/sysutils/u-boot-pinebookpro /usr/ports/sysutils/u-boot-qemu-arm /usr/ports/sysutils/u-boot-qemu-arm64 /usr/ports/sysutils/u-boot-qemu-riscv64 /usr/ports/sysutils/u-boot-riotboard /usr/ports/sysutils/u-boot-rock-pi-4 /usr/ports/sysutils/u-boot-rock64 /usr/ports/sysutils/u-boot-rockpro64 /usr/ports/sysutils/u-boot-rpi /usr/ports/sysutils/u-boot-rpi-0-w /usr/ports/sysutils/u-boot-rpi-arm64 /usr/ports/sysutils/u-boot-rpi2 /usr/ports/sysutils/u-boot-rpi3 /usr/ports/sysutils/u-boot-rpi3-32 /usr/ports/sysutils/u-boot-rpi4 /usr/ports/sysutils/u-boot-sifive-fu540 /usr/ports/sysutils/u-boot-sinovoip-bpi-m3 /usr/ports/sysutils/u-boot-sopine /usr/ports/sysutils/u-boot-sopine-spi /usr/ports/sysutils/u-boot-tools /usr/ports/sysutils/u-boot-utilite /usr/ports/sysutils/u-boot-wandboard As I remember, there are some variations in how much room was needed for u-boot (plus possibly more dd'd to a separate places). So partition layout can be part of what has to be figured out. (Unless one has an idea of the worst case and just sets up to allow for it even when it might not actually be in use for a specific device.) The Rock64's instructions (from the README) indicate: To install this bootloader on an sdcard just do: dd if=3D/usr/local/share/u-boot/u-boot-rock64/idbloader.img = of=3D/path/to/sdcarddevice seek=3D64 bs=3D512 conv=3Dsync dd if=3D/usr/local/share/u-boot/u-boot-rock64/u-boot.itb = of=3D/path/to/sdcarddevice seek=3D16384 bs=3D512 conv=3Dsync Note the seek for the u-boot.itb dd. The size of the 2 files that are dd'd are shown below: # ls -Tld /usr/local/share/u-boot/u-boot-rock64/* -rw-r--r-- 1 root wheel 359 Jan 29 12:14:54 2021 = /usr/local/share/u-boot/u-boot-rock64/README -rw-r--r-- 1 root wheel 103675 Jan 29 12:14:54 2021 = /usr/local/share/u-boot/u-boot-rock64/idbloader.img -rw-r--r-- 1 root wheel 779132 Jan 29 12:14:54 2021 = /usr/local/share/u-boot/u-boot-rock64/u-boot.itb (I've no clue how close this may be to worst-case spread of u-boot + other-materials.) I'll note that the RPi* do not use u-boot or other materials in such an area. I've used this to have one media that boots both an RPi* and another type of device: I installed the alternate's u-boot/whatever as well as RPi* capable materials, both using the same UFS root file system. I used labels and such to avoid machine specific fstab contents and the like. I took care with any environment specific content in FreeBSD, not much for my use that needs to be adjusted for swapping where the media is used. I used a PINE64 (non-LTS) for a lot of years before it finally failed. I have access to a Rock64 and some RPi*'s as far as aarch64 small board computers go. The Rock64 has worked well but my way of mixing a USB3 SSD, removable eMMC (removable while powered off), and microsd card use on it is not a normal configuration. But it means that I have the microsd card slot available for fiddling with microsd cards any time that I want: not normally used in booting or in standard operation. =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)