Xen Zynq Distribution Support Forums

Full Version: booting from SD card
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Hello everyone,

My question is probably related with http://xzdforums.dornerworks.com/showthread.php?tid=651, but unfortunately, I was not able to make it work with the solution presented there.
When following the tutorial for booting from SD card, I'm stuck a the booting process.
Here is the log.
Code:
Xilinx Zynq MP First Stage Boot Loader
Release 2016.3   Jan  5 2017  -  11:58:09
Platform: Silicon (3.0), Cluster ID 0x80000000
Running on A53-0 (64-bit) Processor, Device Name: XCZU9EG
Board Configuration successful
Processor Initialization Done
================= In Stage 2 ============
SD1 with level shifter Boot Mode
SD: rc= 0
File name is BOOT.BIN
SD: Unable to open file BOOT.BIN: 3
                                  XFSBL_ERROR_SD_F_OPEN
Boot Device Initialization failed 0x29
================= In Stage Err ============
Fsbl Error Status: 0x0
I thought about a tool version problem and incompatibility between the boot.bin given and the board I have (ZCU102 rev 1.0 ES2) which is not the same from the tutorial I think because the SW6 configuration shown is not the same (must be 0xE, see UG1182). Hence I tried regenerating the boot.bin with newer SDK version. So I did as the tutorial said for generating a new boot.bin with SDK 2017.2 and get exactly the same error.
Next, I tried to use an FSBL generated with SDK 2017.2. So I started a blank project targeting the board and generated an newer fsbl. I next generated the boot.bin with the same procedure and got :
Code:
Xilinx Zynq MP First Stage Boot Loader
Release 2017.2   Jun 30 2017  -  10:53:29
Reset Mode      :       System Reset
Platform: Silicon (3.0), Cluster ID 0x80000000
Running on A53-0 (64-bit) Processor, Device Name: XCZU9EG
Board Configuration successful
Processor Initialization Done
================= In Stage 2 ============
SD1 with level shifter 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: 0x76E0
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: 0x8EE0
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: 0x8EF0
Partition Attributes: 0x116
Partition 3 Load Success
All Partitions Loaded
================= In Stage 4 ============
Protection configuration applied
 ATF running on XCZU9EG/silicon v3/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


And the console is stuck there. U-boot doesn't show up.

Any idea what I should do ?
Thanks in advance !
Our latest release of XZD doesn't currently support the ES2 revision of silicon for the Xen Zynq Distribution. I suspect that your U-Boot is also out of date. You can try to build our fork of U-Boot provided here: https://github.com/dornerworks/u-boot-xlnx

Your best bet is to use the branch dw-v2016.4 or dw-v2017.1. Keep in mind that these are experimental branches and aren't fully supported. So we likely can't follow up too much before our next release. 

I hope this helps.

Thanks,
Robbie VanVossen
Robbie,

I am having similar issues. I am currently just evaluating Xen on Xilinx Zynq UltraScale zcu102 eval board Revision 1.0. I'm not certain I want to create all of the binaries just to get Xen to run. And based on your last post the u-boot (and what else?) isn't stable on this hardware.

When will DornerWorks have a pre-built set of binaries for this board which I can just use?

J.R. Heisey
J.R.,

We only release binaries that we can verify will actually run on the desired hardware target, and currently we do not have an ES2 hardware target. Our expectation is that we will have support for ES2 and production silicon boards in our September release. If that time frame does not suit your needs, please contact our sales department about arranging a service engagement to accelerate your project. http://dornerworks.com/contact-us

Regards,

-Jarvis
Thanks for your kind answer Robbie (and sorry for my late answer -> holidays). I will try generating the whole bunch of boot files.

I'm pretty sure there is no mention of this (no rev2 support) in the user manual (my version is Xilinx-XenZynq-DOC-0001 v0.14 January 6, 2017). If the boards now sold by Xilinx are all rev2, as mine is, it is a crucial information to have in order to troubleshoot more quickly. Please, update your manual accordingly !

Alban
Alban,

The ZCU102 rev 1.0 boards are not supported in the current XZD release. We are planning on adding that to the release in September, if not sooner.

Regards,

-Jarvis