From owner-freebsd-arm@freebsd.org Mon May 18 13:45:58 2020 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 433952CB15F for ; Mon, 18 May 2020 13:45:58 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: from out1.migadu.com (out1.migadu.com [91.121.223.63]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 49QgJh0tcxz3XGN for ; Mon, 18 May 2020 13:45:55 +0000 (UTC) (envelope-from greg@unrelenting.technology) Date: Mon, 18 May 2020 13:45:47 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=unrelenting.technology; s=default; t=1589809548; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=kwyzpLELiTcBJciiYkGNDvL7uoIwptKEI+RjbA2PhTo=; b=i//0XOwZShKMGePTVNuhNyapLp+KpMjFYoS1mW6bEZXvacvwYSzl4UI6H2zA+wIfoS3x/r u3X0gEBocfD8uvOKhVyv71OJpNvD9XC8Y+kDqRdWrbNmNdWTh7iiH6B58e0dFhpCw/cCYV mwCYPag28LskMmEdqsH/tGt9LZjqh4U= X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: myfreeweb To: Dan Kotowski , John-Mark Gurney CC: "freebsd-arm@freebsd.org" Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X In-Reply-To: <3nsQUg1Gm4VFYfpHVELk6PWaHyYNb3CoyoKnLV55_3VR48tr90bhaseG3sJg007L8czZ4mXUmR_YMQvYVdMbUs1bsoqGtZp5d17FqYT6b-o=@a9development.com> References: <72D47662-240E-4851-844A-A4F92F18B3F2@unrelenting.technology> <20200516051207.GT4213@funkthat.com> <3nsQUg1Gm4VFYfpHVELk6PWaHyYNb3CoyoKnLV55_3VR48tr90bhaseG3sJg007L8czZ4mXUmR_YMQvYVdMbUs1bsoqGtZp5d17FqYT6b-o=@a9development.com> Message-ID: <7AFDA7E0-82EC-4CD2-BB03-B7E33D019EDA@unrelenting.technology> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Score: -0.10 X-Rspamd-Queue-Id: 49QgJh0tcxz3XGN X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=unrelenting.technology header.s=default header.b=i//0XOwZ; dmarc=pass (policy=none) header.from=unrelenting.technology; spf=pass (mx1.freebsd.org: domain of greg@unrelenting.technology designates 91.121.223.63 as permitted sender) smtp.mailfrom=greg@unrelenting.technology X-Spamd-Result: default: False [-1.89 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[unrelenting.technology:s=default]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:91.121.223.63]; MIME_GOOD(-0.10)[text/plain]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[unrelenting.technology:+]; DMARC_POLICY_ALLOW(-0.50)[unrelenting.technology,none]; NEURAL_HAM_SHORT(-0.89)[-0.888]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:16276, ipnet:91.121.0.0/16, country:FR]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 May 2020 13:45:58 -0000 On May 18, 2020 1:01:53 PM UTC, Dan Kotowski wrote: >After a solid 16hrs this weekend, I can confirm that the pre-built images= do NOT "just work", at least not with SolidRun's HoneyComb version rev 1= =2E4=2E > >The 12=2E1 arm7 GENERICSD image fails to boot=2E The included EFI/BOOT/bo= otarm=2Eefi fails to load=2E I dropped in a copy of EFI/BOOT/bootarm64=2Eef= i from the aarch64 image, but that failed to handoff the process properly= =2E Tested with both u-boot and UEFI=2E Why would you even try 32-bit? >The 12=2E1 aarch64 memstick installer iamge fails out trying to mount the= UFS partition and drops into the mountroot> shell with error 19=2E Listing= GEOM managed disk devices returned an empty list=2E What devices does the boot log show? No xhci I guess, how about pci, sdhci= ? >My silicon is rev 1=2E4 so I have to use the SD slot for the firmware lay= er, which is a mild inconvenience because I can't use that slot for an OS i= amge (https://github=2Ecom/SolidRun/lx2160a_build/issues/36#issuecomment-62= 9865674)=2E The comment there says silicon rev 2 starts with board rev 1=2E5, but linu= x4kix on Twitter said the 1=2E4 board is rev 2 silicon! >Unfortunately that's where I ran out of time=2E I spent most of the time = tracing and tweaking SolidRun's build scripts, testing various combinations= of firmware builds and boot images, and learning my way through both the u= -boot and UEFI implementations=2E Please don't waste time on u-boot=2E >Barring other simple ideas, my next step is to make buildworld for TARGET= =3Darm64 TARGET_ARCH=3Daarch64, drop that on an NVMe gumstick, and see if I= can get that booted=2E You can just dd the memstick to an nvme or sata drive as well=2E