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!

cancel
Showing results for 
Search instead for 
Did you mean: 
Visitor niconorena
Visitor
1,283 Views
Registered: ‎06-27-2018

Ultrascale+ Uboot-xlnx not initialing after FSBL

Jump to solution

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

I am not using the petalinux tool, I am loading my own root file system.

 

the .bif file assigns the following config:

the_ROM_image:
 {
         [fsbl_config]a53_x64

          [bootloader]./path to /folder/projectName.sdk/fsbl/Debug/fsbl.elf
          [pmufw_image]./path to/folder/ProjectName.sdk/firmware/Debug/firmware.elf
          [destination_cpu = a53-0]./u-boot-xlnx/u-boot.elf
 }

 

The FSBL loads correctly as shown:

Xilinx Zynq MP First Stage Boot Loader

Release 2017.2 Aug 16 2018 - 17:29:19
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 ============

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: 0x2

Partition Header Address: 0x440

Partition Present Device: 0x0

Initialization Success

======= In Stage 3, Partition No:1 =======

UnEncrypted data Length: 0x3E69A

Data word offset: 0x3E69A

Total Data word length: 0x3E69A

Destination Load Address: 0x8000000

Execution Address: 0x8000000

Data word offset: 0xF590

Partition Attributes: 0x116

Partition 1 Load Success

All Partitions Loaded

================= In Stage 4 ============

PM Init Success
Protection configuration applied
Running Cpu Handoff address: 0x8000000, Exec State: 0

Exit from FSBL

 

It gets stock here, u-boot should print that is started loading. But I don't actually get any prints from u-boot.

Is it possible that the FSBL not finding u-boot in address 0x8000000?

I running blind here!! I was looking at the XSCT console from the SDk to try to print the values of the addresses over JTAG, not sure if this would help. 

Any ideas?

0 Kudos
1 Solution

Accepted Solutions
Adventurer
Adventurer
1,010 Views
Registered: ‎02-19-2018

Re: Ultrascale+ Uboot-xlnx not initialing after FSBL

Jump to solution

I solved it. At first I was building the ATF firmware on the master branch, and then I tried building it on the xilinx-v2018.3 tag. But my SDK version is 2018.2. Switching to the xilinx-v2018.2 tag of the arm-trusted-firmware allowed it to boot.

0 Kudos
8 Replies
Adventurer
Adventurer
1,083 Views
Registered: ‎02-19-2018

Re: Ultrascale+ Uboot-xlnx not initialing after FSBL

Jump to solution

Hello,

I am having the exact same problem. Did you ever solve this?

0 Kudos
Participant gosha-z
Participant
1,068 Views
Registered: ‎09-07-2018

Re: Ultrascale+ Uboot-xlnx not initialing after FSBL

Jump to solution

At least, you forget about bl31 AKA atf (ARM Trusted Firmware)

0 Kudos
Highlighted
Moderator
Moderator
1,050 Views
Registered: ‎09-12-2007

Re: Ultrascale+ Uboot-xlnx not initialing after FSBL

Jump to solution

If you dont want to use the petalinux, then you can use the OSL flow here:

https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/18841722/ZCU102+Image+creation+in+OSL+flow

Can you share your defconfig for your uboot? what is the address here?

0 Kudos
Adventurer
Adventurer
1,040 Views
Registered: ‎02-19-2018

Re: Ultrascale+ Uboot-xlnx not initialing after FSBL

Jump to solution

I am using the xilinx_zynqmp_zcu102_rev1_0_defconfig with no other changes. The load address is 0x8000000.

 

I tried booting again using bl31.elf instead of bl31.bin and I got something new:

Protection configuration applied
  ATF running on XCZU9EG/silicon v4/RTL5.1 at 0xfffea000
NOTICE:  BL31: Secure code at 0x0
NOTICE:  BL31: Non secure code at 0x8000000
NOTICE:  BL31: v1.5(release):xilinx-v2018.3
NOTICE:  BL31: Built : 07:01:47, Feb  7 2019
ERROR:   BL31: Platform Management API version error. Expected: v1.1 - Found: v1.0
ERROR:   Error initializing runtime service sip_svc
PMUFW is not found - Please load it!

### ERROR ### Please RESET the board ###

I built bl31.elf from the source git repo using tag xilinx-v2018.3 so I don't know why there is a version mismatch. I also am using the PMU firmware from the SDK and it is definitely installed in my BOOT.bin, so not sure why it's saying it's not found.

Here is my BIF file:

//arch = zynqmp; split = false; format = BIN
the_ROM_image:
{
	[fsbl_config]a53_x64
	[bootloader]D:\Workspace\arcs_zcu102\arcs_zcu102.sdk\fsbl\Debug\fsbl.elf
	[pmufw_image]D:\Workspace\arcs_zcu102\arcs_zcu102.sdk\pmu_fw\Debug\pmu_fw.elf
	[destination_device = pl]D:\Workspace\arcs_zcu102\arcs_zcu102.sdk\arcs_wrapper_hw_platform_0\arcs_wrapper.bit
	[destination_cpu = a53-0, exception_level = el-3, trustzone]D:\Workspace\arcs_zcu102\bl31.elf
	[destination_cpu = a53-0, exception_level = el-2]D:\Workspace\arcs_zcu102\u-boot.elf
}
0 Kudos
Participant gosha-z
Participant
1,037 Views
Registered: ‎09-07-2018

Re: Ultrascale+ Uboot-xlnx not initialing after FSBL

Jump to solution

You're talking about U-Boot. I'm talking about ARM Trusted Firmware for ZynqMP. It's a mandatory component.

0 Kudos
Adventurer
Adventurer
1,033 Views
Registered: ‎02-19-2018

Re: Ultrascale+ Uboot-xlnx not initialing after FSBL

Jump to solution

Did you read my last reply? I have ATF (bl31.elf) included.

0 Kudos
Participant gosha-z
Participant
1,030 Views
Registered: ‎09-07-2018

Re: Ultrascale+ Uboot-xlnx not initialing after FSBL

Jump to solution

@greande wrote:

Did you read my last reply? I have ATF (bl31.elf) included.


Sorry, missed it. Try "manual" boot of the system. Boot sequence mentioned in this topic. And please share your console output during this "manual" startup

0 Kudos
Adventurer
Adventurer
1,011 Views
Registered: ‎02-19-2018

Re: Ultrascale+ Uboot-xlnx not initialing after FSBL

Jump to solution

I solved it. At first I was building the ATF firmware on the master branch, and then I tried building it on the xilinx-v2018.3 tag. But my SDK version is 2018.2. Switching to the xilinx-v2018.2 tag of the arm-trusted-firmware allowed it to boot.

0 Kudos