cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
msh
Voyager
Voyager
4,139 Views
Registered: ‎10-31-2016

ZCU106: xilinx flash: XFSBL_ERROR_QSPI_LENGTH

Hello, 

 

I am trying to flash into board flash memory. In jatag mode the code works fine. But in QSPI mode I get such error 

XFSBL_ERROR_QSPI_LENGTH (when run in FSBL debug mode)

 

 

================= 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 : 0x1800
QSPI Reading Src 0xC000000, Dest FFFF1C40, Length EC0
XFSBL_ERROR_QSPI_LENGTH
Device Copy Failed
Boot Device Initialization failed 0x19

 

Please advise me what is the problem?

 

Thanks 

Best regards 

0 Kudos
25 Replies
denist
Xilinx Employee
Xilinx Employee
4,096 Views
Registered: ‎10-11-2011

The FSBL is detecting the image at Multiboot Reg : 0x1800 which is weird if you are programming the BOOT.bin at 0x0.

How did you program the flash?

-------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------
4,061 Views
Registered: ‎07-03-2018

Have the same issue, programmed the flash with the sdk.

 

Fsbl Error Status: 0x0Xilinx Zynq MP First Stage Boot Loader
Release 2018.2 Jul 4 2018 - 12:35:13
Reset Mode : System Reset
Platform: Silicon (3.0), Cluster ID 0xC0000100
Running on R5-0 Processor, Device Name: XCZU9EG
Initializing TCM ECC
Address 0x0, Length FFE00020, ECC initialized
Address 0x0, Length FFE20000, ECC initialized
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 : 0x1800
QSPI Reading Src 0xC000000, Dest FFFF0040, Length EC0
XFSBL_ERROR_QSPI_LENGTH
Device Copy Failed
Boot Device Initialization failed 0x19
================= In Stage Err ============
Fsbl Error Status: 0x0

0 Kudos
denist
Xilinx Employee
Xilinx Employee
4,012 Views
Registered: ‎10-11-2011

Please , let me know the revision of your ZCU106 board.

-------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------
0 Kudos
denist
Xilinx Employee
Xilinx Employee
4,005 Views
Registered: ‎10-11-2011

It looks correct on mine:

 

Release 2018.1 Jul 9 2018 - 16:36:58

Reset Mode : System Reset

Platform: Silicon (3.0), Cluster ID 0x80000000

 

Running on A53-0 (64-bit) Processor, Device Name: XCZU7EV

 

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 0x0, Dest FFFF1C40, Length EC0

.QSPI Read Src 0x0, Dest FFFF1C40, Length EC0

Image Header Table Offset 0x8C0

 

QSPI Reading Src 0x8C0, Dest FFFDA150, Length 40

.QSPI Read Src 0x460, Dest FFFDA150, Length 40

-------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------
0 Kudos
smarell
Community Manager
Community Manager
3,989 Views
Registered: ‎07-23-2012

I have recently seen an issue on the similar lines. This issue was seen only with few specific designs. I'm currently investigating on the root cause.

Can you please create a boot image with just FSBL and hello world applications and see if this issue can be reproduced?
-----------------------------------------------------------------------------------------------
Please mark the post as "Accept as solution" if the information provided answers your query/resolves your issue.

Give Kudos to a post which you think is helpful.
0 Kudos
3,981 Views
Registered: ‎07-03-2018

Hi, 

It seems that the issue in my case for my setup (zcu102-es2)  was due to selecting the wrong flash type while programming the flash memory from the sdk, I had selected qspi_single instead of qspi_dual_paralell.

denist
Xilinx Employee
Xilinx Employee
3,964 Views
Registered: ‎10-11-2011

I confirmed choosing the wrong qspi configuration in the flash programmer will give you that error at boot:

 

================= 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 : 0x1800

 

QSPI Reading Src 0xC000000, Dest FFFF1C40, Length EC0

XFSBL_ERROR_QSPI_LENGTH

Device Copy Failed

 

Boot Device Initialization failed 0x19

-------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------
swarnim
Participant
Participant
3,266 Views
Registered: ‎05-24-2018

Hi

I am facing the same issue on ZCU102 , I could not find "qspi_dual_parallel" type in the Program flash window in SDK. It is showing qspi_x8_dual_parallel instead. Following the process mentioned in UG1209 I tried to program the flash but I am unable to do. So I tried using the XSCT terminal and I am getting the following error - 

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 : 0x3000
QSPI Reading Src 0x18000000, Dest FFFF1C40, Length EC0
XFSBL_ERROR_QSPI_LENGTHQSPI 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 : 0x3000
QSPI Reading Src 0x18000000, Dest FFFF1C40, Length EC0
XFSBL_ERROR_QSPI_LENGTH
Device Copy Failed
Boot Device Initialization failed 0x19
================= In Stage Err ============
Fsbl Error Status: 0x0

Device Copy Failed
Boot Device Initialization failed 0x19
================= In Stage Err ============
Fsbl Error Status: 0x0

 

Can anyone help me out, I know its an year old thread but I am facing the same issue so I considered to reply on the same thread instead of opening a new one.

0 Kudos
denist
Xilinx Employee
Xilinx Employee
3,257 Views
Registered: ‎10-11-2011

Can I please see the start of the FSBL log?

I would like to see what heppened the first time when "Multiboot Reg : 0x0".

 

-------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------
0 Kudos
swarnim
Participant
Participant
3,251 Views
Registered: ‎05-24-2018

Hi

Thanks for the reply.

I tried it again with the XSCT terminal and this time it was loaded correctly and booted up on the UART terminal.

But when I am trying to program the flash using SDK "Create boot image" & "Program flash" I am not able to program the flash. I have also tried the patch mentioned in AR#72113 regarding ZCU102 changes in fsbl but then also while programming via SDK i get this log in my console window in SDK and the flash is not programmed -

 

program_flash -f /home/crypto/xilinx-zcu102-zu9-es2-rev1.0-2018.3/qspi_BOOT.bin -offset 0 \
-flash_type qspi-x8-dual_parallel -fsbl \
/home/crypto/xilinx-zcu102-zu9-es2-rev1.0-2018.3/images/linux/zynqmp_fsbl.elf -cable type \
xilinx_tcf url TCP:127.0.0.1:3121

****** Xilinx Program Flash
****** Program Flash v2018.3.1 (64-bit)
**** SW Build 2489853 on Tue Mar 26 04:18:30 MDT 2019
** Copyright 1986-2019 Xilinx, Inc. All Rights Reserved.


Connected to hw_server @ TCP:127.0.0.1:3121
Available targets and devices:
Target 0 : jsn-JTAG-SMT2NC-210308A7AFB8
Device 0: jsn-JTAG-SMT2NC-210308A7AFB8-24738093-0

Retrieving Flash info...

Initialization done, programming the memory
===== mrd->addr=0xFF5E0204, data=0x00000000 =====
BOOT_MODE REG = 0x0000
Downloading FSBL...
Running FSBL...
Finished running FSBL.


U-Boot 2018.01-00073-g63efa8c-dirty (Oct 04 2018 - 08:27:12 -0600)

Model: ZynqMP MINI QSPI
Board: Xilinx ZynqMP
DRAM: "Error" handler, esr 0xbf000002
ELR: fffcf3d0
LR: fffc1658
x0 : 00000000ffe00000 x1 : 0000000000000000
x2 : 0000000000040000 x3 : 00000000ffe40000
x4 : 00000000ffe00010 x5 : 0000000000000000
x6 : 0000000000008000 x7 : 00000000ffe40008
x8 : 00000000fffdf710 x9 : 0000000000000080
x10: 00000000fffdf7bc x11: 00000000fffd3ff0
x12: 0000000000000005 x13: 0000000000000114
x14: 00000000fffdf79c x15: 00000000fffd3ff0
x16: 00000000ff9815e8 x17: 00000000ff9814fc
x18: 00000000fffdf8a0 x19: 00000000fffd0ca8
x20: 00000000fffd0bf0 x21: 0000000000000000
x22: 00000000fffd7238 x23: 00000000fffe0110
x24: 00000000fffe0000 x25: 00000000fffd8640
x26: 00000000ff18035c x27: 0000000000000000
x28: 0000000000000000 x29: 00000000fffdf850

Resetting CPU ...

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

Could you please help me out with the issue in this when I am trying to load same files as per the procedure provided in UG1209 (21 dec 2018 version).

0 Kudos
denist
Xilinx Employee
Xilinx Employee
3,244 Views
Registered: ‎10-11-2011

"Multiboot Reg : 0x1800" ?

Are you programming the image at 0x0 in the flash?

I really would like to see the whole log if possible (starting from the FSBL banner).

-------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------
0 Kudos
swarnim
Participant
Participant
3,230 Views
Registered: ‎05-24-2018

Hi

Yeah I am programming the flash via In-system Programmer (using SDK --> Xilinx --> Program flash). In that I selected the image file as boot.bin created by the create boot image and fsbl.elf is selected in fsbl file. The offset is kept as 0 as suggested in UG1209 document. Also the flash type selected is qspi_x8_dual_parallel.

The prints I attached are the only prints in the SDK console when I hit program button. This is while programming the flash not while booting up from flash. The programming of flash is only failing when done via In-system programmer.

 

PS - The XSCT steps to load via JTAG is done successfully and it loads linux onto the board successfully. I am trying the same with the In-system programmer to program the flash and then boot linux via this.

0 Kudos
denist
Xilinx Employee
Xilinx Employee
3,225 Views
Registered: ‎10-11-2011

When programming the flash you should switch the boot mode to JTAG. That's the recommended way.

The prints show you are booting in QSPI and some code is executing, making the programmer failing afterwards.

-------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------
0 Kudos
swarnim
Participant
Participant
3,210 Views
Registered: ‎05-24-2018

Hi

Yeah I want to program the flash and I have set the boot mode settings to JTAG only i.e 0000 on the dip switches.

The prints are on the SDK terminal while programming the flash not while booting. The board is already powered on in JTAG mode and then I am running the Program flash from SDK and it gives the mentioned prints in the SDK terminal while programming the flash. The prints can also be seen as saying programming flash only not the booting prints.

I am not able to program the flash as shown in the prints.

0 Kudos
denist
Xilinx Employee
Xilinx Employee
3,199 Views
Registered: ‎10-11-2011

There are two logs every time you run SDK Flash Programming.

One on the console (from the tool) and one on the UART (from the specified FSBL).

I see in the thread the one from the tool and it looks like the system is NOT initialized properly when "u-boot" behind the scene try to run.

I really would like to see the one from the FSBL during Flash Progranmming. If the debug prints are all enabled on that FSBL it should show a clean handoff.

Another question .... do you have ECC enabled on your DDR? We saw some problema with that during flash programming in the past.

-------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------
0 Kudos
jasonhuangatpoc
Observer
Observer
2,119 Views
Registered: ‎06-07-2017

I am having the same issue when I try to boot from the flash memory. The device is xczu19eg at a custom board and I am using Vivado/SDK 2019.1. In Vivado the QSPI config is Dual Parallel x4, but in SDK I cannot find qspi-x4-dual_parallel. It has qspi-x8-dual_parallel and others. Below is the log file. Any suggestion?


Connected to COM5 at 115200
Xilinx Zynq MP First Stage Boot Loader

Release 2019.1 Jun 10 2020 - 13:25:35
Reset Mode : System Reset
Platform: Silicon (4.0), Cluster ID 0x80000000

Running on A53-0 (64-bit) Processor, Device Name: XCZU19EG

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 0xBA 0x21

MICRON 1G Bits
Multiboot Reg : 0x0

QSPI Reading Src 0x0, Dest FFFF1C40, Length EC0
.Image Header Table Offset 0x8C0

QSPI Reading Src 0x8C0, Dest FFFDA028, Length 40
.*****Image Header Table Details********

Boot Gen Ver: 0x1020000

No of Partitions: 0x5

Partition Header Address: 0x440

Partition Present Device: 0x0

QSPI Reading Src 0x1100, Dest FFFDA068, Length 40
.QSPI Reading Src 0x1140, Dest FFFDA0A8, Length 40
.QSPI Reading Src 0x1180, Dest FFFDA0E8, Length 40
.QSPI Reading Src 0x11C0, Dest FFFDA128, Length 40
.QSPI Reading Src 0x1200, Dest FFFDA168, Length 40
.Initialization Success

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

UnEncrypted data Length: 0x48C82D

Data word offset: 0x48C82D

Total Data word length: 0x48C82D

Destination Load Address: 0xFFFFFFFF

Execution Address: 0x0

Data word offset: 0x76F0

Partition Attributes: 0x26

QSPI Reading Src 0x1DBC0, Dest 100000, Length 12320B4
.Destination Device is PL, changing LoadAddress
Non authenticated Bitstream download to start now
DMA transfer done
PL Configuration done successfully
Partition 1 Load Success

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

UnEncrypted data Length: 0xA

Data word offset: 0xA

Total Data word length: 0xA

Destination Load Address: 0x100000

Execution Address: 0x100000

Data word offset: 0x493F20

Partition Attributes: 0x11E

QSPI Reading Src 0x124FC80, Dest 100000, Length 28
.Partition 2 Load Success

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

UnEncrypted data Length: 0x2A3

Data word offset: 0x2A3

Total Data word length: 0x2A3

Destination Load Address: 0x50000000

Execution Address: 0x0

Data word offset: 0x493F30

Partition Attributes: 0x11E

QSPI Reading Src 0x124FCC0, Dest 50000000, Length A8C
.Partition 3 Load Success

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

UnEncrypted data Length: 0x4A

Data word offset: 0x4A

Total Data word length: 0x4A

Destination Load Address: 0x50000A90

Execution Address: 0x0

Data word offset: 0x4941E0

Partition Attributes: 0x11E

QSPI Reading Src 0x1250780, Dest 50000A90, Length 128
.Partition 4 Load Success

All Partitions Loaded

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

PMU-FW is not running, certain applications may not be supported.

Protection configuration applied
XFSBL_ERROR_UNSUPPORTED_HANDOFF : A53-0 64 bit to 32 bit

Handoff Failed 0x4E

================= In Stage Err ============

Fsbl Error Status: 0x0Xilinx Zynq MP First Stage Boot Loader

Release 2019.1 Jun 10 2020 - 13:25:35
Reset Mode : System Reset
Platform: Silicon (4.0), Cluster ID 0x80000000

Running on A53-0 (64-bit) Processor, Device Name: XCZU19EG

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 0xBA 0x21

MICRON 1G Bits
Multiboot Reg : 0x2000

QSPI Reading Src 0x10000000, Dest FFFF1C40, Length EC0
XFSBL_ERROR_QSPI_LENGTH
Device Copy Failed

Boot Device Initialization failed 0x19

================= In Stage Err ============

Fsbl Error Status: 0x0

0 Kudos
denist
Xilinx Employee
Xilinx Employee
2,048 Views
Registered: ‎10-11-2011

The real error is "XFSBL_ERROR_UNSUPPORTED_HANDOFF : A53-0 64 bit to 32 bit"

Can I see the .bif used to generate the BOOT.bin?

-------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------
0 Kudos
rjoycequincy
Visitor
Visitor
1,903 Views
Registered: ‎07-17-2019

I am seeing the same error. Will program, but code will not run  'from Flash' .

Custom Board ZCU6EG with Spansion   s25fl512s  in dual parallel  x8. 

SDK = 2019.1

  1.  My example is JUST an FSBL.
    BTW: I can get u-boot (w/ FSBL, PMU-FW, & ATF/BL31) to program to flash, but needs debugger to run it.
  2.   Where does ZynqMP MINI QSPI  come from ? 
  3. Here is all pertinent info / output (I hope). 

bif file   the elf image is from FSBL Template, with Debug Flags enabled

.//arch = zynqmp; split = false; format = BIN
the_ROM_image:
{
[bootloader, destination_cpu=a53-0] <path>\\July27\Release\July27.elf
}

bootgen:

xsct%  exec bootgen -image July27_FSBL_only.bif -arch zynqmp -o package_July27_FSBL_only.bin -w on -log trace

 

Console - 'Program Flash'  (BootMode = JTAG)

cmd /C program_flash -f \
<path>/\package_July27_FSBL_only.bin \
-offset 0 -flash_type qspi-x8-dual_parallel -fsbl \
<path>/\July27\Release\July27.elf \
-cable type xilinx_tcf url TCP:127.0.0.1:3121

****** Xilinx Program Flash
****** Program Flash v2019.1.1 (64-bit)
**** SW Build 2580384 on Sat Jun 29 08:12:21 MDT 2019
** Copyright 1986-2019 Xilinx, Inc. All Rights Reserved.


WARNING: Failed to connect to hw_server at TCP:127.0.0.1:3121
Attempting to launch hw_server at TCP:127.0.0.1:3121

Connected to hw_server @ TCP:127.0.0.1:3121
Available targets and devices:
Target 0 : jsn-DLC9-Port_#0002.Hub_#0004
Device 0: jsn-DLC9-Port_#0002.Hub_#0004-24739093-0

Retrieving Flash info...

Initialization done, programming the memory
===== mrd->addr=0xFF5E0204, data=0x00000000 =====
BOOT_MODE REG = 0x0000
Downloading FSBL...
Running FSBL...
Finished running FSBL.

 


U-Boot 2019.01 (Jun 04 2019 - 09:56:01 -0600)

 

Model: ZynqMP MINI QSPI          [?? HUH ?? Where does this come from ? ]

Board: Xilinx ZynqMP

DRAM: WARNING: Initializing TCM overwrites TCM content

256 KiB

EL Level: EL3

In: dcc

Out: dcc

Err: dcc

ZynqMP> sf probe 0 0 0


SF: Detected s25fl512s_256k with page size 512 Bytes, erase size 512 KiB, total 128 MiB

ZynqMP> Sector size = 524288.
f probe 0 0 0


Performing Erase Operation...
sf erase 0 80000


SF: 524288 bytes @ 0x0 Erased: OK

ZynqMP> Erase Operation successful.
INFO: [Xicom 50-44] Elapsed time = 1 sec.
Performing Program Operation...
0%...sf write FFFC0000 0 19B80


device 0 offset 0x0, size 0x19b80

SF: 105344 bytes @ 0x0 Written: OK

ZynqMP> Program Operation successful.
INFO: [Xicom 50-44] Elapsed time = 4 sec.

Flash Operation Successful

Does not run from POR  (BootMode = QSPI32)

Here is output when run from the debugger:  (BootMode = QSPI32)

Xilinx Zynq MP First Stage Boot Loader

Release 2019.1 Jul 27 2020 - 19:05:46
Reset Mode : System Reset
Platform: Silicon (4.0), Cluster ID 0x80000000

Running on A53-0 (64-bit) Processor, Device Name: XCZU6EG

Processor Initialization Done

================= In Stage 2 ============

QSPI 32 bit Boot Mode

QSPI is in Dual Parallel connection
QSPI is using 4 bit bus      [ is this correct ie does it mean each chip is 4-bits ? ]
FlashID=0x1 0x2 0x20

SPANSION 512M Bits
Multiboot Reg : 0x4000

QSPI Reading Src 0x20000000, Dest FFFF1C40, Length EC0
XFSBL_ERROR_QSPI_LENGTH      [ Remember this is running from debugger ]
Device Copy Failed

Boot Device Initialization failed 0x19

================= In Stage Err ============

Fsbl Error Status: 0x0

0 Kudos
denist
Xilinx Employee
Xilinx Employee
1,842 Views
Registered: ‎10-11-2011

The debugger run fails because previous boot from QSPI failed.

You can see the wrong Multiboot Reg : 0x4000

It should be 0x0. Try to force it to 0x0 and see if the boot proceed a little further (in debug).

 

I am not sure why the original boot from QSPI is not working. The flash programming seems successful.

Are you sure the QUADREAD is enable in the flash?

Can you read the bootrom ERROR CODE?

-------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------
0 Kudos
rjoycequincy
Visitor
Visitor
1,837 Views
Registered: ‎07-17-2019

denist:

Thank you for replying. I'm afraid I'll need some background info to regarding check on all three items. 

My apologies for my inexperience,  but I have never heard of these  names.
Of course I can guess what they imply.

  • Multiboot Reg            (is 0x4000, but must be 0 to select boot from CPU 0 only)
  • QUADREAD          (be sure that QSPI read width is 4-bits (per chip)
  • Bootrom Error code.    (not even sure how the bootrom functions, I guess this is  CSU?)

I suppose all these must be done from : 

  •  SDK GUI: dialog window setting such as 'Program Flash' 
  • SDK GUI:  from xsct%  command line.   
  • Other configuration ? 
  • In the FSBL/PMU code ? 

I'm happy to search out how to do these steps, but I do not know where to look. 

 

 

0 Kudos
denist
Xilinx Employee
Xilinx Employee
1,748 Views
Registered: ‎10-11-2011

OK, let's start from the datasheet of the flash you are using. There's should be a QUAD ENABLE bit that enabled reading in x4 from the flash.

If that's no set, the reading in the FSBL will FAILS.

In theory the mini-u-boot used by the programmer should set that but maybe is failing.

We had issue in the past like (Xilinx Answer 52598). 

-------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------
0 Kudos
jaychoi
Visitor
Visitor
1,321 Views
Registered: ‎08-26-2019

Dear 

================= In Stage 2 ============
QSPI 32 bit Boot Mode
QSPI is in Dual Parallel connection
QSPI is using 4 bit bus
FlashID=0xC2 0x25 0x3B
MACRONIX 1G Bits
MACRONIX_FLASH_MODE
MACRONIX_ENABLE_4BYTE_DONE
Multiboot Reg : 0x4000
QSPI Reading Src 0x20000000, Dest FFFF0040, Length EC0
XFSBL_ERROR_QSPI_LENGTH
Device Copy Failed

Boot Device Initialization failed 0x19
================= In Stage Err ============
Fsbl Error Status: 0x0
0 Kudos
denist
Xilinx Employee
Xilinx Employee
1,286 Views
Registered: ‎10-11-2011

I this particular case, the ROM seems to successfully find the image only after the whole flash is scanned once.

It does detect the image on the second pass.

Most of the time it means the flash wasn't ready to answer the first time around (maybe still under reset or initializing when PS_POR_B was released on zynq).

Can you try delaying PS_POR_B so your are sure the flash is ready to respond?

 

-------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------
0 Kudos
keda_zhengliang
Adventurer
Adventurer
514 Views
Registered: ‎05-07-2019

I also have the same question on zcu106 .

SD card is OK ,the same .BIN.

0 Kudos
denist
Xilinx Employee
Xilinx Employee
464 Views
Registered: ‎10-11-2011

It seems that the issue in my case for my setup (zcu102-es2)  was due to selecting the wrong flash type while programming the flash memory from the sdk, I had selected qspi_single instead of qspi_dual_paralell.

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