From nobody Mon May 16 13:20:54 2022 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 1C5261AEDA64 for ; Mon, 16 May 2022 13:20:55 +0000 (UTC) (envelope-from danfe@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "freefall.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4L20Hp74Nmz4s02; Mon, 16 May 2022 13:20:54 +0000 (UTC) (envelope-from danfe@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1652707255; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=HAFWuBJ3gLHz3oktEWGsUHrwLYO2FEoJkGiUAh2eax0=; b=u2GmcrPIH0wwPKSO++0EcoHYd641H4NOmagCpqQpFbxkAce7MnWXkpX77aES5jd66c+Zcr 3lAyji7WasjkX+rQ4Rikvygb5+nV2vEOr+YJHk1xkrmPDYcraL/XmU0F4ibmrLrNeYTagF jQdG4I7/Bqq86k+WqYMUT5OM4C0DzpBsJKXJZqryTAkQw6XPg5cXGEu3B26BOLwyMf1smz vGYsMC4KVXEKAy8U7ZJc9uJuceWvzUqqK8fo4Monp8czBo43EnyTEABj3h2huo7yfdIYsq SJnuA8SF8UogV4eZIB5PmT1R1nyCpOpUvW2wRb61k+wkxTDeorknJfIc7rffwg== Received: by freefall.freebsd.org (Postfix, from userid 1033) id DCF761D16D; Mon, 16 May 2022 13:20:54 +0000 (UTC) Date: Mon, 16 May 2022 13:20:54 +0000 From: Alexey Dokuchaev To: Emmanuel Vadot Cc: Micha?? G??rny , freebsd-arm@freebsd.org Subject: Re: Hang while trying to boot armv7 on qemu-system-arm Message-ID: References: <20220516112022.d806878fff7fb35d1decd774@bidouilliste.com> 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=us-ascii Content-Disposition: inline In-Reply-To: <20220516112022.d806878fff7fb35d1decd774@bidouilliste.com> ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1652707255; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=HAFWuBJ3gLHz3oktEWGsUHrwLYO2FEoJkGiUAh2eax0=; b=i6DPIpyGTMg0SvyEm2rT4+I0ZQhmWHHlNiIjWmOrpeXykSbfjo97GpgUw7oUg03fag+SsA 32YNJZjsvrqFVaftpon2DzxbnnwZPM2P+X2Tp15ZmjPJxmS4A2f9QGQz1KrkWDFCePJcVy q5av2410sHK4all1lq7egdF9PmvUVbdseAseRsRkpObUsnXbdsOzvGI+iTaRy+vo8BCwSv jNtJq2f80QGYENkX76AuHLDQiXbG5SDkCESf6tC8LhAm3WOorpiTnyrZYOQSItuWYm2QSq viDyR2NYG/Smg5+VWYV4kmIFNyNZ/EuusoYmCt6VxNECnNj+QPJcrM84fqLA/Q== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1652707255; a=rsa-sha256; cv=none; b=dXDgP7YeKBoYuuGSEam0zEFkeFMNnLB8sLf5xnolqUatVQqY5Bsc1nWxPVyI+rdJERvlBH rlVuX5IUZGoyTdigrhPpr/K8LCyPcqdn6SNqe8wRAyDnjfQIIpxOruCZgJxY9ux0dW/yNw Z2AkNQCatFL3aW9d3/nezdh/QDHXUxRpcqetEdr2ZI3p0sAV5q8gNEPs1ALsPoWZHtd9gL pE7twlwOHSdFTY7V5+qVzI1NP6Mn5dRVH/RqkZP2CfXmCvteTQ1e5V2khKttZKYIyrQNLp Snf6m2lSp3WdrQYp4TaBIRBWg2BXC0JNxOCuUHLOThDNIg2ob5VvtFwWh23Wqw== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N On Mon, May 16, 2022 at 11:20:22AM +0200, Emmanuel Vadot wrote: > On Mon, 16 May 2022 09:11:05 +0000 Alexey Dokuchaev wrote: > > > ... > > > Hit [Enter] to boot immediately, or any other key for command prompt. > > > Booting [/boot/kernel/kernel]... > > > Using DTB provided by EFI at 0x47dfd000. > > > Kernel entry at 0x57e00180... > > > Kernel args: (null) > > > > I've just tried following the same wiki recipe with GENERICSD images > > for 12.3 and 13.1-RC4, with the same outcome, regardless of the QEMU > > version. How to proceed from here? Is wiki recipe missing important > > details? If it works for someone, could you guys share exact versions > > of QEMU, U-Boot, FreeBSD version and image type you're using? Thanks, > > GENERICSD doesn't have the QEMU u-boot. Hmm, interestingly, `sysutils/u-boot-qemu-arm/pkg-descr' doesn't mention this, and suggests that $ qemu-system-arm -M virt -m 512m -nographic \ -bios /usr/local/share/u-boot/u-boot-qemu-arm/u-boot.bin \ -hda FreeBSD-13.0-CURRENT-arm-armv7-GENERICSD-20200409-r359731.img should be enough to boot the GENERICSD image in QEMU. Had something changed from 20200409 to present days? Side question: why the same u-boot.bin file has to be baked inside the image and passed via -bios argument? > We cannot add it as it have the same name than the u-boot file for > RPI-B. > So what you need to do is to pkg install u-boot-qemu-arm and copy the > u-boot.bin from there in the image. Okay, so I've mdconfig'ed the image, mounted -t msdosfs /dev/md0s1, and copied /usr/local/share/u-boot/u-boot-qemu-arm/u-boot.bin onto it, but this didn't fix the boot for me. Is there anything else needed, like config.txt file or something? On a larger scale, can you or other folks with sufficient ARM knowledge update relevant ports' descriptions, wiki recipes, and other doc bits on how to reliably get working FreeBSD/arm with QEMU in 2022? Thanks. ./danfe