Hi Piotr,
On 2020/11/16 下午10:55, Piotr Lobacz wrote:
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.
This log shows everything is going well, there is no log from bl31
because the serial setting
is different in U-Boot and ATF, eg. ATF may use a different baud rate so
you can't see the serial output.
Thanks,
- Kever
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/
