[meta-xilinx] zynqmp support in warrior branch

[Adrian Fiergolski]

Hi Alex,

Thank you for your message.

As I wrote, I debugged the system and SPL gets to bl31_entry call in
spl_invoke_atf function (spl_atf.c file). After I get a printout from
ATF in the terminal and nothing more happens. The full printout with SPL
DEBUG flag:

    <debug_uart> Debug uart enabled
    >>SPL: board_init_r()
    spl_init

    U-Boot SPL 2019.01 (Oct 23 2019 - 11:14:03 +0000)
    EL Level:       EL3
    Trying to boot from MMC2
    spl: mmc boot mode: fs
    SPL: payload image:                                  load addr:
    0xfffe9fc0 size: 51128
    Jumping to U-Boot via ARM Trusted Firmware
    NOTICE:  ATF running on XCZU6EG/silicon v4/RTL5.1 at 0xfffea000
    NOTICE:  BL31: Secure code at 0x0
    NOTICE:  BL31: Non secure code at 0x8000000
    NOTICE:  BL31: v2.0(release):xilinx-v2019.1
    NOTICE:  BL31: Built : 15:12:20, Oct 22 201

I understand you use U-Boot SPL based bootflow and you patch
pmu-firmware according to the guides from meta-xilinx-bsp README (link
<https://github.com/Xilinx/meta-xilinx/blob/warrior/meta-xilinx-bsp/README.building.md>),
right?

Regards,

Adrian

On 24.10.2019 10:08, Alexander Kerner wrote:
> Hi,
>
> I'm running warrioir branch on our custom board (ZCU102 based). Can
> you check the backtrace, maybe the uboot just stopped somewhere?
>
> Regards,
>
> Alex
>
> *Gesendet:* Mittwoch, 23. Oktober 2019 um 13:32 Uhr
> *Von:* "Adrian Fiergolski" <adrian.fiergolski at fastree3d.com>
> *An:* "meta-xilinx at yoctoproject.org" <meta-xilinx at yoctoproject.org>
> *Betreff:* [meta-xilinx] zynqmp support in warrior branch
>
> Hi,
>
> I am experiencing issue booting a custom board based on ZynqMP+
> device. The boot process stops at ATF:
>
> U-Boot SPL 2019.01 (Oct 23 2019 - 10:34:53 +0000)
> EL Level:       EL3
> Trying to boot from MMC2
> NOTICE:  ATF running on XCZU6EG/silicon v4/RTL5.1 at 0xfffea000
> NOTICE:  BL31: Secure code at 0x0
> NOTICE:  BL31: Non secure code at 0x8000000
> NOTICE:  BL31: v2.0(release):xilinx-v2019.1
> NOTICE:  BL31: Built : 15:12:20, Oct 22 2019
>
> I checked with debugger and apparently, ATF fails to launch u-boot image.
>
> As mu setup, what is reflected properly in the device-tree, uses 2 SD
> controllers, just as a precaution, I applied two patches on PMU (link
> <https://github.com/topic-embedded-products/meta-topic/tree/master/recipes-bsp/pmu-firmware/pmu-firmware>),
> including the one enabling NODE_SD0 for the cores.
>
> Has anybody experienced a similar issue? Can somebody confirm a
> successful run of ZynqMP+ based platform with warrior branch?
>
> Regards,
>
> Adrian
>
> -- _______________________________________________ meta-xilinx mailing
> list meta-xilinx at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-xilinx
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/meta-xilinx/attachments/20191024/5d9ec537/attachment.html>