From owner-freebsd-arm@freebsd.org Mon Dec 23 14:38:20 2019 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 04B721C96D7 for ; Mon, 23 Dec 2019 14:38:20 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.blih.net", Issuer "mail.blih.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 47hMQz20mJz3G7H for ; Mon, 23 Dec 2019 14:38:18 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) by mail.blih.net (OpenSMTPD) with ESMTP id dfef284f; Mon, 23 Dec 2019 15:38:17 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s=mail; bh=K5kTOPQOJw7C6jwurezQiCIH/Jg=; b=ZNcdF11+Pzpv7SsX1HfVvQToaxwB zrhJGZhg51XXWVw8ocTFgkqtOC9ASuyCvP1/JkZFeUfQGO1s7eCp6QGI93PGJ7lP o3w0PF53uG7GizJ4PxmIPA6IHuRNsv9ulOFjGga+RlozS8G7PX13b+HzvWE56Tos qpto4tqesY5miBo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; q=dns; s= mail; b=KlskTY86cCQ6PIlDMfodjOL0l4675mnjpU8A2CdFONTztehek8GSPkLh dcBWn++Anv3AR7FdGwmXk3naP47gtFoxQ32MQZhvTryv8aETQXI69OTwe6rFrtnG H5PqSupiP9rmMCpl1qU2ZkHL6Dd6hVtPCyOI2K/cGxogAazRz5E= Received: from sonic.home.blih.net (j1a01-1-78-205-69-41.fbx.proxad.net [78.205.69.41]) by mail.blih.net (OpenSMTPD) with ESMTPSA id 470a3e99 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Mon, 23 Dec 2019 15:38:17 +0100 (CET) Date: Mon, 23 Dec 2019 15:38:16 +0100 From: Emmanuel Vadot To: Mark Millard Cc: freebsd-arm , Peter Jeremy Subject: Re: Attempt to update Rock64 to head -r355976 failed to boot afterwards, anyone have a recent FreeBSD booting a Rock64? Message-Id: <20191223153816.4e532acede0605a0c868a8e4@bidouilliste.com> In-Reply-To: <0AADC2F5-9867-40E7-B4C0-139CA16A3974@yahoo.com> References: <78081E30-3758-46F3-A228-02B29CDAA6A6.ref@yahoo.com> <78081E30-3758-46F3-A228-02B29CDAA6A6@yahoo.com> <20191222113844.9385de125afd10e86358bc98@bidouilliste.com> <3C550401-A5BF-441E-81E6-29D5D917302B@yahoo.com> <0AADC2F5-9867-40E7-B4C0-139CA16A3974@yahoo.com> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; amd64-portbld-freebsd13.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 47hMQz20mJz3G7H X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bidouilliste.com header.s=mail header.b=ZNcdF11+; dmarc=none; spf=pass (mx1.freebsd.org: domain of manu@bidouilliste.com designates 212.83.177.182 as permitted sender) smtp.mailfrom=manu@bidouilliste.com X-Spamd-Result: default: False [0.67 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[bidouilliste.com:s=mail]; RECEIVED_SPAMHAUS_PBL(0.00)[41.69.205.78.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.11]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip4:212.83.177.182/32:c]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[bidouilliste.com]; NEURAL_HAM_LONG(-0.51)[-0.512,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[bidouilliste.com:+]; NEURAL_HAM_MEDIUM(-0.34)[-0.340,0]; IP_SCORE(0.42)[ip: (-0.55), ipnet: 212.83.160.0/19(2.39), asn: 12876(0.25), country: FR(0.00)]; FREEMAIL_TO(0.00)[yahoo.com]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:12876, ipnet:212.83.160.0/19, country:FR]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Dec 2019 14:38:20 -0000 On Sun, 22 Dec 2019 15:06:08 -0800 Mark Millard wrote: > [It has taken explicitly controlling the DTB used and > use of "boot -v" together to be able to boot to > completion . . .] > > On 2019-Dec-22, at 12:47, Mark Millard wrote: > > > On 2019-Dec-22, at 11:16, Mark Millard wrote: > > > >> On 2019-Dec-22, at 02:38, Emmanuel Vadot wrote: > >> > >>> On Sun, 22 Dec 2019 00:22:16 -0800 > >>> Mark Millard via freebsd-arm wrote: > >>> > >>>> [OverDrive 1000 and MACCHIATObin Doubleshot updates went fine. > >>>> The code has Peter Jeremy's rk_tsadc.c patch.] > >>>> > >>>> > >>>> The console shows for boot -v . . . > >>>> > >>>> > >>>> Loading kernel... > >>>> /boot/kernel/kernel text=0x98af14 data=0x18e618 data=0x0+0x6fc8e8 syms=[0x8+0x142020+0x8+0x12d3fd] > >>>> Loading configured modules... > >>>> /boot/kernel/umodem.ko text=0x2120 text=0x13e0 data=0x6e8+0x10 syms=[0x8+0xf60+0x8+0xb7f] > >>>> /boot/kernel/ucom.ko text=0x217f text=0x3340 data=0x880+0x858 syms=[0x8+0x1170+0x8+0xb0d] > >>>> /boot/entropy size=0x1000 > >>>> > >>>> Hit [Enter] to boot immediately, or any other key for command prompt. > >>>> Booting [/boot/kernel/kernel] in 8 seconds... > >>>> > >>>> Type '?' for a list of commands, 'help' for more detailed help. > >>>> OK boot -v > >>>> Using DTB provided by EFI at 0x80f3000. > >>>> ---<>--- > >>>> . . . > >>> > >>> > >>> I don't have the same clocks from the dtb, make sure that you are > >>> using the latest one. > >>> rk3328_cru0: mem 0xff440000-0xff440fff on ofwbus0 > >>> . . . > >>> sha256 /boot/dtb/rockchip/rk3328-rock64.dtb > >>> SHA256 (/boot/dtb/rockchip/rk3328-rock64.dtb) = 50a180fed37f1d5dbfda60a6c55261c7b87b5b2bc97e428042481c94877da317 > >> > >> Thanks. > >> > >> # sha256 /mnt/boot/dtb/rockchip/rk3328-rock64.dtb > >> SHA256 (/mnt/boot/dtb/rockchip/rk3328-rock64.dtb) = 50a180fed37f1d5dbfda60a6c55261c7b87b5b2bc97e428042481c94877da317 > >> > >> Looks like a match to me. So I need to look elsewhere than > >> the contents of that file . . . > >> > >> My getting: "Using DTB provided by EFI at 0x80f3000" suggests > >> that the file is not being used for some reason: Instead some > >> sort of nonFreeBSD/internal-to-something-else DTB seems to be > >> in use? > >> > >> So my current guess is that I need to figure out how to control > >> which DTB source is used so that /boot/dtb/rockchip/rk3328-rock64.dtb > >> is used in my context. (Although I've no clue why I'd need a > >> different configuration for controlling such things now.) > >> > >> Note: I tried putting back the prior EFI/BOOT/bootaa64.efi but > >> it made no difference to the failed-boot behavior. > > > > Well, using load -t explicitly got farther: > > (So once I figure out an equivalent in /boot/loader.conf > > it should automatically get farther.) > . . . > > The following forced the desired .dtb to be used: > > # more /boot/loader.conf > . . . > rk3328_rock64_load="YES" > rk3328_rock64_type="dtb" > rk3328_rock64_name="/boot/dtb/rockchip/rk3328-rock64.dtb" > . . . You need to put the dtb in the ESP partition under /efi/dtb/rockchip U-Boot dtb is sometimes different than the one we use for the kernel. > Interestingly, so far, boot -v works for power up booting, > but default booting does not, even for when "boot" is > typed to the loader prompt. > > The default usually just hangs instead of showing all > the information that I reported previously. The hangup > (possibly with some text) is just before the start_init > line in: > > Warning: no time-of-day clock registered, system time will not be set accurately > start_init: trying /sbin/init > > So far, no hang-up has shown part of the "start_init" > message line. > > But I've not had troubles (so far) with "shutdown -r now" > reboots, defaults or otherwise: problems Just for going > from power-off to power-on and trying to boot. I don't have access to my boards right now but I'm pretty sure that booting without verbose worked for me recently. > (Someday, I also want to figure out how to set up the > Rock64 to get a stable DHCP binding: a fixed MAC > address, I guess.) > > === > Mark Millard > marklmi at yahoo.com > ( dsl-only.net went > away in early 2018-Mar) -- Emmanuel Vadot