public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Piotr Lobacz <piotr.lobacz@softgent.com>
To: u-boot@lists.denx.de
Subject: Booting on RK3399[Please note, mail behalf by sjg@google.com]
Date: Mon, 16 Nov 2020 07:55:55 -0700 (MST)	[thread overview]
Message-ID: <1605538555362-0.post@n7.nabble.com> (raw)
In-Reply-To: <CAPnjgZ2UHxLY5qxTAoHnQbQAFsGzJ_d6L+D-Vr8hL93xEbXt3g@mail.gmail.com>

Hi all,
i also have a firefly-rk3399 and got problems booting atf >= 1.4 with
whatever optee i use. Only rockchip blob is working for me. I know that i'm
doing something wrong but dunno what. The command for building atf is:
 
# make CROSS_COMPILE=aarch64-linux-gnu- PLAT=rk3399 LOG_LEVEL=40 DEBUG=0
CRASH_REPORTING=1 SPD=opteed bl31

and i only generate uboot.img and trust.img using rockchip build.sh script
with command

# ./buid.sh uboot

Rockchip has added this trust_merger app to their u-boot source code. The
build.sh script builds u-boot and executes make.sh script from u-boot which
runs trust_merger. But for some reason it does not work atf >= 1.4. I don't
know what exectly but what i can tell, i do not see any logs from bl31. For
atf 1.3 with rockchip bl32 blob i can see logs:

No find bl30.bin
Load uboot, ReadLba = 4000
Load OK, addr=0x200000, size=0xda214
RunBL31 0x10000 @ 105506 us
NOTICE:  BL31: v1.3(release):d43a527de
NOTICE:  BL31: Built : 15:41:07, Nov 16 2020
INFO:    GICv3 with legacy support detected. ARM GICV3 driver initialized in
EL3
INFO:    plat_rockchip_pmu_init(1331): pd status 3e
INFO:    BL31: Initializing runtime services
INFO:    BL31: Initializing BL32
INF [0x0] TEE-CORE:init_primary_helper:337: Initializing
(1.1.0-266-gee81607c #1 Mon Aug 17 09:23:30 UTC 2020 aarch64)

INF [0x0] TEE-CORE:init_primary_helper:338: Release version: 1.2

INF [0x0] TEE-CORE:init_teecore:83: teecore inits done
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x200000
INFO:    SPSR = 0x3c9


U-Boot 2017.09 (Nov 11 2020 - 10:27:07 +0100)

And this is what i get for 2.3 atf version:

find part:trust OK. first_lba:0x6000.
Trust Addr:0x6000, 0x58334c42
No find bl30.bin
Load uboot, ReadLba = 4000
Load OK, addr=0x200000, size=0xda214
RunBL31 0x40000 @ 105604 us


U-Boot 2017.09 (Nov 11 2020 - 10:27:07 +0100)

Model: Firefly-RK3399 Board
PreSerial: 2
DRAM:  3.8 GiB
Sysmem: init
Relocation Offset is: f5beb000
Using default environment

There is no NOTICE or INFO log. The bl32 blob is the same so i suspect for
99% that bl31 was not initialized.

Can anybody help me solving this issue? Because currently i'm with no more
ideas and this is really frustrating...

Best Regards
Piotr ?obacz





--
Sent from: http://u-boot.10912.n7.nabble.com/

  reply	other threads:[~2020-11-16 14:55 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-03  1:15 [U-Boot] Booting on RK3399 Simon Glass
2019-01-03  1:50 ` Mark Kettenis
2019-01-03  3:37   ` Simon Glass
2019-01-03 11:23     ` Mark Kettenis
2019-01-03 23:25       ` Simon Glass
2019-01-04 19:43         ` Mark Kettenis
2019-01-04 20:12           ` Simon Glass
2019-01-04 20:29             ` Mark Kettenis
2019-01-04 20:43               ` Simon Glass
2019-01-05  3:35                 ` Simon Glass
2019-01-05 15:56                   ` Simon Glass
2019-01-05 16:05                     ` Mark Kettenis
2019-01-08  0:38                       ` Simon Glass
2019-01-08  6:38                         ` [U-Boot] Booting on RK3399[Please note, mail behalf by sjg@google.com] Kever Yang
2019-01-10 12:56                           ` Simon Glass
2020-11-16 14:55                             ` Piotr Lobacz [this message]
2020-11-19  8:07                               ` Kever Yang
2020-11-19  8:25                                 ` Piotr Lobacz
2019-01-03 15:23   ` [U-Boot] Booting on RK3399 Jagan Teki
2019-01-03 15:40     ` Mark Kettenis
2019-01-03 15:49       ` Philipp Tomsich
2019-01-03 16:02       ` Jagan Teki
2019-01-03  7:01 ` [U-Boot] Booting on RK3399[Please note, mail behalf by sjg@google.com] Kever Yang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1605538555362-0.post@n7.nabble.com \
    --to=piotr.lobacz@softgent.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox