From nobody Fri Dec 15 15:56:40 2023 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 4SsDP15fglz53kH3 for ; Fri, 15 Dec 2023 15:56:53 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mx.blih.net (mx.blih.net [212.83.155.74]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4SsDP12Jccz4WFD for ; Fri, 15 Dec 2023 15:56:53 +0000 (UTC) (envelope-from manu@bidouilliste.com) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bidouilliste.com; s=mx; t=1702655803; 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=Y8e/SSf08v3NnGXpoGq42awpYg0YhPyMf6DtyCZswV8=; b=KLfUwpUAO/mTwlih27gmqXTwyUniZWC5WPvO7ZcbbShQBHytvRaa1JJR6thhbUku1wn/x6 0KQ5LLYnUSSWrE3e7hd9zQasbHe58/7WicOyhADmRor/YDy9VZhGey5aESBW4pJOvGtz53 fUS4fa7c52TVYlqRb7YhfLnob1Dd4Y4= Received: from skull.home.blih.net (lfbn-lyo-1-2174-135.w90-66.abo.wanadoo.fr [90.66.97.135]) by mx.blih.net (OpenSMTPD) with ESMTPSA id 9c2634be (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Fri, 15 Dec 2023 15:56:43 +0000 (UTC) Date: Fri, 15 Dec 2023 16:56:40 +0100 From: Emmanuel Vadot To: Harry Cc: freebsd-arm Subject: Re: u-boot-nanopi-r5c [Was: Re: 14-BETA5 panic on rk3566] Message-Id: <20231215165640.78bab647c883368b8fc9c34e@bidouilliste.com> In-Reply-To: <5211ad65-5289-4776-b839-7c681de77bf4@omnilan.de> References: <2CE509A2-AECF-4562-A080-589AC7888F21@edc.ro> <20231012184430.952dd9d5a26c97ee225c9e77@bidouilliste.com> <5211ad65-5289-4776-b839-7c681de77bf4@omnilan.de> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd15.0) 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=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:12876, ipnet:212.83.128.0/19, country:FR] X-Spamd-Bar: ---- X-Rspamd-Queue-Id: 4SsDP12Jccz4WFD Hi, On Fri, 15 Dec 2023 12:06:02 +0100 Harry wrote: > On 10/12/23 18:44, Emmanuel Vadot wrote: > >> can this be merged to 14-STABLE > >> /sys/dev/iicbus/pmic/rockchip/rk8xx_clocks.c > >> this seems to cause a panic > >> clkidef.name =3D (nclks =3D 2) ? clknames[0] : "clk32kout1"; > >> > > It's a bit too late tbh, also I don't consider rk356x stable even in > > 15-CURRENT, so this will be merged in stable/14 at some point but for > > now if you want to run on rk356x please use 15-CURRENT. >=20 >=20 > Hi Emmanuel, >=20 > thanks for your great FreeBSD contributions! Highly appreciate the=20 > Porting-FreeBSD-to-a-new-ARM-Board publication too! Thanks. > Quick question - I'm new to arm/u-boot, but some FreeBSD src & ports=20 > experience here... >=20 > In u-boot-2023.10 there's (master/)configs/nanopi-r5c-rk3568_defconfig=20 > added. > Simply copy'n'paste the ports/sysutils/u-boot-nanopi-r4s to=20 > u-boot-nanopi-r5c isn't enough... (after updating u-boot-master from=20 > 2023.07 to 2023.10, done that) >=20 > I don't understand sysutils/atf-master resp. sysutils/atf-rk3399. > Simply creating new rk3568 slave ports doesn't work since PLAT rk3568=20 > isn't implemenmted upstream...=A0 I guess I would have to adjust=20 > sysutils/u-boot-nanopi-r5c to get rid of the AT-F dependency first... but Yes upstream TF-A doesn't have rk356x support right now so we have to use the ones provided at https://github.com/rockchip-linux/rkbin > You mention running 15-CURRENT on rk356x >=20 > How to boot? >=20 > Would highly appreciate links - I'm currently trying to deploy=20 > FriendlyELEC R5C here - I could successfully start 14-stable, but just=20 > by try'n'error metgod, gluing lots of different loader blobs onto=20 > SDcard.=A0 I need to learn a lot, so I'm trying to do it a little bit=20 > smarter than try'n'error... >=20 >=20 > Thanks in advance, >=20 > -harry >=20 >=20 U-Boot also doesn't support the DRAM controller so we also need an external blob from rkbin. That's the main reason I haven't done ports for u-boot on rk356x so one have to compile u-boot themselve. It can be simply done like any other u-boot targets and only needs two env variable : export BL31=3D/path/to/rkbin/bin/rk35/rk3568_bl31_v1.43.elf export ROCKCHIP_TPL=3D/path/to/rkbin/bin/rk35/rk3568_ddr_1560MHz_v1.18.bin Cheers, --=20 Emmanuel Vadot