UPGRADE YOUR BROWSER

We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

Reply

u-boot-xlnx 2017.3: Not starting after FSBL

Visitor
Posts: 15
Registered: ‎09-30-2017

u-boot-xlnx 2017.3: Not starting after FSBL

Hello,

 

Using 2017.3 I created an FSBL default project. 

Then I downloaded u-boot from git, checkout v2017.3 and compiled u-boot.

I created a boot image that contains FSBL.elf and then u-boot.elf

If I used Hello.elf instead of u-boot.elf, Hello.elf is running. 

 

What can cause u-boot not to run at all ?

No message is printed. 

 

In my project, security is not required. So I do not need bI31.elf, pmufw.elf

I tried using u-boot.elf for 2017.3 downloaded from xilinx with my FSBL.

Works Ok. 

 

Thank you,

Zvika 

 

Moderator
Posts: 526
Registered: ‎12-04-2016

Re: u-boot-xlnx 2017.3: Not starting after FSBL

Hi Zvika

 

pmufw is not for security reasons, it is essential to setup the clock and does platform management. It is needed required

 

 

Best Regards

Shabbir

Visitor
Posts: 15
Registered: ‎09-30-2017

Re: u-boot-xlnx 2017.3: Not starting after FSBL

Hi Shabbir,

 

Currently I'm not using petalinux. 

So I downloaded u-boot from https://github.com/Xilinx/u-boot-xlnx and then ran : git checkout xilinx-v2017.3

I created u-boot.elf 

The boot file contains: fsbl.elf, pmufw.elf, bI31.elf, u-boot.elf

With this scenario, u-boot.elf boots OK

 

I double checked: when u-boot.elf is burned after pmufw.elf without bI31.elf, u-boot is not starting.

Can you please explain why ?

 

Thank you, 

Zvika 

Moderator
Posts: 526
Registered: ‎12-04-2016

Re: u-boot-xlnx 2017.3: Not starting after FSBL

Hi Zvika

 

BL31.elf (ATF) not only does the secure functionality alone, please refer to this wiki to know in detail what the ATF does

http://www.wiki.xilinx.com/Arm+Trusted+Firmware

 

 

Best Regards

Shabbir

Moderator
Posts: 386
Registered: ‎04-24-2017

Re: u-boot-xlnx 2017.3: Not starting after FSBL

Hi @zvivered,

 

Can you enable DEBUG flags in FSBL and PMUFW and post the boot log.

Thanks,
Sandeep
PetaLinux Yocto | Embedded SW Support

---------------------------------------------------------------------------
Don’t forget to Reply, Kudo, and Accept as Solution.
---------------------------------------------------------------------------
Visitor
Posts: 15
Registered: ‎09-30-2017

Re: u-boot-xlnx 2017.3: Not starting after FSBL

Hi All,

 

Following is the output of the boot sequence till u-boot start running:

 

Xilinx Zynq MP First Stage Boot Loader
Release 2017.3 Jul 6 2018 - 22:51:42
Reset Mode : System Reset
Platform: Silicon (4.0), Cluster ID 0x80000000
Running on A53-0 (64-bit) Processor, Device Name: XCZU9EG
Board Configuration successful
Processor Initialization Done
================= In Stage 2 ============
QSPI 32 bit Boot Mode
QSPI is in Dual Parallel connection
QSPI is using 4 bit bus
FlashID=0x20 0xBB 0x20
MICRON 512M Bits
Multiboot Reg : 0x0
QSPI Reading Src 0x44, Dest FFFDEFC4, Length 4
.QSPI Read Src 0x22, Dest FFFDEFC4, Length 4
QSPI Reading Src 0x98, Dest FFFDEFC8, Length 4
.QSPI Read Src 0x4C, Dest FFFDEFC8, Length 4
Image Header Table Offset 0x8C0
QSPI Reading Src 0x8C0, Dest FFFDA150, Length 40
.QSPI Read Src 0x460, Dest FFFDA150, Length 40
*****Image Header Table Details********
Boot Gen Ver: 0x1020000
No of Partitions: 0x4
Partition Header Address: 0x440
Partition Present Device: 0x0
QSPI Reading Src 0x1100, Dest FFFDA190, Length 40
.QSPI Read Src 0x880, Dest FFFDA190, Length 40
QSPI Reading Src 0x1140, Dest FFFDA1D0, Length 40
.QSPI Read Src 0x8A0, Dest FFFDA1D0, Length 40
QSPI Reading Src 0x1180, Dest FFFDA210, Length 40
.QSPI Read Src 0x8C0, Dest FFFDA210, Length 40
QSPI Reading Src 0x11C0, Dest FFFDA250, Length 40
.QSPI Read Src 0x8E0, Dest FFFDA250, Length 40
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: 0xF590
Partition Attributes: 0x116
QSPI Reading Src 0x3D640, Dest FFFEA000, Length 6000
.QSPI Read Src 0x1EB20, Dest FFFEA000, Length 6000
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: 0x10D90
Partition Attributes: 0x116
QSPI Reading Src 0x43640, Dest FFFF0000, Length 20
.QSPI Read Src 0x21B20, Dest FFFF0000, Length 20
Partition 2 Load Success
======= In Stage 3, Partition No:3 =======
UnEncrypted data Length: 0x2835C
Data word offset: 0x2835C
Total Data word length: 0x2835C
Destination Load Address: 0x8000000
Execution Address: 0x8000000
Data word offset: 0x10DA0
Partition Attributes: 0x112
QSPI Reading Src 0x43680, Dest 8000000, Length A0D70
.QSPI Read Src 0x21B40, Dest 8000000, Length A0D70
Partition 3 Load Success
All Partitions Loaded
================= In Stage 4 ============
PM Init Success
Protection configuration applied
ATF running on XCZU9EG/silicon v4/RTL5.1 at 0xfffea000, with PMU firmware
NOTICE: BL31: Secure code at 0x0
NOTICE: BL31: Non secure code at 0x8000000
NOTICE: BL31: v1.3(release):f9b244b
NOTICE: BL31: Built : 20:55:38, Oct 11 2017
PMUFW: v0.3

 

In the PMU project:
#define XPFW_PRINT_VAL (1U)
#define XPFW_DEBUG_ERROR_VAL (1U) //Z.V (0U)
#define XPFW_DEBUG_DETAILED_VAL (1U) //Z.V (0U)

 

But It seems no messages are printed from PMU project. 

I searched the PMU code for the DEBUG defines and found no references. 

 

Thank you,

Zvika 

Highlighted
Visitor
Posts: 2
Registered: ‎06-27-2018

Re: u-boot-xlnx 2017.3: Not starting after FSBL

[ Edited ]

Did you figure out the issue? 

I am having the same issue on  the ultrascale+ (ZCU102).

I am using 2017.2 Vivado to generate the FSBL.elf and the u-boot-xlnx branch 2017.2 from github.