cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Observer
Observer
407 Views
Registered: ‎06-01-2016

Ultrascale and sd card boot issue

Jump to solution

Hi,

I am trying (and failing) to boot our custom board that uses an UltraScale. I have tried to follow similar procedures for our Zynq boards, but to no avail. I have created a new Petalinux project (2019.2) and built the whole thing and put BOOT.BIN and image.ub on the sd card. FSBL starts and gets only up to the Arm Trusted Firmware, then stops. No u-boot.

Release 2019.2 Oct 12 2020 - 17:09:58
Reset Mode : System Reset
Platform: Silicon (4.0), Cluster ID 0x80000000
Running on A53-0 (64-bit) Processor, Device Name: XCZU7CG
Processor Initialization Done
================= In Stage 2 ============
SD0 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: 0x3
Partition Header Address: 0x440
Partition Present Device: 0x0
Initialization Success
======= In Stage 3, Partition No:1 =======
UnEncrypted data Length: 0x31DE
Data word offset: 0x31DE
Total Data word length: 0x31DE
Destination Load Address: 0xFFFEA000
Execution Address: 0xFFFEA000
Data word offset: 0xF5A0
Partition Attributes: 0x117
Partition 1 Load Success
======= In Stage 3, Partition No:2 =======
UnEncrypted data Length: 0x2B859
Data word offset: 0x2B859
Total Data word length: 0x2B859
Destination Load Address: 0x8000000
Execution Address: 0x8000000
Data word offset: 0x12780
Partition Attributes: 0x114
Partition 2 Load Success
All Partitions Loaded
================= In Stage 4 ============
PM Init Success
Protection configuration applied
Running 5J
iUU9-9Q1չ Qa
сjR5J1с5RrE5J1rсjRNOTICE: BL31: v2.0(release):xilinx-v2019.1-12-g713dace

Then I tried just a simple "Hello World" bare metal application both via Vitis and the older SDK. Fail. I followed the steps, made a boot image out of the FSBL and the hello world app, and it gives me this:

Xilinx Zynq MP First Stage Boot Loader
Release 2017.4 Oct 16 2020 - 10:37:43
Reset Mode : System Reset
Platform: Silicon (4.0), Cluster ID 0x80000000
Running on A53-0 (64-bit) Processor, Device Name: XCZU7CG
Processor Initialization Done
================= In Stage 2 ============
SD0 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: 0x2812
Data word offset: 0x2812
Total Data word length: 0x2812
Destination Load Address: 0x0
Execution Address: 0x0
Data word offset: 0x10D90
Partition Attributes: 0x114
Partition 1 Load Success
All Partitions Loaded
================= In Stage 4 ============
PM Init Success
Protection configuration applied
Running Cpu Handoff address: 0x0, Exec State: 0
Exit from FSBL
XFSBL_ERROR_UNDEFINED_EXCEPTION

In all cases, I cannot jump from FSBL to RAM to execute code. I also have the PMU firmware built and incorporated into the boot image just after the FSBL, but still no good. Any ideas?

0 Kudos
Reply
1 Solution

Accepted Solutions
Xilinx Employee
Xilinx Employee
331 Views
Registered: ‎10-11-2011

Have you run the Memory test to be sure your DDR (0x0) is stable?

-------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------

View solution in original post

2 Replies
Xilinx Employee
Xilinx Employee
332 Views
Registered: ‎10-11-2011

Have you run the Memory test to be sure your DDR (0x0) is stable?

-------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------

View solution in original post

Observer
Observer
316 Views
Registered: ‎06-01-2016

I ran a memtest from OCM and it seemed ok. But, I did find that the problem was with the PS DDR - bad settings. Once the timing and settings were all correct, then everything worked. 

0 Kudos
Reply