From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from phobos.denx.de (phobos.denx.de [85.214.62.61]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 27C21C61DA3 for ; Thu, 26 Jan 2023 18:27:30 +0000 (UTC) Received: from h2850616.stratoserver.net (localhost [IPv6:::1]) by phobos.denx.de (Postfix) with ESMTP id BB6A485650; Thu, 26 Jan 2023 19:27:27 +0100 (CET) Authentication-Results: phobos.denx.de; dmarc=none (p=none dis=none) header.from=edgeble.ai Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=u-boot-bounces@lists.denx.de Authentication-Results: phobos.denx.de; dkim=pass (2048-bit key; unprotected) header.d=edgeble-ai.20210112.gappssmtp.com header.i=@edgeble-ai.20210112.gappssmtp.com header.b="vgDVxcy4"; dkim-atps=neutral Received: by phobos.denx.de (Postfix, from userid 109) id C839E85650; Thu, 26 Jan 2023 19:27:25 +0100 (CET) Received: from mail-yb1-xb34.google.com (mail-yb1-xb34.google.com [IPv6:2607:f8b0:4864:20::b34]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)) (No client certificate requested) by phobos.denx.de (Postfix) with ESMTPS id BE0CD85463 for ; Thu, 26 Jan 2023 19:27:11 +0100 (CET) Authentication-Results: phobos.denx.de; dmarc=none (p=none dis=none) header.from=edgeble.ai Authentication-Results: phobos.denx.de; spf=none smtp.mailfrom=jagan@edgeble.ai Received: by mail-yb1-xb34.google.com with SMTP id h5so3062317ybj.8 for ; Thu, 26 Jan 2023 10:27:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=edgeble-ai.20210112.gappssmtp.com; s=20210112; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=qoNkPDGviAlzadBCqFXTa8u7zLNA4b36zXjXGagq3j0=; b=vgDVxcy4NK+znZqYjPEtDoLA94SMnaws7xOhVe5kNW7Lk9DtBn4FZEhxaHatI8/lcZ wdEwyOudwZFnV4Ht8sC2wNSRcaAeelUDv57E+4KCGA7CgJwkKzMieZIheb8LRKjmB8TT XXGq88XNYbPv/9Yyli7lN8S4duQfQZ3dlYospKh7EW4HZIhy6SbNX06Jo00lCF33BFZd Yd67iyrPZb4z2WWFiwqDXy0GVJzIjLbh+xyLoWMQrJO8LWLWvJDQQjRb6wvKP+VCrbKi EYjtxbMvWk/V6PaRhffogpqPVSQGJmoTb1cI1uZVBrA8q4qmLofDW3l8nWDXyqZgZAdm DIsA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=qoNkPDGviAlzadBCqFXTa8u7zLNA4b36zXjXGagq3j0=; b=4hfRPJHGxD4o0B7Z2w1k6fo2fMrpR7OmvBy+ubkunCpsI+c43M29KjFlVWsJQOF62n gen1mpHbENxgD8soM2BjyVHzRoGfERehIFlEJMZ3ce30ecOTSfkp1gMtCoMCV9FCCSLy QmhUmF2zuDnlMsanNNQOHBODWyGrnCgDB6InN3bUC9huMUgAbQig+1ed3rnI5PAjGXpa hlet+M69qelcuayNiP7DMml3E38qKW6DIv/rc/Cyru9NxBl4EP7GkFXPlVaaCjCwdWGF 4OUUGdQ5opYKqpwcQ/3psPrTJfsRxjbeu41qJALeLq+5STB+Sx2WWhC6/aYIHW14cCij xxTg== X-Gm-Message-State: AO0yUKVzOnRtwPm/T76Lm84CJA0kjIvVHWfFlLiLal4pSGFhILWGyWb2 QvDbiAYnYQgWNoUjwM+M7DLI1ETw7IkulxZ0UVWsGg== X-Google-Smtp-Source: AK7set8f0QRwEPyqjYNagKbj6lg9bWT2tga/RrWpSAFj9wO6lxkbgi9MfCalwncPJxIUJa7FpHpvhj2pQF64InOqhRo= X-Received: by 2002:a25:5:0:b0:80b:7d50:ee3c with SMTP id 5-20020a250005000000b0080b7d50ee3cmr780423yba.44.1674757630283; Thu, 26 Jan 2023 10:27:10 -0800 (PST) MIME-Version: 1.0 References: <20230125222741.303259-1-jagan@edgeble.ai> <2efd56b6-4dc9-cd77-3792-e60142faa6ae@kwiboo.se> <64443c40-03b1-bfe2-23fe-ad61236d7dde@kwiboo.se> In-Reply-To: From: Jagan Teki Date: Thu, 26 Jan 2023 23:56:59 +0530 Message-ID: Subject: Re: [RFC PATCH 00/16] arm: Add Rockchip RK3588 support To: Simon Glass , Jonas Karlman Cc: Kever Yang , Philipp Tomsich , fatorangecat@189.cn, u-boot@lists.denx.de Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: u-boot@lists.denx.de X-Mailman-Version: 2.1.39 Precedence: list List-Id: U-Boot discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: u-boot-bounces@lists.denx.de Sender: "U-Boot" X-Virus-Scanned: clamav-milter 0.103.6 at phobos.denx.de X-Virus-Status: Clean Hi Simon, On Thu, 26 Jan 2023 at 23:34, Simon Glass wrote: > > Hi Jagan, > > On Thu, 26 Jan 2023 at 10:42, Jagan Teki wrote: > > > > On Thu, 26 Jan 2023 at 22:28, Jonas Karlman wrote: > > > > > > Hi Jagan, > > > On 2023-01-26 17:51, Jagan Teki wrote: > > > > Hi Jonas, > > > > > > > > On Thu, 26 Jan 2023 at 04:17, Jonas Karlman wrote= : > > > >> > > > >> Hi Jagan, > > > >> > > > >> On 2023-01-25 23:27, Jagan Teki wrote: > > > >>> This series support Rockchip RK3588. All the device tree files ar= e > > > >>> synced from linux-next with the proper SHA1 mentioned in the comm= it > > > >>> messages. > > > >>> > > > >>> Unfortunately, the BL31 from rkbin is not compatible with U-Boot = so > > > >>> it is failing to load ATF entry from SPL and hang. > > > >>> > > > >>> Verified below BL31 versions, > > > >>> bl31-v1.15 > > > >>> bl31-v1.21 > > > >>> bl31-v1.22 > > > >>> bl31-v1.23 > > > >>> bl31-v1.24 > > > >>> bl31-v1.25 > > > >>> bl31-v1.26 > > > >>> > > > >>> Rever-engineered with respect to rockchip u-boot by using the sam= e > > > >>> FIT_GENERATOR being used in Mainline, rockchip u-boot is booting = but > > > >>> mainline showing the same issue. > > > >>> > > > >>> Log: > > > >>> > > > >>> LPDDR4X, 2112MHz01-00642-g6bdfd31756-dirty (Jan 26 2023 =EF=BF=BD= =EF=BF=BD=EF=BF=BD3:44:34 +0530) > > > >>> channel[0] BW=3D16 Col=3D10 Bk=3D8 CS0 Row=3D17 CS1 Row=3D17 CS= =3D2 Die BW=3D8 Size=3D4096MB > > > >>> channel[1] BW=3D16 Col=3D10 Bk=3D8 CS0 Row=3D17 CS1 Row=3D17 CS= =3D2 Die BW=3D8 Size=3D4096MB > > > >>> channel[2] BW=3D16 Col=3D10 Bk=3D8 CS0 Row=3D17 CS1 Row=3D17 CS= =3D2 Die BW=3D8 Size=3D4096MB > > > >>> channel[3] BW=3D16 Col=3D10 Bk=3D8 CS0 Row=3D17 CS1 Row=3D17 CS= =3D2 Die BW=3D8 Size=3D4096MB > > > >>> change to F1: 528MHz > > > >>> change to F2: 1068MHz > > > >>> change to F3: 1560MHz > > > >>> change to F0: 2112MHz > > > >>> out > > > >>> > > > >>> U-Boot SPL 2023.01-00642-g6bdfd31756-dirty (Jan 26 2023 - 03:44:3= 4 +0530) > > > >>> Trying to boot from MMC1 > > > >>> bl31_entry: atf_entry start > > > >>> << hang >> > > > >>> > > > >>> Any information on BL31 for RK3588 please share. > > > >> > > > >> I had a similar strange booing issue with RK3568 and mainline U-Bo= ot, > > > >> turned out to be related to all parts of ATF not being properly lo= aded > > > >> into PMU SRAM. > > > >> > > > >> Using my series at [1] I managed to get ATF to be fully loaded int= o > > > >> PMU SRAM. Using CONFIG_SPL_FIT_SIGNATURE=3Dy helped me finding out= that > > > >> the segment being loaded ended up corrupted. > > > >> > > > >> The use of 512 bytes alignment of the FIT helped mitigate that iss= ue. > > > >> Vendor U-Boot use a bounce buffer for all parts that is written in= to > > > >> SRAM (anything loaded outside the gd->ram_base to gd->ram_top rang= e). > > > >> > > > >> You can also find newer bl31 at [2], up to version v1.32. > > > >> > > > >> [1] https://patchwork.ozlabs.org/project/uboot/list/?series=3D3378= 91>>> [2] https://gitlab.com/rk3588_linux/rk/rkbin/-/tree/linux-5.10-gen-rk= r3.5/bin/rk35>> > > > > Thanks for the details. I did apply this set on the master. No chan= ge > > > > in the behavior, used BL31 and ddr from [2] as well as in > > > > rkbin/master. > > > > > > I did some tests on my Radxa ROCK 3 Model B with CONFIG_SPL_FIT_SIGNA= TURE=3Dy > > > and it looked like it failed to read data into memory, see below. > > > > > > It also looks like the sdhci compatible is not supported by the drive= r. > > > Something that may need to be added to driver to properly read data? > > > > > > > > > DDR V1.09 a930779e06 typ 22/11/21-17:50:56 > > > LPDDR4X, 2112MHz > > > channel[0] BW=3D16 Col=3D10 Bk=3D8 CS0 Row=3D16 CS1 Row=3D16 CS=3D2 D= ie BW=3D16 Size=3D2048MB > > > channel[1] BW=3D16 Col=3D10 Bk=3D8 CS0 Row=3D16 CS1 Row=3D16 CS=3D2 D= ie BW=3D16 Size=3D2048MB > > > channel[2] BW=3D16 Col=3D10 Bk=3D8 CS0 Row=3D16 CS1 Row=3D16 CS=3D2 D= ie BW=3D16 Size=3D2048MB > > > channel[3] BW=3D16 Col=3D10 Bk=3D8 CS0 Row=3D16 CS1 Row=3D16 CS=3D2 D= ie BW=3D16 Size=3D2048MB > > > Manufacturer ID:0x6 > > > CH0 RX Vref:31.7%, TX Vref:21.8%,20.8% > > > CH1 RX Vref:31.7%, TX Vref:21.8%,21.8% > > > CH2 RX Vref:32.7%, TX Vref:22.8%,21.8% > > > CH3 RX Vref:32.7%, TX Vref:21.8%,20.8% > > > change to F1: 528MHz > > > change to F2: 1068MHz > > > change to F3: 1560MHz > > > change to F0: 2112MHz > > > out > > > > > > U-Boot SPL 2023.01 (Jan 26 2023 - 00:24:53 +0000) > > > Trying to boot from MMC1 > > > ## Checking hash(es) for config config_1 ... OK > > > ## Checking hash(es) for Image atf_1 ... sha256 error! > > > Bad hash value for 'hash' hash node in 'atf_1' image node > > > mmc_load_image_raw_sector: mmc block read error > > > Trying to boot from MMC1 > > > ## Checking hash(es) for config config_1 ... OK > > > ## Checking hash(es) for Image atf_1 ... sha256 error! > > > Bad hash value for 'hash' hash node in 'atf_1' image node > > > > Look like this is something wrong with your patch series or master > > changes on binman, not with the driver. I have observed the same if I > > enable CONFIG_SPL_FIT_SIGNATURE. > > There are some more changes in dm/master that I'm about to pull in. > One of them from Jonas Karlman adds hash nodes so may be involved. I found the same issue on the dm/master U-Boot SPL 2023.01-00176-gb21fb7a9c0 (Jan 26 2023 - 23:55:11 +0530) Trying to boot from MMC1 ## Checking hash(es) for config config-1 ... OK ## Checking hash(es) for Image atf-1 ... sha256 error! Bad hash value for 'hash' hash node in 'atf-1' image node mmc_load_image_raw_sector: mmc block read error SPL: failed to boot from all boot devices ### ERROR ### Please RESET the board ### Jagan.