cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
analoglamb
Observer
Observer
668 Views
Registered: ‎07-30-2019

Zynq MPSOC Reboot Failed in FSBL

Jump to solution

 Hi Xilinx

I am using ZCU102 and Petalinux 2019.2 to Test Watchdog Timer as Xilinx Wiki,https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/18842055/Cadence+WDT+Driver. But after the watchdog timer timeout, It reboots failed on FSBL, the log as below, If I use the reboot command in Linux, It's same.

Rebooting... [  723.888220] reboot: Restarting system
Xilinx Zynq MP First Stage Boot Loader
Release 2019.2   Aug  3 2020  -  10:56:58
Reset Mode      :       System Reset
Platform: Silicon (4.0), Cluster ID 0x80000000
Running on A53-0 (64-bit) Processor, Device Name: XCZU9EG
FMC VADJ Configuration Successful
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: 0x65216F
Data word offset: 0x65216F
Total Data word length: 0x65216F
Destination Load Address: 0xFFFFFFFF
Execution Address: 0x0
Data word offset: 0x109B0
Partition Attributes: 0x26
Destination Device is PL, changing LoadAddress
XPFW: Calling ROM PWRUP Handler..Done
XPFW: Calling ROM Isolation Handler..Done
Non authenticated Bitstream download to start now
DMA transfer done
PL Configuration done successfully
aPFW: Calling ROM PWRUP Handler..DoneP
 rtition 1 Load Success
======= In Stage 3, Partition No:2 =======
UnEncrypted data Length: 0x31DE
Data word offset: 0x31DE
Total Data word length: 0x31DE
Destination Load Address: 0xFFFEA000
Execution Address: 0xFFFEA000
Data word offset: 0x662B20
Partition Attributes: 0x117
SD: f_read returned 1
XFSBL_ERROR_SD_F_READ
Partition 2 Load Failed, 0x2B
================= In Stage Err ============
Fsbl Error Status: 0x0

But if I power on zcu102, It boots well, the log as below

Release 2019.2   Aug  3 2020  -  10:56:58
Reset Mode      :       System Reset
Platform: Silicon (4.0), Cluster ID 0x80000000
Running on A53-0 (64-bit) Processor, Device Name: XCZU9EG
FMC VADJ Configuration Successful
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: 0x65216F
Data word offset: 0x65216F
Total Data word length: 0x65216F
Destination Load Address: 0xFFFFFFFF
Execution Address: 0x0
Data word offset: 0x109B0
Partition Attributes: 0x26
Destination Device is PL, changing LoadAddress
XPFW: Calling ROM PWRUP Handler..Done
XPFW: Calling ROM Isolation Handler..Done
Non authenticated Bitstream download to start now
DMA transfer done
PL Configuration done successfully
PaFW: Calling ROM PWRUP Handler..Done
  rtition 1 Load Success
======= In Stage 3, Partition No:2 =======
UnEncrypted data Length: 0x31DE
Data word offset: 0x31DE
Total Data word length: 0x31DE
Destination Load Address: 0xFFFEA000
Execution Address: 0xFFFEA000
Data word offset: 0x662B20
Partition Attributes: 0x117
Partition 2 Load Success
======= In Stage 3, Partition No:3 =======
UnEncrypted data Length: 0x32976
Data word offset: 0x32976
Total Data word length: 0x32976
Destination Load Address: 0x8000000
Execution Address: 0x8000000
Data word offset: 0x665D00
Partition Attributes: 0x114
Partition 3 Load Success
All Partitions Loaded
================= In Stage 4 ============
Protection configuration applied
Running A▒▒}M▒▒▒▒ձ▒▒I▒▒▒ٕQ▒ͭ Removed 1 tasks
NOTICE:  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: v2.0(release):xilinx-v2019.1-12-g713dace9
NOTICE:  BL31: Built : 09:08:18, Aug  3 2020
Copied FSBL image to DDR and image hash checksum calculation successful
XPfw_SchedulerRemoveTask: Removed 1 tasks
PMUFW:  v1.1

Please help me solve the problem as soon as possible, Thanks

Tags (2)
1 Solution

Accepted Solutions
chaoz
Xilinx Employee
Xilinx Employee
631 Views
Registered: ‎09-14-2018

@analoglamb 

Could you read BootROM error after reboot failure?

You can refer to UG1085 for bootrom error codes information.

 

----------------------------------------------------------------------------------------------
如果帖子有帮助,别忘“接受为解决方案”或“奖励”。谢谢!
Don't forget to "Accept as solution" or "Kudo" if it helps. Thanks!
----------------------------------------------------------------------------------------------

View solution in original post

0 Kudos
2 Replies
chaoz
Xilinx Employee
Xilinx Employee
632 Views
Registered: ‎09-14-2018

@analoglamb 

Could you read BootROM error after reboot failure?

You can refer to UG1085 for bootrom error codes information.

 

----------------------------------------------------------------------------------------------
如果帖子有帮助,别忘“接受为解决方案”或“奖励”。谢谢!
Don't forget to "Accept as solution" or "Kudo" if it helps. Thanks!
----------------------------------------------------------------------------------------------

View solution in original post

0 Kudos
analoglamb
Observer
Observer
587 Views
Registered: ‎07-30-2019

Thanks, I find out the problem is led by sd card, no matters with petalinux. Use another SD card, It works well.

Thanks again

0 Kudos