Inspired by your last post I tried adding an #undef CONFIG_ARM64 in arch/arm/lib/spl.c to force it to jump to the ATF without dropping to EL2 first. That is, to try to mimic the old hacky way of booting the ATF.
Unfortunately this hack seems to be insufficient as it gets stuck at address 0xfffea928 so I assume the ATF has crashed ending up in a reset vector - probably because some preconditions not being fulfilled. In the end, perhaps the best way forward is to try use the new ATF framework in u-boot but as you point out the information is sparse on that point. Hopefully someone out there can provide us with the missing information so that we can get the zynqmp booting without using the horrible xilinx toolchain. On Sat, May 5, 2018 at 4:19 PM, Andreas Galauner <[email protected]> wrote: > On 04.05.2018 21:25, Andreas Galauner wrote: > > It seems that it expects a FIT image there. > > > > If somebody knows how to use this, any help would be great. > > Ideally I'd like to have it boot a FIT image containing the BL31, BL32 > > (I'd try to hack support into u-boot for this once the thing boots), > > BL33 (main u-boot) and maybe even a kernel + dtb > > Short follow-up on this because I just got lucky with a google search > for CONFIG_SPL_ATF. > I found that the RK3399 enables the ATF loading[1] and also references a > script which seems to generate a FIT image with ATF inside[2]. > > I didn't try it so far but might give it a go when I have some time. > > - Andy > > [1]: > https://github.com/u-boot/u-boot/blob/master/configs/ > firefly-rk3399_defconfig#L19 > [2]: > https://github.com/u-boot/u-boot/blob/master/arch/arm/ > mach-rockchip/make_fit_atf.py > -- > _______________________________________________ > meta-xilinx mailing list > [email protected] > https://lists.yoctoproject.org/listinfo/meta-xilinx >
-- _______________________________________________ meta-xilinx mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-xilinx
