Re: [U-Boot] How to support ATF on u-boot

Hi Kever,

Am 20.06.2016 um 04:59 schrieb Kever Yang:

I want to upstream a new SoC named RK3399 from Rockchip which is

AARCH64/ARMv8, we need to support Arm Trust Firmware base on U-boot.

Right now we are using a miniloader(just like SPL in U-boot) to load

ATF/U-boot, and PC jump from miniloader to ATF and then to U-boot(with CPU change to EL2 mode or nsEL1), then U-boot load kernel/rootfs as usual.

The ATF support for RK3399 has already upstream
Could you give your opinion on how to support ATF on U-boot upstream?

When I asked Simon Glass offline, he suggest if we can build ATF as part of the U-boot build process, perhaps with a script in U-boot tree,

Perhaps something like:

make rk3399_board_defconfig make ./scripts/build-atf-image rk3399_board ^^ new script

In any case, a good README would help.

I've started looking into RK3368 for my GeekBox, which raises a similar issue. Are you working on that as well or just RK3399?

Personally I think that the approach the HiKey has taken is the best, i.e. decouple U-Boot from ATF and just supply a README for how to make it work with U-Boot as ATF payload.

Obviously it would help to integrate your loaderimage tool into mkimage.

Also, what is the difference between your trust_merger tool and ATF's fip_create / fiptool?

Regards, Andreas