Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
SD card booting hangs stage 4, ES1
Using the prebuilt binary files from XZD_20161231.gz.
There are no errors. It just stops during Stage 4 as demonstrated in thread
Here is the console output.
Xilinx Zynq MP First Stage Boot Loader
Release 2016.3   Jan  5 2017  -  11:58:09
Platform: Silicon (1.0), Cluster ID 0x80000000
Running on A53-0 (64-bit) Processor, Device Name: XCZU9EG
Board Configuration successful
Processor Initialization Done
================= In Stage 2 ============
SD1 Boot Mode
SD: rc= 0
File name is BOOT.BIN
Multiboot Reg : 0x0
Image Header Table Offset 0x8C0
*****Image Header Table Details********
Boot Gen Ver: 0x1020000
No of Partitions: 0x4
Partition Header Address: 0x440
Partition Present Device: 0x0
Initialization Success
======= In Stage 3, Partition No:1 =======
UnEncrypted data Length: 0x1800
Data word offset: 0x1800
Total Data word length: 0x1800
Destination Load Address: 0xFFFEA000
Execution Address: 0xFFFEA000
Data word offset: 0x8A20
Partition Attributes: 0x116
Partition 1 Load Success
======= In Stage 3, Partition No:2 =======
UnEncrypted data Length: 0x8
Data word offset: 0x8
Total Data word length: 0x8
Destination Load Address: 0xFFFF0000
Execution Address: 0x0
Data word offset: 0xA220
Partition Attributes: 0x116
Partition 2 Load Success
======= In Stage 3, Partition No:3 =======
UnEncrypted data Length: 0x22B80
Data word offset: 0x22B80
Total Data word length: 0x22B80
Destination Load Address: 0x8000000
Execution Address: 0x8000000
Data word offset: 0xA230
Partition Attributes: 0x116
Partition 3 Load Success
All Partitions Loaded
================= In Stage 4 ============
Protection configuration applied
  ATF running on XCZU9EG/silicon v1/RTL5.1 at 0xfffea000
NOTICE:  BL31: Secure code at 0x0
NOTICE:  BL31: Non secure code at 0x0
NOTICE:  BL31: v1.2(release):2c2b23f
NOTICE:  BL31: Built : 11:58:24, Jan  5 2017
Note that my boot output says
ATF running on XCZU9EG/silicon v1/RTL5.1 at 0xfffea000
Where the boot in the below referenced forum thread is
ATF running on XCZU9EG/silicon v3/RTL5.1 at 0xfffea000
Is this relevant?

I am going down the path of rebuilding u-boot.

The Xen-Zynq-Distribution-XZD-Users-Manual.pdf says …
If the U-Boot boot command was not modified, you will need to interrupt the startup sequence and enter the boot commands manually:
U-Boot-PetaLinux> fatload mmc 0:1 $fdt_addr xen.dtb
U-Boot-PetaLinux> fdt addr $fdt_addr
U-Boot-PetaLinux> fdt resize
U-Boot-PetaLinux> fatload mmc 0:1 0x80000 Image
U-Boot-PetaLinux> fdt set /chosen/dom0 reg <0 0x80000 0x$filesize>
U-Boot-PetaLinux> fatload mmc 0:1 6000000 xen.ub
U-Boot-PetaLinux> bootm 6000000 - $fdt_addr
The document does not say how to interrupt the startup sequence.
Pressing CTL->C after the last output has no effect.

J.R. Heisey

After Stage 4, you should be dropped into UBoot to load the Xen kernel, which is where you would enter the commands in the manual. Using the prebuilt binaries, I was able to get to UBoot, so it seems like there might be a problem with your BOOT.BIN. To rule that out, could you post the md5sum of the BOOT.BIN on the SD card so we can double check it with ours? 

Also, what revision of the board are you using?  Under the Xilinx logo, there's the hardware name and then the revision. We've noticed slight changes between the revisions that could be causing the issues. 

Another method you could try is booting via JTAG. If that works, then the SD card could be the issue.  

Reuben Lewis

Forum Jump:

Users browsing this thread: 1 Guest(s)