From owner-freebsd-arm@freebsd.org Sun Jul 28 14:46:29 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 9EB8FACD41 for ; Sun, 28 Jul 2019 14:46:29 +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 03D7A979BF for ; Sun, 28 Jul 2019 14:46:27 +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 0f68ab18; Sun, 28 Jul 2019 16:46:19 +0200 (CEST) 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=Th4FyJ5r7lmEQkmR5GBsRT2Z6qw=; b=ENOcUL2rSuSoRm5fGkzh6mWQBHy0 r0AGKNSWd5zeVhAM6MDPXZBaLmZEkcaWR8//O/2aLIx9IUAlA1NmVhVybkGehvGM 23o4YZU5uXy2251T1VY0nIeRiVijpLyVsxM2R46EaI8cHe9+6OwBu0IP4nB60Q2b JnI2bV9ZF2RPG9M= 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=oWWayJrRnrHocSV2UjO7HJUv3XDz/IVxIhD1up58O2H8RlJubbOghRdd 2pBy8bf7aYhT9dvtPBz3OOJN3RhkmukTf7oZOPZKZjZ9YFZkFXyYcimiy2S26ubY i4NoEic396L8wOCbrw9BGxaz0138e7c1iUm5NU6y8EfCH8mu0xw= Received: from skull.home.blih.net (ip-9.net-89-3-105.rev.numericable.fr [89.3.105.9]) by mail.blih.net (OpenSMTPD) with ESMTPSA id 14660e77 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Sun, 28 Jul 2019 16:46:19 +0200 (CEST) Date: Sun, 28 Jul 2019 16:46:19 +0200 From: Emmanuel Vadot To: Denis Polygalov Cc: freebsd-arm@freebsd.org Subject: Re: Booting FreeBSD on Rock64 Message-Id: <20190728164619.7f40eccb59717d18996164b1@bidouilliste.com> In-Reply-To: <300bcdce-1471-e9a6-e332-84d3f822a65c@gmail.com> References: <169de7cf-32f2-7b7b-c12e-a86a4b6a9e87@gmail.com> <20190715200127.4b649877d8baefeb5282df64@bidouilliste.com> <878b15d5-92a5-5137-121c-5a5038323857@gmail.com> <20190718145840.c4487d2174930374300a0d7d@bidouilliste.com> <300bcdce-1471-e9a6-e332-84d3f822a65c@gmail.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: 03D7A979BF X-Spamd-Bar: + Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bidouilliste.com header.s=mail header.b=ENOcUL2r; 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 [2.00 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[bidouilliste.com:s=mail]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:212.83.177.182/32]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[bidouilliste.com]; NEURAL_SPAM_MEDIUM(0.56)[0.561,0]; NEURAL_SPAM_SHORT(0.96)[0.961,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[bidouilliste.com:+]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_SPAM_LONG(0.04)[0.043,0]; MX_GOOD(-0.01)[mx-backup.blih.net,mail.blih.net]; FREEMAIL_TO(0.00)[gmail.com]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; IP_SCORE(0.34)[ip: (-0.97), ipnet: 212.83.160.0/19(2.61), asn: 12876(0.08), country: FR(-0.01)]; 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: Sun, 28 Jul 2019 14:46:29 -0000 On Sun, 28 Jul 2019 23:33:16 +0900 Denis Polygalov wrote: > Can somebody please explain what is exact > command to switch FreeBSD's serial console > speed to the 1.5Mbps as required by ROCK64 board? > > I have u-boot interrupted from auto-loading > and trying to boot FreeBSD via network manually > by typing this: > > => dhcp > tftpboot ${kernel_addr_r} boot/loader.efi > tftpboot ${fdt_addr_r} boot/dtb/rockchip/rk3328-rock64.dtb > bootefi ${kernel_addr_r} ${fdt_addr_r} > > After that I can see the FreeBSD loader's menu, > but then kernel hangs during loading. You didn't do what I said in my last email : fdt addr ${fdt_addr_r} before bootefi. Note that if your DHCP server expose the next-server option you can just do : => setenv boot_targets dhcp => boot > Is the fact that I can see FreeBSD loader's menu is enough > to ensure that kernel will also inherit and continue use > the correct baud-rate? The kernel will use the baud rate specified in the DTB. > How can I be sure that FreeBSD kernel when loaded > will continue to use 1.5Mbps speed or this is not supported > and I have to switch u-boot to something standard (115200) > somehow? If so - how? > > thanks in advance, > Denis. BTW there is a new u-boot-rock64 port that you might want to use, you can boot from sdcard now. > On 18/07/2019 9:58 pm, Emmanuel Vadot wrote: > > On Thu, 18 Jul 2019 21:51:43 +0900 > > Denis Polygalov wrote: > > > >>> On 16/07/2019 3:01 am, Emmanuel Vadot wrote: > >>> How did you setup the boot ? > >> > >> download u-boot-flash-spi-rock64.img.xz from here: > >> https://github.com/ayufan-rock64/linux-u-boot/releases > >> and flash it. Remove the microSD card. > >> Setup tftp server and nfs servers. > >> Reset the board, interrupt u-boot and switch to manual mode. > >> Then type in terminal: > >> dhcp > >> tftpboot ${kernel_addr_r} boot/loader.efi > >> tftpboot ${fdt_addr_r} boot/dtb/rockchip/rk3399-rockpro64.dtb > > > > You need to 'fdt addr ${fdt_addr_r}' here iirc > > > >> bootefi ${kernel_addr_r} ${fdt_addr_r} > >> > >> > >>> Do you have tftpd running so u-boot can download the loader and the > >>> dtb ? > >> > >> yes, I do and I can see in the tftp server logs that both > >> boot/loader.efi > >> and boot/dtb/rockchip/rk3399-rockpro64.dtb > >> are downloaded successfully. > >> > >>> If you don't have the dtb in $TFTPDIR/dtb/rockchip/ that might be the > >>> problem, I recall the dtb included in u-boot being incomplete. > >> > >> I'm using dtb that is included into the > >> FreeBSD-13.0-CURRENT-arm64-aarch64-20190711-r349909-memstick.img > >> > >> > >>> I've just booted mine after updating to r350003+c99cb2e79ed6 > >>> without a problem. > >>> > >> > >> Well, I don't see image of this release on the FreeBSD.org server. > >> I guess you mean you compile it from source by yourself? > >> > >>> On 16/07/2019 4:49 am, Peter Jeremy wrote: > >>>> I'm running a Rock64 with > >>>> U-Boot SPL 2017.09-rockchip-ayufan-1035-gd646df03ac (Oct 26 2018 - 08:35:43) > >>>> and booting FreeBSD diskless. > >> > >> I tried this old 1035 u-boot. No luck, same problem. > >> > >> Regards, > >> Denis. > > > > > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" -- Emmanuel Vadot