On Mon, Feb 1, 2021 at 12:54 PM Leon Woestenberg via
lists.yoctoproject.org <[email protected]>
wrote:
> using a very default ZCU102 build using 'gatesgarth', my kernel
> crashes on the ZCU102 board just after "psci: probing for conduit
> method from DT."
>
> MACHINE = "zcu102-zynqmp"
> EXTRA_IMAGEDEPENDS_append = " u-boot-zynq-scr"
>
I think the crash is related to the ARM Trusted Firmware not being
present in my build. My setup is without BL31.bin being present.

"PSCI is the interface from non-secure software to firmware
implementing power management use-cases (for example, secondary CPU
boot, hotplug, and idle). Non-secure software can access ATF runtime
services using the Arm secure monitor call (SMC) instruction."

So next I tried to build arm-trusted-firmware(.bin) which is not much
more than BL31.bin in a U-Boot wrapper.

The build works but U-Boot (both mainstream and Xilinx) SPL refused to
load the binary:

U-Boot SPL 2021.01 (Jan 21 2021 - 12:39:47 +0000)
PMUFW:    v1.1
Loading new PMUFW cfg obj (2200 bytes)
EL Level:    EL3
Chip ID:    zu9eg
Multiboot:    0
Trying to boot from MMC2
spl: could not initialize mmc. error: -19
Trying to boot from MMC1
spl_parse_legacy_header() = -22
spl_parse_image_header() = -22
spl_load_image_fat: error reading image atf-uboot.ub, err - -22
spl_load_image_fat: error reading image u-boot.itb, err - -2
Trying to boot from RAM
spl_parse_legacy_header() = -22

U-Boot SPL 2020.01 (Oct 21 2020 - 13:39:28 +0000)
PMUFW:    v1.1
Loading new PMUFW cfg obj (2200 bytes)
EL Level:    EL3
Multiboot:    0
Trying to boot from MMC2
spl: could not initialize mmc. error: -19
Trying to boot from MMC1
spl_load_image_fat: error reading image atf-uboot.ub, err - -22
spl_load_image_fat: error reading image u-boot.itb, err - -2
Trying to boot from RAM

The extra debug information was added by me, to find out that SPL
support for legacy images is missing in the U-Boot configuration.

By modifying build/.config and enabling that:

CONFIG_SPL_LEGACY_IMAGE_SUPPORT=y

The SPL now loads the ARM Trusted Firmware (ATF):

U-Boot SPL 2020.01 (Oct 21 2020 - 13:39:28 +0000)
PMUFW:    v1.1
Loading new PMUFW cfg obj (2200 bytes)
EL Level:    EL3
Multiboot:    0
Trying to boot from MMC2
spl: could not initialize mmc. error: -19
Trying to boot from MMC1
SPL: payload image:                                  load addr:
0xfffe9fc0 size: 51184
JuNOTICE:  ATF running on XCZU9EG/silicon v4/RTL5.1 at 0xfffea000
NOTICE:  BL31: v2.2(release):xilinx_rebase_v2.2_2020.2
NOTICE:  BL31: Built : 09:12:26, Nov  4 2020

But now suddenly fails to recognize the boot.scr:

U-Boot 2020.01 (Oct 21 2020 - 13:39:28 +0000)

Model: ZynqMP ZCU102 Rev1.0
Board: Xilinx ZynqMP
DRAM:  4 GiB
PMUFW:    v1.1
EL Level:    EL2
Chip ID:    zu9eg
NAND:  0 MiB
MMC:   mmc@ff170000: 0
In:    serial@ff000000
Out:   serial@ff000000
Err:   serial@ff000000
Bootmode: LVL_SHFT_SD_MODE1
Reset reason:    EXTERNAL
Net:
ZYNQ GEM: ff0e0000, mdio bus ff0e0000, phyaddr 12, interface rgmii-id

Warning: ethernet@ff0e0000 (eth0) using random MAC address - b2:63:28:bf:09:1e
eth0: ethernet@ff0e0000
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot.scr
496 bytes read in 11 ms (43.9 KiB/s)
## Executing script at 20000000
Bad Linux ARM64 Image magic!
SCRIPT FAILED: continuing...


Continuing the quest to get the most basic setup for ZynqMP working...
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#4837): 
https://lists.yoctoproject.org/g/meta-xilinx/message/4837
Mute This Topic: https://lists.yoctoproject.org/mt/80282679/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/meta-xilinx/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to