Date: Thu, 21 May 2020 13:44:48 +0100 From: Edward Tomasz =?utf-8?Q?Napiera=C5=82a?= <trasz@freebsd.org> To: Oleksandr Tymoshenko <gonzo@bluezbox.com> Cc: Gordon Bergling <gbergling@googlemail.com>, freebsd-hackers@freebsd.org Subject: Re: Building arm64 image for booting in qemu Message-ID: <20200521124448.GA1474@brick> In-Reply-To: <20200521022956.GA32686@bluezbox.com> References: <20200520165024.GA2695@lion.0xfce3.net> <20200521022956.GA32686@bluezbox.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 0520T1929, Oleksandr Tymoshenko wrote: > Gordon Bergling via freebsd-hackers (freebsd-hackers@freebsd.org) wrote: > > Greetings, > > > > I am currently try to setup a crossbuild for arm64 to test some > > local changes. I use the following steps to create the image > > after crossbuilding arm64 on amd64. These steps were taken from > > the arm64_build.sh found at the FreeBSD wiki. > > Hi Gordon, > > I believe that script is very outdated in several areas. It refers > to boot1.efifat which is not boot1.efi but a FAT image that contains > boot1.efi as EFI\BOOT\bootaa64.efi. Also current version of u-boot-qemu > looks for DTB file which is not provided by the script (probably it was > built into u-boot before). We use both u-boot-qemu-arm (for armv7) and u-boot-qemu-arm64 packages on CI; they don't seem to depend on any external DTB. You are right about boot1.efi, though. The arm64 part of the build script used on CI (https://github.com/freebsd/freebsd-ci/blob/master/scripts/build/build-test_image-head.sh) looks like this: mkdir -p efi/EFI/BOOT cp -f ufs/boot/loader_lua.efi efi/EFI/BOOT/bootaa64.efi sudo makefs -d 6144 -t msdos -s 50m -Z efi.img efi mkimg -s gpt -f raw \ -p efi:=efi.img \ -p freebsd-swap/swapfs::1G \ -p freebsd-ufs/rootfs:=ufs.img \ -o ${OUTPUT_IMG_NAME} [..]
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20200521124448.GA1474>